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

Decouple clustered e2e tests and migrate to their own directory #3515

Open
mkcp opened this issue Feb 18, 2025 · 0 comments
Open

Decouple clustered e2e tests and migrate to their own directory #3515

mkcp opened this issue Feb 18, 2025 · 0 comments
Labels
enhancement ✨ New feature or request

Comments

@mkcp
Copy link
Contributor

mkcp commented Feb 18, 2025

Is your feature request related to a problem? Please describe.

Currently, our with-cluster e2e tests rely on 20_zarf_init_test.go to run and configure a cluster before they can run. This presents a few problems.

First, the zarf init test not only sets up a test cluster, it also runs assertions and test cases against it. This means it is both test setup and a test itself. This adds overhead and implicit ordering dependencies if you want to set up multiple clusters.

Describe the behavior you'd like

Decouple cluster initialization and zarf init behavioral tests from 20_zarf_init_test.go. Migrate all with-cluster tests into their own directory.

Additional context

  • main_test.go still must run first.
  • Just set up cluster from 20_zarf_init_test.go once and share it still.
  • Running tests in serial is fine for this one, parallelization is specced out in parent issue Parrallelize e2e test suite #3335
  • Tunable timeouts would be nice but not required. 35m feels arbitrary
@mkcp mkcp added the enhancement ✨ New feature or request label Feb 18, 2025
@mkcp mkcp added this to Zarf Feb 18, 2025
@mkcp mkcp moved this to Backlog in Zarf Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement ✨ New feature or request
Projects
Status: Backlog
Development

No branches or pull requests

1 participant