Project

General

Profile

action #65927

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

[functional][y] Identify list of the scenarios where we can remove test suites

Added by riafarov 12 months ago. Updated 11 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Enhancement to existing tests
Target version:
Start date:
2020-04-21
Due date:
2020-05-19
% Done:

0%

Estimated time:
5.00 h
Difficulty:

Description

With script from #65393 we should be able to identify scenarios where we can move settings to the job group or yaml files directly and remove test suite.

Url like https://openqa.suse.de/tests/overview?test=USBinstall can be used to identify if test suites is scheduled in other job groups.

Acceptance criteria

  1. List of the scenarios with proposals (e.g. move all the settings to the job group or create single test suite to inherit settings from it and override different ones in the job group)

History

#1 Updated by riafarov 12 months ago

  • Description updated (diff)
  • Due date set to 2020-05-19

#2 Updated by riafarov 12 months ago

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

#3 Updated by riafarov 11 months ago

  • Status changed from Workable to Feedback

https://github.com/perlpunk/openqa-convert-jobtemplates/blob/master/t/data/demo-template.yaml.expected1#L10
This is how test suite description can be defined in the job group.

move settings to yaml schedule, define only YAML_SCHEDULE in the job group:
autoyast_bcache
autoyast_btrfs
autoyast_eula_full_medium
autoyast_invalid_default_target
autoyast_nfs_share
autoyast_non_existing_graphical_target
autoyast_resize_luks2
autoyast_systemd_timesync
autoyast_y2_firstboot
crypt_no_lvm
ext4_yast
installer_extended_textmode
installer_extended_x11
minimal+base_yast
minimal+role_minimal
msdos

migrate to yaml schedule, use test suite for env related settings:
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)
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
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
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

For other test suites we have more complex things, but acting on the listed ones, will reduce number of test suites by almost 50% for our job group already.

#4 Updated by riafarov 11 months ago

  • Status changed from Feedback to Resolved

Follow up tickets are created for the identified list of the scenarios.

Also available in: Atom PDF