action #42227

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

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

[functional][y] Move relevant scenarios to YaST job group on OSD

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

Status:ResolvedStart date:09/10/2018
Priority:NormalDue date:04/12/2018
Assignee:riafarov% Done:

0%

Category:Enhancement to existing testsEstimated time:5.00 hours
Target version:SUSE QA tests - Milestone 21
Difficulty:
Duration: 41

Description

See motivation in the parent ticket

Acceptance criteria

  1. Relevant scenarios are moved to YaST job group
  2. All performed changes are documented
  3. Setup is backed up before the changes

Here is the list of identified scenarios to be moved as they are currently are in Functional job group:

  • RAID0/1/10/5/6 (done)
  • addon-module-ftp
  • addon-module-http
  • allmodules+allpatterns
  • btrfs
  • btrfs+warnings (use EXIT_AFTER_START_INSTALL)
  • clone_system
  • 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
  • dud_sdk
  • ext4
  • gnome_http
  • gnome_install_smt ? (we don't own smt)
  • gnome_self_signed_https
  • gnome_smb
  • gpt
  • 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
  • lvm+resize_root
  • lvm_thin_provisioning
  • minimal+base
  • minimal+role_minimal
  • multipath
  • nis_client
  • nis_server
  • nvme
  • releasenotes_origin+unregistered
  • remote_ssh_controller
  • remote_ssh_target_ftp
  • remote_vnc_controller
  • remote_vnc_target_nfs
  • select_disk
  • skip_registration
  • sles+sdk+proxy_SCC_via_YaST
  • switch_keyboard_gnome
  • switch_keyboard_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

Functional_jobgroup_orig.json - SLE 15 job group template before the change (158 KB) riafarov, 06/11/2018 04:27 pm

YaST_SLE12_jobs.json - SLE 12 Server: Functional job group (135 KB) riafarov, 22/11/2018 03:16 pm

History

#1 Updated by okurz over 1 year ago

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

#2 Updated by riafarov over 1 year ago

  • Description updated (diff)
  • Status changed from New to Workable

#3 Updated by riafarov over 1 year ago

  • Description updated (diff)

#4 Updated by riafarov over 1 year ago

  • Description updated (diff)

#5 Updated by riafarov over 1 year ago

  • Description updated (diff)

#6 Updated by riafarov over 1 year ago

  • Due date set to 06/11/2018

#7 Updated by mloviska over 1 year ago

  • Description updated (diff)

#8 Updated by riafarov over 1 year ago

  • Assignee set to riafarov

#9 Updated by riafarov over 1 year ago

  • Description updated (diff)

#10 Updated by riafarov over 1 year ago

  • Due date changed from 06/11/2018 to 20/11/2018

#11 Updated by riafarov over 1 year ago

#12 Updated by riafarov over 1 year ago

  • Due date changed from 06/11/2018 to 20/11/2018

#13 Updated by riafarov over 1 year ago

  • Status changed from Workable to Feedback

Done for SLE 15, waiting for SLE 12 SP4 G<C release to apply there as well.

Hints:
1) Rename job group so the name is uinique
2) dump Job template: ./dump_templates --apikey xxx --apisecret xxx --host https://openqa.suse.de --group "YaST 15" --json JobTemplates > ~/Documents/YaST_jobgroup.json
3) Filter required scenarios with jq jq '.JobTemplates[] | select(.test_suite.name |test("lvm\\+RAID1|"))' < Functional_jobgroup.json
4) Save output to the file, fix json format
5) Remove test scenarios from the original job group
6) Load target job group template: ./load_templates --update --apikey xxx --apisecret xxx --host https://openqa.suse.de ~/Documents/YaST_jobgroup.json
7) Compare the list of the test suites in the target job group with the list of test suites to be moved
8) Move remaining scenarios if anything is missing

Errors I did during the move:
a) When importing had non-unique name, test suites were added to SLE 12 YaST job group
b) Didn't escape + in the test suites names when filtering with jq, need double backslash
c) For one test suite, priority was set to null when exported, doesn't work when import

#14 Updated by riafarov over 1 year ago

  • Description updated (diff)

#15 Updated by riafarov over 1 year ago

  • Due date changed from 20/11/2018 to 04/12/2018

We can split SLE 12 job group, which is the only missing part.

#16 Updated by riafarov over 1 year ago

  • Estimated time set to 5.00

#17 Updated by riafarov over 1 year ago

  • Status changed from Feedback to In Progress

Addressing SLE 12

#18 Updated by riafarov over 1 year ago

#19 Updated by riafarov over 1 year ago

  • Status changed from In Progress to Resolved

All listed scenarios were moved, now we will address each scenario separately to split/move/leave.

Also available in: Atom PDF