Skip to content

Dependencies between e2e tests lead to cascading failures #512

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

Closed
m1kola opened this issue Nov 3, 2023 · 0 comments · Fixed by #534
Closed

Dependencies between e2e tests lead to cascading failures #512

m1kola opened this issue Nov 3, 2023 · 0 comments · Fixed by #534
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.

Comments

@m1kola
Copy link
Member

m1kola commented Nov 3, 2023

In this test we delete the test catalog:

// Delete the catalog first
Expect(c.Delete(ctx, operatorCatalog)).To(Succeed())

And later recreate it here:

operatorCatalog, err = createTestCatalog(ctx, testCatalogName, os.Getenv(testCatalogRefEnvVar))
Expect(err).ToNot(HaveOccurred())

The issue is that - if any of the assertions before catalog recreation fails all tests which use the test catalog will also fail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant