coordination #91193
Updated by punkioudi almost 3 years ago
After comparing test coverage of SLE 15 SP2 and SP3 in opneQA I identified several tests that are exclusive to either pre-release or post-release testing and could be easily used to increase our coverage just by using what we already have. It is possible that are some errors and some of the tests from the list are already being used. It is also just my opinion, therefor review from other colleagues is more then welcome. These are the console tests that run only before release and could be used also after the release (product QE -> QEM) ~~tests/console/btrfsmaintenance.pm (runs on mau-filesystem)~~ ~~tests/console/journald_fss.pm~~ tests/console/journald_fss.pm ~~tests/console/lvm_thin_check.pm~~ tests/console/lvm_thin_check.pm tests/console/ndctl.pm ~~tests/console/network_hostname.pm~~ tests/console/network_hostname.pm tests/console/nvme_checks.pm ~~tests/console/openvswitch_ssl.pm~~ tests/console/openvswitch_ssl.pm tests/console/snapper_cleanup_timeline.pm tests/console/systemd_nspawn.pm tests/console/verify_default_target.pm tests/console/verify_network.pm ~~tests/console/vsftpd.pm~~ tests/console/vsftpd.pm ## Acceptance criteria * **AC1** All aforementioned tests are scheduled in maintenance tests (aggregated or incidents), in their corresponding categories (When in doubt ask in qe-core channel) * **AC2** Cross reference with [openqa-module-mapper](https://github.com/ge0r/openQA-module-mapper) to figure what's already done and what's running where. * **AC3** If a test module needs black magic to work (i.e, takes more than half a day), a corresponding ticket is created and it is removed from this list.