Project

General

Profile

action #42854

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

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

Status:
In Progress
Priority:
Normal
Assignee:
Category:
New test
Target version:
SUSE QA tests - SLE 15 SP3
Start date:
2018-10-24
Due date:
2020-07-28
% Done:

80%

Estimated time:
(Total: 52.00 h)
Difficulty:
Duration: 460

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 space tests in lvm_thin_provisioningResolvedriafarov

action #42917: [sle][functional][y] Introduce only relevant tests modules for USBinstall test suiteResolvedJERiveraMoya

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_existingResolvedybonatakis

action #64911: [functional][y] Validate only relevant parts of lvm+resize_rootResolvedybonatakis

action #65349: [functional][y][timeboxed:16h] Add validation module for nis mm testsResolvedsyrianidou_sofia

action #67126: [functional][y] Add validation module for nis mm testsResolvedsyrianidou_sofia

action #67579: [functional][y] Add validation for addon-module-http and addon-module-ftpResolvedriafarov

action #68386: [functional][y] Add validation for cryptlvm+activate_existing+import_users ResolvedJERiveraMoya

action #68398: [functional][y] Add validation for autoyast_lvmIn ProgressJRivrain

action #68773: [functional][y] Add validation for autoyast_miniFeedbackJERiveraMoya

action #68803: [functional][y] Add validation for autoyast_reinstallNew


Related issues

Related to openQA Tests - action #42494: [epic][functional][y] Split/adapt scenarios to move installer related part to YaST specific job groupResolved2018-10-252019-11-19

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

  • Is duplicate of 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

  • Is duplicate of 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 2018-12-04 to 2018-12-18

due to changes in a related task

#7 Updated by JERiveraMoya over 1 year ago

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

due to changes in a related task

#8 Updated by riafarov over 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 about 1 year ago

  • Target version changed from Milestone 25 to Milestone 27

#10 Updated by riafarov 12 months ago

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

due to changes in a related task

#11 Updated by riafarov 12 months ago

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

due to changes in a related task

#12 Updated by riafarov 11 months ago

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

due to changes in a related task

#13 Updated by riafarov 11 months ago

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

due to changes in a related task

#14 Updated by riafarov 10 months ago

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

due to changes in a related task

#15 Updated by mgriessmeier 10 months ago

  • Target version changed from Milestone 27 to Milestone 28

#16 Updated by JERiveraMoya 10 months ago

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

due to changes in a related task

#17 Updated by riafarov 9 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 9 months ago

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

due to changes in a related task

#19 Updated by riafarov 9 months ago

  • Target version changed from Milestone 28 to Milestone 30+

#20 Updated by riafarov 8 months ago

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

due to changes in a related task

#21 Updated by riafarov 8 months ago

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

due to changes in a related task

#22 Updated by riafarov 7 months ago

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

due to changes in a related task

#23 Updated by mgriessmeier 6 months ago

  • Target version changed from Milestone 30+ to Milestone 30

bulk moved to M30 for revisiting

#24 Updated by riafarov 5 months ago

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

due to changes in a related task

#25 Updated by riafarov 3 months ago

  • Due date changed from 2020-04-21 to 2020-05-05

due to changes in a related task: #64911

#26 Updated by riafarov 2 months ago

  • Due date changed from 2020-05-19 to 2020-06-02

due to changes in a related task: #65349

#27 Updated by riafarov about 2 months ago

  • Status changed from New to In Progress
  • Assignee set to riafarov
  • Target version changed from Milestone 30 to SLE 15 SP2

#28 Updated by riafarov about 2 months ago

  • Parent task deleted (#40475)

#29 Updated by riafarov about 1 month ago

  • Due date changed from 2020-06-02 to 2020-06-16

due to changes in a related task: #67579

#30 Updated by riafarov about 1 month ago

  • Due date changed from 2020-06-16 to 2020-06-30

due to changes in a related task: #67579

#31 Updated by riafarov 17 days ago

  • Due date changed from 2020-06-30 to 2020-07-14

due to changes in a related task: #68386

#32 Updated by riafarov 2 days ago

  • Target version changed from SLE 15 SP2 to SLE 15 SP3

#33 Updated by riafarov 2 days ago

  • Due date changed from 2020-07-14 to 2020-07-28

due to changes in a related task: #68773

Also available in: Atom PDF