action #45152
Updated by riafarov almost 6 years ago
I would like to initiate a discussion regarding possible modules to use in installation validation.
Let me propose the bear minimum modules, which might be useful and already exists in our test directory.
* console/firewall_enabled
* console/aplay
* console/btrfs_autocompletition
* console/glibc_sanity
* console/gpt_ptable
* console/gpg
* console/journalctl
* console/kdump_and_crash
* console/rsync
* console/http_srv
* console/sshd
* console/sysctl
* console/sysstat
* console/cron
* console/yast2_lan
* console/yast2_bootloader
* console/yast2_i
* console/yast2_clone_system
* toolchain/gcc_compilation
* toolchain/gcc_fortran_compilation
* x11/firefox
* x11/wireshark
* x11/yast2_snapper
* x11/yast2_hostnames
* x11/yast2_firewall
* <del> console/consoletest_setup</del>
* <del> console/zypper.ref</del>
* <del> console/zypper.lr</del>
* <del> rt/kmp_modules</del>
* <del> rt/rt_devel_packages</del>
* <del> rt/rt_is_realtime</del>
* <del> rt/rt_peak_pci</del>
* <del> rt/rt_preempt_test</del>
* <del> console/hostname</del>
## Acceptance criteria
1. List of modules to be used is identified
2. The identified set of modules is enabled in the test suite for RT product
## Suggestions
We could use new scheduling mechanism not to deal with main.pm complexity.