Project

General

Profile

Actions
Copy link

coordination #53015

closed

[epic][functional][y] Test multidevice btrfs support

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

Status:
Resolved
Priority:
High
Assignee:
riafarov
Category:
New test
Target version:
SUSE QA - Milestone 30
Start date:
2019-06-13
Due date:
2020-01-14
% Done:

100%

Estimated time:
(Total: 29.00 h)
Difficulty:

Description

Motivation

We got feature implemented and would like to test this and come up with scenarios to automate.

More details about the feature can be found here:
https://github.com/yast/yast.github.io/issues/189
https://github.com/yast/yast-storage-ng/pull/926
https://jira.suse.com/browse/SLE-3877

Acceptance criteria

  1. Feature is tested manually
  2. Draft test plan for the feature is created
  3. At least AY installation with new functionality is automated with validation in openQA for affected products

NOTE: feature is available in TW and in updates SLE 15 SP1.

Subtasks 5 (0 open — 5 closed)

action #53024: [functional][y][research] Integration testing of multidevice btrfs featureResolvedoorlov2019-06-132019-07-30

Actions
action #54683: [functional][y][research][SLE-3877][timeboxed:20h] Integration testing of multidevice btrfs feature in SLESResolvedJERiveraMoya2019-06-132019-10-08

Actions
action #57668: [functional][y] Automate installation with multidevice btrfs (openSUSE only)Resolvedoorlov2019-10-032019-11-19

Actions
action #58265: [functional][y] Automate installation with multidevice btrfs (SLE 15 SP2 only)Resolvedoorlov2019-10-032019-11-19

Actions
action #60002: [functional][y] Add validation module to check cloned system xml with AutoYaST for multidevice btrfs scenarioResolvedJERiveraMoya2019-11-192020-01-14

Actions
Actions
Copy link
 #1

Updated by riafarov almost 5 years ago

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

due to changes in a related task

Actions
Copy link
 #2

Updated by riafarov almost 5 years ago

  • Status changed from New to Workable
Actions
Copy link
 #3

Updated by riafarov over 4 years ago

  • Due date changed from 2019-07-30 to 2019-11-19

due to changes in a related task

Actions
Copy link
 #4

Updated by riafarov over 4 years ago

  • Due date changed from 2019-11-19 to 2019-10-08

due to changes in a related task

Actions
Copy link
 #5

Updated by riafarov over 4 years ago

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

due to changes in a related task

Actions
Copy link
 #6

Updated by riafarov over 4 years ago

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

due to changes in a related task

Actions
Copy link
 #7

Updated by riafarov over 4 years ago

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

due to changes in a related task

Actions
Copy link
 #8

Updated by riafarov over 4 years ago

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

due to changes in a related task

Actions
Copy link
 #9

Updated by mgriessmeier over 4 years ago

  • Target version changed from Milestone 30+ to Milestone 30

bulk moved to M30 for revisiting

Actions
Copy link
 #10

Updated by JERiveraMoya over 4 years ago

  • Due date changed from 2019-12-31 to 2020-01-14

due to changes in a related task

Actions
Copy link
 #11

Updated by riafarov over 4 years ago

  • Status changed from Workable to Resolved

Good job, everyone.

Actions
Copy link
 #12

Updated by szarate over 3 years ago

  • Tracker changed from action to coordination
Actions
Copy link

Also available in: Atom PDF