-
Notifications
You must be signed in to change notification settings - Fork 126
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
test: re-work test strategy for integration tests #3443
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3443 +/- ##
==========================================
+ Coverage 85.31% 85.36% +0.04%
==========================================
Files 167 167
Lines 7415 7412 -3
==========================================
+ Hits 6326 6327 +1
+ Misses 800 798 -2
+ Partials 289 287 -2 see 2 files with indirect coverage changes
Flags with carried forward coverage won't be shown. Click here to find out more. |
Signed-off-by: odubajDT <[email protected]>
1d2c0fd
to
201134e
Compare
Signed-off-by: odubajDT <[email protected]>
Signed-off-by: odubajDT <[email protected]>
Signed-off-by: odubajDT <[email protected]>
Signed-off-by: odubajDT <[email protected]>
Quality Gate passedIssues Measures |
Signed-off-by: odubajDT <[email protected]> Signed-off-by: vickysomtee <[email protected]>
security scans:
https://github.com/keptn/lifecycle-toolkit/actions/runs/8752659807
Changes
Reworked integration tests cluster setups to batches and run appropriate tests on each setup. Each cluster setup has Keptn installation with a custom values.yaml file, which enables/disables Keptn components or features.
A single integration test workflow was divided into multiple, so that each workflow sets up 1-3 different clusters with similar settings and runs the tests on them
The installation action for installing Keptn on cluster was simplified to accept fewer parameters (especially path to values.yaml file user for installation of Keptn)
Not all tests are ran with all possible combinations of cluster setup -> there is no need for such testing, we are aiming for testing certain functionality with certain cluster setup. Every test is ran at least once, max 3x on different cluster setups (where it makes sense to run).
Runtime for integration tests was reduced from ~20min to ~12min.