-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Frontend] Server Testing - test infra for pipeline ui node server #2215
Comments
Can you clarify the e2e tests item? I think we run some frontend tests as part of 2e2 tests. |
I saw there are some UI e2e tests, but I don't think they cover all usages of the node server. |
All p0 issues resolved |
/priority p1 |
The last p2 item of Unit tests for low coverage files according to coverage report can be improved in a separate issue. This one can be considered done. /close |
@Bobgy: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Signed-off-by: Dan Sun <[email protected]>
Pipeline UI node server has 0 test coverage at the moment. It prevents adding new features into the node server with confidence. In order to test more nuanced features like added in #2081.
We should add
Starting with jest tests would be the best
Work Items:
pipelines/frontend/server/app.test.ts
Line 354 in 2ec2fd2
/priority p0
/area testing
The text was updated successfully, but these errors were encountered: