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
simplify e2e.go #74353
Comments
/sig testing |
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 |
/help |
@pohly: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed 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. |
@pohly I would like to work on this issue. |
Thanks for the offer. Let's see whether I can assign it to you... /assign @vinicyusmacedo If you want to discuss it further, feel free to reach out to the folks currently maintaining the E2E framework (the testing-commons sub-project of SIG-testing, see https://github.com/kubernetes/community/tree/master/sig-testing#subprojects). I'm less active there at the moment. |
What would you like to be added:
#66649 and its PR #68483 made it possible to use test/e2e/framework outside of Kubernetes. But projects doing that (like https://github.com/intel/pmem-CSI/blob/d4bd9086d742701ba5b5fe10d413a2ed79a8fad4/test/e2e/e2e.go or https://github.com/intel/oim/blob/799b79eb01b4471a715f3f12b4c199a7c055c8ef/test/e2e/e2e.go) still need to copy a significant chunk of code. It would be better to move more of that code into the test/e2e/framework itself where it then can be reused.
One thing that has to be kept in mind is that the set of dependencies of the framework should not be increased by this.
Why is this needed:
Simplifies the writing of a custom E2E test suite.
The text was updated successfully, but these errors were encountered: