action #132992
closed
coordination #130072: [epic] Handle openQA adaptions in Yam squad - SLE 15 SP6
Copy test coverage to YaM job group for SLE Micro
Added by leli 10 months ago.
Updated 10 months ago.
Description
Motivation¶
Based the analysis in https://progress.opensuse.org/issues/132317#note-2, we will start copying test coverage to YaM job group for SLE Micro from sle micro job group.
The test suites to be copied are the following:
- slem-extensions_and_modules
- slem_installation_autoyast (only we few basic module post-installation, including anything Cockpit-related, not all of them)
- slem_installation_default (only we few basic module post-installation, including anything Cockpit-related, not all of them)
- slem_ssh_installation_{controller|target}
Acceptance criteria¶
AC1: Copy test coverage to our own group for SLE Micro
Additional information¶
Notice it says "copy" and not "move" due to this is under discussion and the split of test suites among squads might not be a perfect clean cut, so, we can re-evaluate later it something is missing.
- Parent task set to #130072
- Subject changed from Copy test coverage to our own group for sle micro to Copy test coverage to YaM job group for SLE Micro
- Description updated (diff)
- Status changed from New to Workable
- Priority changed from Normal to Urgent
- Target version set to Current
- Status changed from Workable to In Progress
- Assignee set to zoecao
JERiveraMoya wrote:
looks like it is mostly copied, we should include in this ticket then to put in control version using YaST CI.
we are missing slem-extensions_and_modules in https://openqa.suse.de/tests/overview?distri=sle-micro&version=5.5&build=7.1_1.3&groupid=510
The test suite of slem-extensions_and_modules had been added to [SLE-Micro: Functional] job group, so I can not add it to Yast and Migration job group with the same test suite name, shall I change test suite name or submit MR to Function job group to remove it?
And for these two test suites, do I need to add a yaml schedule to control the test modules?
- slem_installation_autoyast (only we few basic module post-installation, including anything Cockpit-related, not all of them)
- slem_installation_default (only we few basic module post-installation, including anything Cockpit-related, not all of them)
JERiveraMoya wrote:
looks like it is mostly copied, we should include in this ticket then to put in control version using YaST CI.
I don't understand "using Yast CI", would you please help to explain it?
Submit PR to schedule the test modules for the test suites:
- Related to action #133739: Replace the ALP YAM job group flavor Micro-Default by Dolomite-Default added
- Status changed from In Progress to Resolved
The ticket above is resolved, and the MR for this ticket is also merged, so close here, thanks.
Also available in: Atom
PDF