-
Notifications
You must be signed in to change notification settings - Fork 38.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
Write CoreV1Pod and CoreV1PodStatus lifecycle test - +4 coverage #90936
Comments
/reopen |
@Riaankl: Reopened 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. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
/reopen |
@Riaankl: Reopened 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. |
/triage accepted |
Progress
[8/8]
This issue is created to allow edit by @Riaankl
/wip
/hold
Identify an untested feature Using APISnoop
According to this APIsnoop query, there are still some remaining Pod endpoints which are untested.
Use API Reference to Lightly Document the Feature
The mock test
Test outline
Example in Go
Verify Increase it Coverage with APISnoop
Discover useragents:
List endpoints hit by the test:
Display endpoint coverage change:
Final notes
If a test with these calls gets merged, test coverage will go up by 4 points
This test is also created with the goal of conformance promotion.
/sig testing
/sig architecture
/area conformance
The text was updated successfully, but these errors were encountered: