-
Notifications
You must be signed in to change notification settings - Fork 9
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
🧪 Initial regression testing framework #780
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ff137
force-pushed
the
feat/regression_tests
branch
from
April 30, 2024 12:20
27754ee
to
f8ae589
Compare
Coverage Report
|
ff137
force-pushed
the
feat/regression_tests
branch
from
May 6, 2024 12:11
50e342d
to
8d72990
Compare
Coverage Report
|
Quality Gate passedIssues Measures |
Coverage Report
|
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements regression testing functionality, by utilising fixture parametrization, so existing tests can be run in a "clean_run" or a "regression_run" mode. A clean run will follow the existing logic of creating new members, connections, credentials etc, for each test. A regression run will utilise existing tenants, connections, credentials, etc, to assert that functionality works for existing fixtures.
Usage:
The above env vars will configure test fixtures to create regression test fixtures (i.e. reusable tenants, connections, schemas, and cred defs), if they don't already exist.
After a first test run is complete, you can set the following:
This will configure the tests to fail if any fixture is re-created, because after an initial first run, we expect existing fixtures to be re-used in subsequent test runs.
The PR currently skips 3 problematic tests from running in regression mode. They can be investigated in more detail at a later stage. Apart from that, all tests are currently passing in regression mode, in the first initial run, and subsequent runs.
To-do: