coordination #91139
closed[qe-core][epic] add QEM exclusive tests to product QE runs to increase coverage
100%
Description
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 tests that run only after release and could be used also before the release (QEM -> product QE)
QE Core:
tests/console/bind.pm
tests/console/dracut_enhanced.pm
tests/console/gd.pm
tests/console/iotop.pm
tests/console/journalctlLevels.pm
tests/console/krb5.pm
tests/console/libgcrypt.pm
tests/console/libssh.pm
tests/console/openssl_nodejs.pm
tests/console/perf.pm
tests/console/rsync_client.pm
tests/console/rsync_server.pm
tests/console/systemd_rpm_macros.pm
tests/console/valgrind.pm
tests/network/autofs_client.pm & autofs_server
tests/network/salt_master.pm
tests/network/salt_minion.pm
tests/network/samba/samba_adcli.pm
tests/x11/piglit/piglit.pm
tests/x11/tomcat.pm
QE Yast
tests/console/yast2_registration.pm
tests/yast2_gui/yast2_instserver.pm
tests/yast2_gui/yast2_keyboard.pm
tests/yast2_gui/yast2_storage_ng.pm
Updated by tjyrinki_suse about 3 years ago
- Tracker changed from action to coordination
- Subject changed from add QEM exclusive tests to product QE runs to increase coverage to [qe-core][epic] add QEM exclusive tests to product QE runs to increase coverage
- Start date deleted (
2021-04-14)
Updated by tjyrinki_suse about 3 years ago
- Category set to New test
- Status changed from New to Workable
Updated by tjyrinki_suse over 2 years ago
- Status changed from Workable to Resolved
- Assignee set to tjyrinki_suse
These have all been done!