Project

General

Profile

action #42236

action #40475: [functional][y][saga] Establish YaST team split

action #42191: [functional][y][epic] Have separate job group for YaST subteam

[functional][y] Identify all scenarios to be split into two parts, to have one part in YaST job group

Added by riafarov over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Enhancement to existing tests
Target version:
SUSE QA tests - Milestone 20
Start date:
2018-10-09
Due date:
2018-10-23
% Done:

0%

Estimated time:
3.00 h
Difficulty:
Duration: 11

Description

See motivation in the parent ticket.

Acceptance criteria

  1. List of test suites which has to be split is created and mentioned in the parent epic for test suites on osd
  2. Same as 1., but for o3

History

#1 Updated by riafarov over 1 year ago

  • Parent task deleted (#40481)

#2 Updated by riafarov over 1 year ago

  • Parent task set to #42191

#3 Updated by okurz over 1 year ago

  • Category set to Enhancement to existing tests
  • Target version set to Milestone 20

#4 Updated by riafarov over 1 year ago

  • Estimated time set to 3.00 h

#5 Updated by riafarov over 1 year ago

  • Assignee set to riafarov

#6 Updated by riafarov over 1 year ago

For OSD:
Move:
RAID0/1/10/5/6
addon-module-ftp
addon-module-http
allmodules+allpatterns
btrfs
btrfs+warnings
clone_system
create_hdd_gnome
create_hdd_minimal_base+sdk ?
create_hdd_minimal_base+sdk_withhome ?
create_hdd_pcm_aws ?
create_hdd_pcm_azure ?
create_hdd_pcm_googlecloud ?
create_hdd_sled_gnome@64bit-virtio-vga ?
create_hdd_sled_gnome+development@64bit-virtio-vga ?
create_hdd_textmode
crypt_no_lvm
cryptlvm+activate_existing
cryptlvm+activate_existing+force_recompute
cryptlvm+activate_existing+import_users
cryptlvm+cancel_existing
detect_yast2_failures
dud_development_tools
ext4
gnome_http
gnome_install_smt ? (we don't own smt)
gnome_self_signed_https
gnome_smb
gpt (no sense to run on SLE15, default there, covered)
installer_extended (we can cover it in detect_yast2_failures, as of now this test suite doesn't make any sense)
iscsi_client
iscsi_server
lvm+RAID1
lvm+cancel_existing_cryptlvm
lvm-encrypt-separate-boot
minimal+base ?
minimal+role_minimal
multipath ?
nis_client
nis_server
nvme ?
registered+gnome+dev_tools_all_packages_dvd
releasenotes_origin+unregistered
remote_ssh_controller ?
remote_ssh_target_ftp ? vs ssh-X
remote_vnc_controller ?
remote_vnc_target_nfs ?
select_disk
skip_registration
skip_registration+sled+all-packages+activate_existing ?
skip_registration+workaround_modules ?
sles+sdk+proxy_SCC_via_YaST
ssh-X ?
switch_keyboard_gnome
switch_keyboard_textmode
textmode
xfs
yast2_gui
yast2_ncurses
yast2_ui_devel
yast_hostname
yast_hostname+dhcp_hostname
yast_hostname+linuxrc_hostname
yast_no_self_update
yast_self_update
zfcp@s390x-zfcp

Split:
USBinstall
allmodules+allpatterns
cryptlvm
cryptlvm_minimal_x
default
gnome_sled
iscsi_ibft
lvm
lvm+resize_root
lvm-full-encrypt
lvm_thin_provisioning
minimalx
minimal_x+uefi (nonsense to run on aarch64, covered by minimalx)
skip_registration+all-packages-iso
textmode+role_kvm
textmode+role_textmode
textmode+role_xen
videomode_text+textmode+role_kvm
videomode_text+textmode+role_xen
we-module ?
wsm+textmode ?

Convert to INSTALLONLY:
USBinstall (covered by default)
cryptlvm (covered by default)
cryptlvm_minimal_x (covered by minimalx)
lvm+resize_root
minimal_x+uefi

With question marks I've marked test suites which we could leave in functional, as they end up in different setup, but installer functionality is already covered. E.g. selecting custom set of patterns, as if selecting patterns works, then we can assume if other similar scenario fails, it's because of pattern content.

Secondly, we have 115 scenarios in total, considering smaller capacity in Y sub-team, we cannot afford having more than half of them in it.

#7 Updated by riafarov over 1 year ago

For openSUSE we could consider following:

openSUSE
Move:
RAID0/1/10/5
autoyast_gnome
autoyast_minimal
autoyast_reinstall_gnome
btrfs
btrfs_textmode
clone_system
create_hdd_gnome
create_hdd_kde
create_hdd_textmode
create_hdd_xfce
crypt_no_lvm
ext4
gnome-gdm
gnome+do_not_import_ssh_keys
gpt (no sense to run on Leap 15+ and TW, default there, covered)
install_offline
installer_extended
install_only
kde_dual_windows10
lvm+RAID1
minimalx+btrfs+nosephome ?
nvme@uefi
select_disk
switch_keyboard_gnome
switch_keyboard_textmode
transactional_host_install_only
uefi ?
xfs ?
xfs_textmode ?
yast2_gui
yast2_ncurses
yast_no_self_update
kde-live_installation

Split:
gnome
crypt_lvm
kde
kde-sddm
kde-wayland
lvm
lvm_thin_provisioning
lxde
minimalx
minimalx_btrfs_snapper
splitusr
textmode
xfce

#8 Updated by riafarov over 1 year ago

After discussion with Matthias, we agreed that for different combinations of patterns/modules/extensions, it's enough to validate that in general this functionality works, and problem can then be specific to the pattern/modules/extensions, which can be handled by U-team to split the load.

#9 Updated by riafarov over 1 year ago

  • Status changed from Workable to Resolved

Follow up tickets are created.

Also available in: Atom PDF