Project

General

Profile

Actions
Copy link

action #64911

closed

coordination #42854: [functional][y][epic] Introduce relevant installation validation test modules

[functional][y] Validate only relevant parts of lvm+resize_root

Added by riafarov almost 5 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
ybonatakis
Target version:
SUSE QA (private) - Milestone 33
Start date:
2020-03-27
Due date:
2020-05-05
% Done:

0%

Estimated time:
5.00 h

Description

See parent ticket for motivation

From the video
https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=64bit&test=lvm%2Bresize_root&version=15-SP2#step/partitioning_resize_root/13

we don't really resize partition, so we should fix the test

Acceptance criteria

  1. Only relevant modules are scheduled in lvm+resize root test scenario
  2. Test suite actually resizes root partition
  3. Partitioning is validated in the end of the installation
  4. Description of the test scenario is updated in the test plan
Actions
Copy link
 #1

Updated by riafarov almost 5 years ago

  • Description updated (diff)
  • Status changed from New to Workable
  • Estimated time set to 5.00 h
Actions
Copy link
 #2

Updated by ybonatakis almost 5 years ago

  • Status changed from Workable to In Progress
  • Assignee set to ybonatakis
Actions
Copy link
 #4

Updated by riafarov almost 5 years ago

  • Due date changed from 2020-04-21 to 2020-05-05
Actions
Copy link
 #5

Updated by ybonatakis almost 5 years ago

scheduler is created with minimizing the modules to the relevant ones and validation of the partitioning was added. Now the run_expert_partitioner can take a parameter to indicate which ExpertPartitioner Option wants to select. Another thing which modified is the call of accept_changes. the method mixed the Accept button with the combination of the Next Button to terminate the configuration and go on. however there were methods that do not end with the same logic. so two methods accept_changes and accept_changes_and_press_next will distinguish the expected action in any case.

Actions
Copy link
 #6

Updated by ybonatakis almost 5 years ago

  • Status changed from In Progress to Feedback
Actions
Copy link
 #7

Updated by ybonatakis almost 5 years ago

TODO: update TS with YAML_SCHEDULER

Actions
Copy link
 #8

Updated by ybonatakis almost 5 years ago

  • Status changed from Feedback to In Progress
Actions
Copy link
 #9

Updated by ybonatakis almost 5 years ago

  • Status changed from In Progress to Feedback

YAML_SCHEDULE=schedule/yast/lvm/lvm+resize_root.yaml added to the TS and wait for validation

Actions
Copy link
 #10

Updated by ybonatakis almost 5 years ago

i have removed the needle that was causing the problem. we need to recreate it properly, however to not break https://openqa.suse.de/tests/4088415

Actions
Copy link
 #12

Updated by ybonatakis almost 5 years ago

  • Status changed from Feedback to Resolved

everything seems to go smoothly. resolve this

Actions
Copy link

Also available in: Atom PDF