Project

General

Profile

action #42494

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

[epic][functional][y] Split/adapt scenarios to move installer related part to YaST specific job group

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

Status:
Resolved
Priority:
High
Assignee:
Category:
Enhancement to existing tests
Target version:
SUSE QA tests - Milestone 30+
Start date:
2018-10-25
Due date:
2019-11-19
% Done:

100%

Estimated time:
(Total: 37.00 h)
Difficulty:
Duration: 279

Description

See motivation in the parent ticket.

Use same, approach as we used in #42230 for default

Valuable outcomes of discussions:
We decided that it makes sense to keep test suites which people from a single team can fix should stay by that team. E.g. zVM tests.
+VAR_NAME format can be used in the machines definition to override settings in the test suite. E.g. for the env which do not support booting into images, we can override HDD_1 and BOOT_TO_SNAPSHOT and BOOT_HDD_IMAGE, so it first of all doesn't fail as incomplete due to missing expected image and secondly conducts prerequisite steps to get to the same point as in case of booting to the image.

Proposed naming convention is %current_test_suite_name%_installation for the installation part, other test scenario keeps it's current name.

Acceptance criteria

  1. All the scenarios from the list are either divided into parts or decision made to keep them in one job group or another.
  2. All performed changes are documented
  3. Setup is backed up before the changes

List of scenarios to be split into installation part and other

