action #132992
closedcoordination #130072: [epic] Handle openQA adaptions in Yam squad - SLE 15 SP6
Copy test coverage to YaM job group for SLE Micro
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.
Updated by JERiveraMoya 9 months ago
- 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
Updated by JERiveraMoya 9 months ago
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
Updated by zoecao 9 months ago
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)
Updated by zoecao 9 months ago
Submit PR to schedule the test modules for the test suites:
- 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)
- PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/17488
Updated by zoecao 9 months ago
The test suites are all added to SLE_Micro Yam job group now, and I re-triggered the jobs, will continue to review the tests results and add the job group template to yast ci.
Jobs: https://openqa.suse.de/tests/overview?distri=sle-micro&version=5.5&build=8.1_1.4&groupid=510
Updated by zoecao 9 months ago
Submit MR to add the job group template to yast ci:
https://gitlab.suse.de/qsf-y/qa-sle-functional-y/-/merge_requests/521
And submit a new PR to make the case slem_installation_default on s390x zvm also scheduled by yaml fileļ¼
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/17519
Updated by zoecao 9 months ago
The MR has pipeline error because of ALP Micor-default flavor is removed from openqa. File a ticket on it: https://progress.opensuse.org/issues/133739
Updated by leli 9 months ago
- Related to action #133739: Replace the ALP YAM job group flavor Micro-Default by Dolomite-Default added