-
Notifications
You must be signed in to change notification settings - Fork 216
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 E2E tests #233
Comments
I am looking into this, but may not be super fast. Need to catch up on prow and how the test infrastructure for Kubeflow works. Do I understand it correct that prow is not used atm, since the prow config is empty @terrytangyuan ? |
/assign |
Thanks! Yes that’s correct. |
I have played around with the test infra a bite. Do we have any thought about how we like the e2e test to look like? Should we build it based upon one of the examples? If so I suggest that we use the v1alpha2/tensorflow-benchmark. |
Yes that would be a good example to use for end2end test. |
Actually v1 controller is the one we want to graduate so use this example instead: https://github.com/kubeflow/mpi-operator/blob/master/examples/v1/tensorflow-benchmarks.yaml |
@terrytangyuan How about doing e2e using something like |
See #296 for an alternative approach to leverage AWS's test infra. |
cc @kubeflow/wg-training-leads @PatrickXYS |
FYI, you can check migration doc here https://github.com/kubeflow/testing/blob/master/aws/Doc/onboarding.md |
I agree that the end goal is to use the real infrastructure. As a contributor I would like to run functional test prior submitting the PR. Also I would like to run partial set of tests based on the changes. Can you explain what is the disadvantages of using something in memory and also have an option to use the actual infrastructure based on a flag? This gives significant advantages of having a short dev/test cycle. |
@PatrickXYS How do I get access to the repo aws-kf-ci-bot? I would like to start working on the e2e tests. |
You won't, you should follow the doc to proceed |
I started to look into this (along with integration tests). Did anyone make any progress? |
With #399 and #403 merged, I think we should be good to close this. @terrytangyuan wdyt? |
Sure. Thank you! |
Part of #217.
The text was updated successfully, but these errors were encountered: