-
Notifications
You must be signed in to change notification settings - Fork 490
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
Add hook points support in conformance test suite #3131
Comments
@mlavacca: The label(s) 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-sigs/prow repository. |
@mlavacca: The label(s) 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-sigs/prow repository. |
/triage needs-triage |
@mlavacca: The label(s) 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-sigs/prow repository. |
This sounds like a good idea, yeah. Making it easier for developers to get value from the conformance tests, whether or not they're "part of the Gateway API", sounds like a Good Thing™. 🙂 |
Discussed in today's community meeting, this sounds like a great idea, thanks @shawnh2! /triage accepted |
Assign myself, since I've been working on something that is quite similar to this issue as well. I will post the initial design of this here once it's done. /assign |
What would you like to be added:
Add the hook point support for current conformance test suite.
For example, like
AfterTestFail
hook point, developers can attach various commands to this hook point, and programs that attach to this hook point wil only be executed if one conformance test is failed.Why this is needed:
This will be super helpful for developers to debug the failed conformance test.
Sometimes the error trace reported by conformance test is not very useful. For example, we'd like to see the status/logs of specific resources (by attaching
kubectl
cmd to the hook which I described above could ease the pain), even some other configs that can be retrieved by other commands.The text was updated successfully, but these errors were encountered: