Project

General

Profile

Actions

action #44213

closed

YaST2 tests for quarterly refreshed ISOs

Added by hrommel1 over 5 years ago. Updated about 2 months ago.

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

0%

Estimated time:

Description

run the YaST2 tests on the quarterly refreshed ISOs on all architectures

note that a lot of test cases have been moved from the test group 'functional' to 'YaST2' lately

for reference of what is currently in this group of tests see
http://openqa.suse.de/tests/overview?distri=sle&version=15-SP1&build=100.4&groupid=129
or the attached PDF document

Update 2020-11: Current SLE 15SP2 QU testing done at https://openqa.suse.de/group_overview/321


Files

YaST2-SLE15-SP1-build100.4.pdf (64.4 KB) YaST2-SLE15-SP1-build100.4.pdf list of tests in YaST2 for SLE15 SP1 build 100.4 hrommel1, 2018-11-21 16:47
Actions #1

Updated by lnussel over 5 years ago

any reason why you specifically want the yast tests here? just start with a few tests from the Functional group.

Actions #2

Updated by hrommel1 over 5 years ago

lnussel wrote:

any reason why you specifically want the yast tests here? just start with a few tests from the Functional group.

Marita told me that recently a big portion of functional tests have been migrated into the YaST2 group. This is mostly consolidated as of today.

The intention of selecting the YaST2 group was to pick a group of tests that cover the installation and configuration workflow - which potentially is impacted a lot when using refreshed installation medias.

Actions #3

Updated by hrommel1 over 5 years ago

hrommel1 wrote:

lnussel wrote:

any reason why you specifically want the yast tests here? just start with a few tests from the Functional group.

Marita told me that recently a big portion of functional tests have been migrated into the YaST2 group. This is mostly consolidated as of today.

The intention of selecting the YaST2 group was to pick a group of tests that cover the installation and configuration workflow - which potentially is impacted a lot when using refreshed installation medias.

Rodion shared this link where functional tests are documented in detail:
https://gitlab.suse.de/riafarov/qa-sle-functional-y/blob/master/SLES_Integration_Level_Testplan.md

He suggested to pick something like the 'btrfs' test to get started.

Actions #4

Updated by lnussel over 5 years ago

So looks like you picked a more complicated one, qam-allpatterns+addons but no test ran yet.
AFAICS the yast2 test group contain more elaborate tests that need to use the ui of yast more, like RAID, non standard file systems etc. I'd still recommend to simply start with eg "default", "gnome", "cryptlvm" from the Functional group. The initial goal is to really get this going with a chance to have the tests green rather than testing yast UI features.

Actions #5

Updated by osukup over 5 years ago

Most important to test is an ability to install and prepare the working system in various scenarios -> which is +- Yast2 Group in productQA test :D so we will slowly add +- same tests

now is tested install with btrfs , ext4 , raid variants , install over SMB and HTTP, and many s390x senarios + xen-hvm and xen-pv

I'll plan check other tests in Yast2 group and select all usable tests.

On other side test on installed system isnt much needed to cover -> almost whole coverage is provided by QAM incident tests and Maintenance-Updates group

Actions #6

Updated by vpelcak over 4 years ago

  • Subject changed from YaST2 tests for quarterly refreshed ISOs to [qam][feature] YaST2 tests for quarterly refreshed ISOs
Actions #7

Updated by tjyrinki_suse over 3 years ago

  • Project changed from 119 to qe-yam
  • Target version deleted (QAM tests - current)
  • Parent task deleted (#44021)
Actions #8

Updated by riafarov over 3 years ago

  • Subject changed from [qam][feature] YaST2 tests for quarterly refreshed ISOs to YaST2 tests for quarterly refreshed ISOs
  • Assignee deleted (osukup)
  • Target version set to future
Actions #9

Updated by tjyrinki_suse over 3 years ago

  • Description updated (diff)
Actions #10

Updated by okurz about 2 years ago

This ticket was set to "Normal" priority but was not updated within the SLO period for "Normal" tickets (365 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives. Please consider picking up this ticket within the next 365 days or just set the ticket to the next lower priority of "Low" (no SLO related time period).

Actions #11

Updated by slo-gin about 1 year ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions #12

Updated by JERiveraMoya about 2 months ago

  • Status changed from New to Rejected

Backlog clean-up.

Actions

Also available in: Atom PDF