action #91181
closedcoordination #91139: [qe-core][epic] add QEM exclusive tests to product QE runs to increase coverage
[qe-core] Add existing console QEM tests to Product QE
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 console tests that run only after release and could be used also before the release (QEM -> product QE)
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
Updated by tjyrinki_suse about 4 years ago
- Tracker changed from coordination to action
Updated by tjyrinki_suse almost 4 years ago
- Category set to New test
- Status changed from New to Workable
Updated by zluo almost 4 years ago
- Status changed from Workable to In Progress
http://10.160.64.152/tests/2688 shows that other test modules are not possible to pass the test for sles 15 functional. These tests are quite different and require source repos or Maintenace repos or runs on sles 12. Therefore I won't try further for adding to sles 15 functional.
With above 2 sub tickets should be okay for now.
Updated by zluo almost 4 years ago
- Status changed from In Progress to Feedback
Set is as feedback, waiting for resolved status of 2 sub tickets.
Updated by zluo over 3 years ago
- Status changed from Feedback to Resolved
sub tickets got resolved, so set it as resolved then.