Project

General

Profile

action #66967

coordination #63280: [functional][y][epic] Reduce number of test suites used for YaST job group

[functional][y] Move more scenarios to job group from openQA database

Added by riafarov about 1 year ago. Updated 12 months ago.

Status:
Resolved
Priority:
Normal
Category:
Infrastructure
Target version:
Start date:
2020-05-18
Due date:
2020-08-11
% Done:

0%

Estimated time:
8.00 h
Difficulty:

Description

Alex has migrated all the scenarios to yaml, so it will be easier now. We still should use openQA database where it allows us to keep cleaner structure and inherit settings from those.
In case scenario is used in other job groups, we should keep it as it is for now and only act on the scenarios which are executed in the YaST job group.
NOTE: please, keep in mind that some scenarios can be executed in TW/Leap and changes on osd should not break/change them.

So for some of the scenarios below we have some special settings, which can be reused for multiple test suites.
In braces we have settings which are different and prevents from complete removal of the test suite from openQA DB ( https://openqa.suse.de/admin/test_suites ).
We store test suites definitions here: https://gitlab.suse.de/qsf-y/qa-sle-functional-y/-/blob/master/JobGroups/test_suites.yaml

List of the scenarios:
autoyast_bug-872532_ix64ph1069 (HDDMODEL: scsi-hd)
autoyast_bug-876411_btrfs_h5_autoinst (HDDMODEL: scsi-hd)
autoyast_bug-877438_ix64ph1029 (HDDMODEL: scsi-hd)
autoyast_bug-879147_autoinst (HDDMODEL: scsi-hd)
autoyast_bug-887126_autoinst (HDDMODEL: scsi-hd)
autoyast_bug-887653_autoinst_jy-snapshot (HDDMODEL: scsi-hd)
autoyast_error_dialog
autoyast_ext4
autoyast_gnome
autoyast_keyboard_layout (HDDMODEL: scsi-hd HDDSIZEGB: '30')
autoyast_mini (HDDMODEL: scsi-hd HDDSIZEGB: '30')
autoyast_multi_btrfs (NUMDISKS: 4)
autoyast_multipath (MULTIPATH)
multipath (MULTIPATH)
autoyast_non_secure_boot (UEFI_PFLASH_CODE, UEFI_PFLASH_VARS)
autoyast_salt (HDDMODEL: scsi-hd HDDSIZEGB: '30')
autoyast_zkvm_sles_product_reg
btrfs+warnings
btrfs_libstorage-ng (HDDSIZEGB)
crypt_no_lvm (used by qam)
cryptlvm+activate_existing (HDD_1, BOOTFROM)
cryptlvm+activate_existing+force_recompute (HDD_1, BOOTFROM)
cryptlvm+activate_existing+import_users (HDD_1, BOOTFROM)
cryptlvm+cancel_existing (HDD_1, BOOTFROM)
lvm+cancel_existing_cryptlvm (HDD_1, BOOTFROM)
detect_yast2_failures
dud_development_tools
ext4_yast (used by qam)
gnome_http
gnome_self_signed_https
gnome_smb
installer_extended
lvm
lvm+RAID1 (HDDSIZEGB)
lvm+resize_root (HDDSIZEGB)
lvm-encrypt-separate-boot
lvm-full-encrypt (HDDSIZEGB)
lvm_thin_provisioning (HDDSIZEGB)
mediacheck
minimal+role_minimal
releasenotes_origin+unregistered
repo_inst
textmode_installation_minimal_role
xfs
yast_hostname
yast_hostname+dhcp_hostname
yast_hostname+linuxrc_hostname
yast_no_self_update
yast_self_update
zfcp

History

#1 Updated by JERiveraMoya about 1 year ago

  • Description updated (diff)

#2 Updated by JERiveraMoya about 1 year ago

  • Description updated (diff)

#3 Updated by riafarov about 1 year ago

  • Due date set to 2020-07-28

#4 Updated by oorlov about 1 year ago

  • Status changed from New to In Progress
  • Assignee set to oorlov

Here is the list with all the test suites from the last build (209.2) in YaST Job Group, that does not have yaml schedule:

#5 Updated by oorlov about 1 year ago

  • Status changed from In Progress to Workable
  • Assignee deleted (oorlov)

Unassigned, as I thought it is related to https://progress.opensuse.org/issues/68555

#6 Updated by riafarov about 1 year ago

  • Status changed from Workable to New

#7 Updated by riafarov about 1 year ago

  • Subject changed from [functional][y] Migrate scenarios to yaml and move to job group to [functional][y] Move more scenarios to job group from openQA database
  • Description updated (diff)

#8 Updated by riafarov about 1 year ago

  • Due date changed from 2020-07-28 to 2020-08-11

#9 Updated by riafarov about 1 year ago

  • Description updated (diff)
  • Status changed from New to Workable
  • Estimated time set to 8.00 h

#10 Updated by syrianidou_sofia about 1 year ago

  • Status changed from Workable to In Progress
  • Assignee set to syrianidou_sofia

#12 Updated by syrianidou_sofia 12 months ago

  • Status changed from In Progress to Feedback

#13 Updated by syrianidou_sofia 12 months ago

  • Status changed from Feedback to Resolved

The test suite entries have been deleted from the osd data base. No related failures were found when running all YaST jobs.

Also available in: Atom PDF