Project

General

Profile

Actions

action #91172

closed

coordination #94045: [epic] Takeover of YaST-related automated tests from QAM to qe-yast team

Add existing QEM YaST tests to Product QE

Added by tjyrinki_suse over 3 years ago. Updated over 2 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:

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 after release and could be used also before the release (QEM -> product QE)

tests/console/yast2_registration.pm
tests/yast2_gui/yast2_instserver.pm
tests/yast2_gui/yast2_keyboard.pm
tests/yast2_gui/yast2_storage_ng.pm

Actions #1

Updated by tjyrinki_suse over 3 years ago

  • Subject changed from [qe-yast] Add existing QEM tests to Product QE to [qe-yast] Add existing QEM YaST tests to Product QE
  • Description updated (diff)
Actions #2

Updated by tjyrinki_suse over 3 years ago

  • Category set to New test
Actions #3

Updated by tjyrinki_suse over 3 years ago

  • Project changed from openQA Tests (public) to qe-yam
  • Category deleted (New test)

This is intended to be done by QE Yast.

Actions #4

Updated by oorlov over 3 years ago

  • Subject changed from [qe-yast] Add existing QEM YaST tests to Product QE to Add existing QEM YaST tests to Product QE
  • Target version set to Current
  • Parent task changed from #91139 to #94045
Actions #5

Updated by JERiveraMoya over 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.

Actions

Also available in: Atom PDF