QA » openQA Project » openQA Tests » Containers and images

Currently, different JeOS tests are using different ways of scheduling tests.

SLES:

• jeos-main -> schedule/jeos/sle/jeos-main.yaml
• jeos-extratest -> schedule/jeos/sle/jeos-extratest.yaml
• jeos-fs_stress -> schedule/jeos/sle/jeos-fs_stress.yaml
• jeos-fips -> schedule/jeos/sle/fips.yaml
• jeos-ltp -> schedule/jeos/sle/jeos-ltp.yaml
• jeos-base+sdk+desktop -> schedule/jeos/sle/jeos-base%2Bsdk%2Bdesktop.yaml jeos-apparmor -> lib/main_common.pm openstack -> lib/main_common.pm jeos-containers -> lib/main_containers.pm

SLES RPi: https://github.com/os-autoinst/os-autoinst-distri-opensuse/tree/master/schedule/jeos/sle/rpi

for openSUSE, everything is handled via main_common.pm
https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/products/opensuse/main.pm#L261

if (is_jeos) {
    load_jeos_tests();
}

which loads common tests from main_common.pm for all the tests, and then we have specific tests for for the other jobs, for instance kernel or containers:

if (is_kernel_test()) {
    load_kernel_tests();
}
elsif (is_container_test) {
    load_container_tests();
}

We have everything scattered over different files. This can lead to gaps in coverage from OSD and O3.
The best way to unify all the schedules would be to have a dedicated centralized schedule, similar to main_publiccloud.pm or main_containers.pm will all the needed conditions for the different distris/versions/backends etc.

What we would need to do in the products/sle|opensuse/main.pm is:

if (is_jeos) {
    load_jeos_tests();
    return;
}