action #25210
closedcoordination #23798: [qe-core][sles][functional][epic] Add systemd test suite execution to openQA
[sle][functional] Add test suite patched_systemd
0%
Description
****## User story
As a SUSE systemd developer I want to automatically test our patches for systemd on released distribution versions to have earlier feedback about potential regressions introduced by SUSE patches on architectures I do not have available for testing
Acceptance criteria¶
- AC1 The test should install the patched systemd version provided by systemd department.
- AC2 The test should install the systemd-testsuite that matches the patched systemd version.
- AC3 The test should work for all the released version (at the moment SLE <= 12-SP3 and Leap <= 42.3)
Tasks¶
- create new test module that executes the systemd test suite
- create new test schedule (main.pm) that executes the installation of systemd - compare to gnuhealth but in textmode, reboot, install of testsuite, execution
- add this test suite to osd
- add this test suite to o3
Settings¶
Test suite name: suse_patches-systemd_testsuite
O3 42.3¶
BOOT_HDD_IMAGE=1
DESKTOP=textmode
HDD_1=%DISTRI%-%VERSION%-%ARCH%-%BUILD%-%DESKTOP%@%MACHINE%.qcow2
QA_HEAD_REPO=https://download.opensuse.org/repositories/home:/tsaupe:/testsuites/openSUSE_Leap_42.3
START_AFTER_TEST=create_hdd_textmode
SYSTEMD_TESTSUITE=1
OSD 12-SP2¶
BOOT_HDD_IMAGE=1
DESKTOP=textmode
HDD_1=%DISTRI%-%VERSION%-%ARCH%-%BUILD%-%DESKTOP%@%MACHINE%.qcow2
QA_HEAD_REPO=http://download.suse.de/ibs/QA:/Head/SLE-12-SP2/
START_AFTER_TEST=create_hdd_textmode
SYSTEMD_TESTSUITE=1
OSD 12-SP3¶
BOOT_HDD_IMAGE=1
DESKTOP=textmode
HDD_1=%DISTRI%-%VERSION%-%ARCH%-%BUILD%-%DESKTOP%@%MACHINE%.qcow2
QA_HEAD_REPO=http://download.suse.de/ibs/QA:/Head/SLE-12-SP3/
START_AFTER_TEST=create_hdd_textmode
SYSTEMD_TESTSUITE=1
Info¶
This approach should be applied to test a patched systemd version for an already released product. For example, Leap 42.3 and SLE-12-SP3.
As this request would be about testing systemd patches on released products with custom repositories it is neither part of main QA SLE responsibility for build validation of new product versions nor QAM because the patches should be tested before an incident update is prepared.