action #152083
closedcoordination #151990: [epic] Optimize test coverage
Unify migration test suites names according to each row in migration matrix for SLES 15 SP3
0%
Description
Motivation¶
Same than #152011 but for SLES 15 SP3. Offline and Online test suites are very much different technically so we can still have different test suite name for them BUT we could add the offline or online at the end, so we see together ordered alphabetically the test suites related with each line in the migration test matrix.
Additionally:
- we could apply here renaming of "minimal" to "updatestack" due to it is very confusing in sles 15 where we have system role minimal.
- avoid to use ltss in the name of the test suite.
Acceptance criteria¶
AC1: Group all test suites for extension/module combination in migration matrix + role under same test suite name
AC2: Fill in test suite description differently for each case in job group yaml indicating the differences contained in the cells of the migration matrix.
Updated by JERiveraMoya about 1 year ago
- Subject changed from Unify migration test suites doing functionally the same with small differences under same name for SLES 15 SP3 to Unify migration test suites names according to each row in migration matrix for SLES 15 SP3
Updated by hjluo about 1 year ago
- Status changed from Workable to In Progress
- Assignee set to hjluo
Updated by hjluo about 1 year ago · Edited
Updated by JERiveraMoya 12 months ago
- Tags changed from qe-yam-dec-sprint, qe-yam-jan-sprint to qe-yam-jan-sprint
Updated by JERiveraMoya 11 months ago
- Tags changed from qe-yam-jan-sprint to qe-yam-feb-sprint
Updated by JERiveraMoya 11 months ago · Edited
Please, apply similar approach than in https://gitlab.suse.de/qe-yam/openqa-job-groups/-/merge_requests/41
Updated by JERiveraMoya 11 months ago
- Status changed from In Progress to Resolved