*USBinstall

  • allmodules+allpatterns
  • cryptlvm
  • default (Please see the solution in poo#42230);
  • iscsi_ibft
  • lvm
  • lvm+resize_root
  • lvm-full-encrypt
  • lvm_thin_provisioning
  • minimalx
  • minimal_x+uefi (nonsense to run on aarch64, covered by minimalx, fix when changing schedule)
  • registered+gnome+dev_tools_all_packages_dvd (has to be adjusted for sp2)
  • skip_registration+all-packages-iso (has to be adjusted for sp2)
  • textmode
  • textmode+role_textmode
  • videomode_text+textmode+role_kvm
  • videomode_text+textmode+role_xen

Subtasks

action #42941: [sle][functional][y] implement validation for lvm-full-encrypt and lvm-encrypt-separate-boot test suitesResolvedybonatakis

action #48173: [sle][functional][y] implement validation for encrypt lvm test suitesResolvedmloviska

action #48401: [functional][y] Implement test module to validate iscsi_ibft installationResolvedmloviska

action #48176: [sle][functional][y] implement validation for autoyast_gnome test suiteResolvedybonatakis

action #52508: [functional][y] Validate skip_registration+all-packages-iso scenario with modules which make senseRejectedriafarov

action #53258: [functional][y] Validate installation with btrfsResolvedoorlov

action #54779: [sle][functional][y] fix validation tests for encrypted lvm test suitesResolvedoorlov

action #55421: [functional][y] change btrfs test suite as per #53258Resolvedoorlov

action #56990: [functional][y] Validate minimal+base scenario with modules which make senseClosedybonatakis


Related issues

Related to openQA Tests - action #44144: [functional][y] Rework "boot_into_snapshot" to boot from images and not reconduct whole installationResolved2018-11-212019-07-16

Related to openQA Tests - action #42854: [functional][y][epic] Introduce relevant installation validation test modulesIn Progress2018-10-242020-07-14

History

#1 Updated by riafarov over 1 year ago

  • Subject changed from [fucntional][y] Split scenarios to move installer related part to YaST specific job group to [functional][y] Split scenarios to move installer related part to YaST specific job group
  • Description updated (diff)

#2 Updated by riafarov over 1 year ago

  • Description updated (diff)

#3 Updated by oorlov over 1 year ago

  • Description updated (diff)

#4 Updated by oorlov over 1 year ago

  • Description updated (diff)

#5 Updated by okurz over 1 year ago

  • Category set to Enhancement to existing tests

#6 Updated by riafarov over 1 year ago

  • Description updated (diff)

#7 Updated by okurz over 1 year ago

  • Target version set to Milestone 21

#8 Updated by okurz over 1 year ago

  • Blocks action #44144: [functional][y] Rework "boot_into_snapshot" to boot from images and not reconduct whole installation added

#9 Updated by okurz over 1 year ago

  • Due date set to 2018-12-18

#10 Updated by riafarov over 1 year ago

  • Subject changed from [functional][y] Split scenarios to move installer related part to YaST specific job group to [epic][functional][y] Split scenarios to move installer related part to YaST specific job group

#11 Updated by riafarov over 1 year ago

  • Subject changed from [epic][functional][y] Split scenarios to move installer related part to YaST specific job group to [epic][functional][y] Split/adapt scenarios to move installer related part to YaST specific job group
  • Description updated (diff)

#12 Updated by riafarov over 1 year ago

  • Has duplicate action #42854: [functional][y][epic] Introduce relevant installation validation test modules added

#13 Updated by riafarov over 1 year ago

  • Has duplicate deleted (action #42854: [functional][y][epic] Introduce relevant installation validation test modules)

#14 Updated by riafarov over 1 year ago

  • Blocks action #42854: [functional][y][epic] Introduce relevant installation validation test modules added

#15 Updated by okurz over 1 year ago

  • Target version changed from Milestone 21 to Milestone 23

#16 Updated by riafarov over 1 year ago

  • Due date set to 2019-02-26

due to changes in a related task

#17 Updated by okurz over 1 year ago

@team this is an epic which the team should be highly interested in. However so far there is only one subtask and there has not been much action by you guys, e.g. propose something, create subtasks, etc. I suggest during your normal work within the sprints you pick up these tasks accordingly.

#18 Updated by okurz over 1 year ago

  • Status changed from New to Workable

I consider this a "Workable" epic, i.e. one can create more subtasks and refine

#19 Updated by riafarov over 1 year ago

okurz wrote:

@team this is an epic which the team should be highly interested in. However so far there is only one subtask and there has not been much action by you guys, e.g. propose something, create subtasks, etc. I suggest during your normal work within the sprints you pick up these tasks accordingly.

We working on that step by step and have other tasks of tests maintenance where we have to spend a lot of time. On top we have 209 jobs in YaST vs 190 in Functional, which decreases urgency of moving even more scenarios to the YaST. So main goal is reached, and we will continue in that direction.
I will add more sub-tasks as we go.

#20 Updated by riafarov over 1 year ago

  • Description updated (diff)

#21 Updated by riafarov over 1 year ago

  • Blocks deleted (action #42854: [functional][y][epic] Introduce relevant installation validation test modules)

#22 Updated by riafarov over 1 year ago

  • Due date changed from 2019-02-26 to 2019-03-12

due to changes in a related task

#23 Updated by riafarov over 1 year ago

  • Due date changed from 2019-03-12 to 2019-03-26

due to changes in a related task

#24 Updated by okurz over 1 year ago

  • Due date changed from 2019-03-26 to 2019-06-18

due to changes in a related task

#25 Updated by okurz over 1 year ago

  • Target version changed from Milestone 23 to Milestone 25

#26 Updated by riafarov about 1 year ago

  • Blocks deleted (action #44144: [functional][y] Rework "boot_into_snapshot" to boot from images and not reconduct whole installation)

#27 Updated by riafarov about 1 year ago

  • Related to action #44144: [functional][y] Rework "boot_into_snapshot" to boot from images and not reconduct whole installation added

#28 Updated by riafarov about 1 year ago

  • Description updated (diff)

#29 Updated by riafarov about 1 year ago

  • Parent task deleted (#42191)

#30 Updated by riafarov about 1 year ago

  • Parent task set to #40475

#31 Updated by riafarov about 1 year ago

  • Due date changed from 2019-06-18 to 2019-07-02

due to changes in a related task

#32 Updated by riafarov about 1 year ago

  • Target version changed from Milestone 25 to Milestone 30+

This is still ongoing.

#33 Updated by riafarov about 1 year ago

  • Due date changed from 2019-07-02 to 2019-07-16

due to changes in a related task

#34 Updated by riafarov 12 months ago

  • Due date changed from 2019-07-16 to 2020-02-04

due to changes in a related task

#35 Updated by riafarov 12 months ago

  • Due date changed from 2020-02-04 to 2019-08-13

due to changes in a related task

#36 Updated by JERiveraMoya 11 months ago

  • Due date changed from 2019-08-13 to 2019-08-27

due to changes in a related task

#37 Updated by riafarov 10 months ago

  • Due date changed from 2019-08-27 to 2019-09-10

due to changes in a related task

#38 Updated by riafarov 10 months ago

  • Due date changed from 2019-09-10 to 2019-09-24

due to changes in a related task

#39 Updated by riafarov 10 months ago

  • Due date changed from 2019-09-24 to 2019-10-08

due to changes in a related task

#40 Updated by riafarov 9 months ago

  • Related to action #42854: [functional][y][epic] Introduce relevant installation validation test modules added

#41 Updated by riafarov 9 months ago

  • Due date changed from 2019-10-22 to 2019-11-05

due to changes in a related task

#42 Updated by riafarov 8 months ago

  • Description updated (diff)

#43 Updated by riafarov 8 months ago

  • Description updated (diff)

#44 Updated by riafarov 8 months ago

  • Due date changed from 2019-11-05 to 2019-11-19

due to changes in a related task

#45 Updated by riafarov 8 months ago

  • Status changed from Workable to Resolved
  • Assignee set to riafarov

Resolving this one in favor of #42854
Those are too tightly coupled.

Also available in: Atom PDF