QA (public) » openQA Project (public) » openQA Tests (public) » qe-yam

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

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.

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.

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.

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

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).

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.