action #25210
Updated by okurz over 6 years ago
## User story Info As This approach should be applied to test a SUSE patched systemd developer I want to automatically test our patches version for systemd on an already released distribution versions to have earlier feedback about potential regressions introduced by SUSE patches on architectures I do not have available for testing product. For example, Leap 42.3 and SLE-12-SP3. ## 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 ## IBS repos: - SLE-12-SP2 http://download.suse.de/ibs/home:/tsaupe/SLE_12_SP2/x86_64/ - SLE-12-SP3 http://download.suse.de/ibs/home:/tsaupe/SLE_12_SP3/x86_64/ - Leap 42.2 n/a - Leap 42.3 n/a ## 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.