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.

Sign up for GitHub

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

Jump to bottom

✨ Use a separate namespace for each e2e test #1428

Merged
merged 1 commit into from
Nov 7, 2024
Merged

✨ Use a separate namespace for each e2e test #1428

merged 1 commit into from
Nov 7, 2024
+105 −37

Commits on Nov 7, 2024

  1. Use a separate namespace for each e2e test 

    Fixes operator-framework#1307

Create and use a new namespace for every e2e test. This means that
extension resources are placed in their own namespace. The tests
deletes the namespace, and then waits until completion. This ensures
that _most_ of an extension's resources are deleted.

It does guarantee that global resources (e.g. CRDs, CRs, CRBs) are
deleted.

And would eventually allow the tests to be run in parallel (assuming
the installed extensions allow for that).

Signed-off-by: Todd Short <[email protected]>
    @tmshort
    tmshort committed Nov 7, 2024
    Configuration menu
    Copy the full SHA
    c64e360 View commit details
    Browse the repository at this point in the history