action #42854

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

[functional][y][epic] Introduce relevant installation validation test modules

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

Status:NewStart date:24/10/2018
Priority:HighDue date:21/04/2020
Assignee:-% Done:

86%

Category:New testEstimated time:31.00 hours
Target version:SUSE QA tests - Milestone 30
Difficulty:
Duration: 390

Description

Motivation

We have a lot of different scenarios, where we validate the setup using same or similar set of test suites, which indirectly assure functional properties of the system, but is not most efficient way.
For example, in INSTALL_ONLY test suites we only check that system can boot, which is already good, but misses validation of the part of the system which is different to the "default".
Could of examples: GPT test suite doesn't check partitioning table,
USBintstall should validate the only difference which is repo from mounted usb

Acceptance criteria

  1. All INSTALL_ONLY scenarios have relevant validation test module(s) for specific scenario enabled
  2. Default set of test modules (x11 and console tests) is executed only for some scenarios and relevant test modules are implemented to assure functional properties of the system

Subtasks

action #42848: [sle][functional][y] Do not trigger not relevant user spa...Resolvedriafarov

action #42917: [sle][functional][y] Introduce only relevant tests module...ResolvedJERiveraMoya

action #52418: [functional][y] Validate setup in lvm+RAID1 test suiteResolvedybonatakis

action #57794: [functional][y] Validate crypt_no_lvm test suiteResolvedJERiveraMoya

action #58909: [functional][y] Validate ext4 installationResolvedsyrianidou_sofia

action #58912: [functional][y] Validate gpt installationResolvedJRivrain

action #63328: [functional][y] Enable validation for cryptlvm+activate_e...Resolvedybonatakis

action #64911: [functional][y] Validate only relevant parts of lvm+resiz...In Progressybonatakis


Related issues

Related to openQA Tests - action #42494: [epic][functional][y] Split/adapt scenarios to move insta... Resolved 25/10/2018 19/11/2019

History

#1 Updated by okurz over 1 year ago

  • Category set to New test

Please try to always assign a category

#2 Updated by riafarov over 1 year ago

  • Duplicates action #42494: [epic][functional][y] Split/adapt scenarios to move installer related part to YaST specific job group added

#3 Updated by riafarov over 1 year ago

  • Duplicates deleted (action #42494: [epic][functional][y] Split/adapt scenarios to move installer related part to YaST specific job group)

#4 Updated by riafarov over 1 year ago

  • Blocked by action #42494: [epic][functional][y] Split/adapt scenarios to move installer related part to YaST specific job group added

#5 Updated by riafarov over 1 year ago

  • Target version changed from Milestone 22 to Milestone 25

We should proceed with split first as already address same motivation for the test scenarios. After that we should check if anything still remains.

#6 Updated by okurz over 1 year ago

  • Due date changed from 04/12/2018 to 18/12/2018

due to changes in a related task

#7 Updated by JERiveraMoya over 1 year ago

  • Due date changed from 18/12/2018 to 03/12/2018

due to changes in a related task

#8 Updated by riafarov about 1 year ago

  • Blocked by deleted (action #42494: [epic][functional][y] Split/adapt scenarios to move installer related part to YaST specific job group)

#9 Updated by riafarov 10 months ago

  • Target version changed from Milestone 25 to Milestone 27

#10 Updated by riafarov 9 months ago

  • Due date changed from 09/07/2019 to 30/07/2019

due to changes in a related task

#11 Updated by riafarov 8 months ago

  • Due date changed from 30/07/2019 to 13/08/2019

due to changes in a related task

#12 Updated by riafarov 8 months ago

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

due to changes in a related task

#13 Updated by riafarov 8 months ago

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

due to changes in a related task

#14 Updated by riafarov 7 months ago

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

due to changes in a related task

#15 Updated by mgriessmeier 7 months ago

  • Target version changed from Milestone 27 to Milestone 28

#16 Updated by JERiveraMoya 7 months ago

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

due to changes in a related task

#17 Updated by riafarov 6 months ago

  • Related to action #42494: [epic][functional][y] Split/adapt scenarios to move installer related part to YaST specific job group added

#18 Updated by riafarov 6 months ago

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

due to changes in a related task

#19 Updated by riafarov 6 months ago

  • Target version changed from Milestone 28 to Milestone 30+

#20 Updated by riafarov 5 months ago

  • Due date changed from 19/11/2019 to 03/12/2019

due to changes in a related task

#21 Updated by riafarov 5 months ago

  • Due date changed from 03/12/2019 to 17/12/2019

due to changes in a related task

#22 Updated by riafarov 4 months ago

  • Due date changed from 17/12/2019 to 28/01/2020

due to changes in a related task

#23 Updated by mgriessmeier 3 months ago

  • Target version changed from Milestone 30+ to Milestone 30

bulk moved to M30 for revisiting

#24 Updated by riafarov 2 months ago

  • Due date changed from 28/01/2020 to 11/02/2020

due to changes in a related task

Also available in: Atom PDF