coordination #13040
closed[functional][epic][u]more flexible console test selection by addons, testsuite variable, etc. (was: Run zypper lifecycle more selectively)
0%
Description
As discussed in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/1613
"introduce a new variable to run additional console tests that need more coverage but not so much to run in every scenario.
This needs to be set in one test suite run per product and main.pm can calculate it to run when we have ADDONS or other things."
Updated by okurz over 7 years ago
- Blocked by action #14692: Running zypper_lifecycle on unpatched system reveals different results added
Updated by okurz over 7 years ago
sorry, I don't understand the module enough anymore to actually do this. Also, it's kinda blocked by #14692 now. Maybe nadvornik can help.
Updated by okurz over 7 years ago
- Related to coordination #15132: [saga][epic] Better structure of test plans in main.pm added
Updated by okurz about 7 years ago
- Subject changed from Run zypper lifecycle more selectively to more flexible console test selection by addons, testsuite variable, etc. (was: Run zypper lifecycle more selectively)
- Category changed from Bugs in existing tests to Enhancement to existing tests
- Priority changed from High to Normal
not going forward here but at least since the ticket was created we have #15132 with better ideas regarding the testplan. We can keep this ticket for the idea how to do it.
Updated by okurz about 6 years ago
- Subject changed from more flexible console test selection by addons, testsuite variable, etc. (was: Run zypper lifecycle more selectively) to [functional]more flexible console test selection by addons, testsuite variable, etc. (was: Run zypper lifecycle more selectively)
Updated by okurz about 6 years ago
- Subject changed from [functional]more flexible console test selection by addons, testsuite variable, etc. (was: Run zypper lifecycle more selectively) to [functional][epic][u]more flexible console test selection by addons, testsuite variable, etc. (was: Run zypper lifecycle more selectively)
- Target version set to Milestone 18
Updated by okurz almost 6 years ago
- Target version changed from Milestone 18 to Milestone 18
Updated by okurz over 5 years ago
- Target version changed from Milestone 18 to future
Updated by mgriessmeier about 4 years ago
- Status changed from New to Rejected
already covered by splitting extratests, as well as by YAML scheduling approach
Updated by szarate over 3 years ago
- Tracker changed from action to coordination
Updated by szarate over 3 years ago
See for the reason of tracker change: http://mailman.suse.de/mailman/private/qa-sle/2020-October/002722.html