Skip to content
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

re-organize e2e tests #1404

Closed
lburgazzoli opened this issue Apr 14, 2020 · 2 comments
Closed

re-organize e2e tests #1404

lburgazzoli opened this issue Apr 14, 2020 · 2 comments
Labels
area/continuous integration Related to CI and automated testing kind/question Further information is requested

Comments

@lburgazzoli
Copy link
Contributor

We do execute e2e tests against a number of platform with different container image publishers but for most of the tests, the way the image is published does not matter at all so I think we should re-organize the e2e to:

  • define the tests beseline as vanilla k8s + knative with spectrum
  • specific test for OpenShift
  • specific test for OpenShift + knative (if possible)
  • specific test for buildah
  • specific test for buildah + knative

@nicolaferraro @astefanutti WDYT ?

@lburgazzoli lburgazzoli added kind/question Further information is requested area/continuous integration Related to CI and automated testing labels Apr 14, 2020
@astefanutti
Copy link
Member

I think that makes sense to improve tests execution time and resources optimisation. For the baseline tests, we may want to choose the builder that's the most supported, to cover most of its surface.

@nicolaferraro
Copy link
Member

This is done, except that for common test we had to choose the builder that doesn't fail randomly in the CI environment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/continuous integration Related to CI and automated testing kind/question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants