action #91196
closedcoordination #94045: [epic] Takeover of YaST-related automated tests from QAM to qe-yast team
Add existing qe-yast Product QE tests to QEM
0%
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 YaST tests that run only before release and could be used also after the release (product QE -> QEM)
tests/console/yast2_cmdline.pm
tests/console/yast2_dns_server.pm
tests/console/yast2_kdump.pm
tests/console/yast2_lan_hostname.pm
tests/console/yast2_ntpclient.pm
tests/console/yast2_proxy.pm
tests/console/yast2_rmt.pm
tests/console/yast2_samba.pm
tests/console/yast2_settings.pm
tests/console/yast2_snapper_ncurses.pm
tests/console/yast2_vnc.pm
tests/network/wireguard.pm
tests/security/yast2_apparmor/manually_add_profile.pm
tests/security/yast2_apparmor/scan_audit_logs.pm
tests/security/yast2_apparmor/settings_disable_enable_apparmor.pm
tests/security/yast2_apparmor/settings_toggle_profile_mode.pm
tests/security/yast2_users/add_users.pm
Updated by tjyrinki_suse almost 3 years ago
- Project changed from openQA Tests to qe-yam
- Category deleted (
New test)
So this is intended to be done by QE Yast, moving to project accordingly.
Updated by oorlov almost 3 years ago
- Subject changed from [qe-yast][qem] Add existing qe-yast Product QE tests to QEM to Add existing qe-yast Product QE tests to QEM
- Target version set to Current
- Parent task changed from #91142 to #94045
Updated by JERiveraMoya almost 2 years ago
- Status changed from New to Rejected
Old ticket, we will consider with the new structure of squad how to increase test coverage.