Project

General

Profile

Actions
Copy link

coordination #76861

closed

Adjust test code for the new partitioner UI

Added by riafarov over 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
riafarov
Target version:
SUSE QA - SLE 15 SP3
Start date:
2020-11-02
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)

Description

There are changes coming to the partitioner UI, including usage of the new bar widget:

We have RAID tests working already, so can be used:
https://openqa.opensuse.org/tests/1469868

The changes are described here (includes screenshots):
https://github.com/yast/yast-storage-ng/pull/1157

These are the corresponding SRs:
https://build.opensuse.org/request/show/845043
https://build.suse.de/request/show/229575

Some of them are already visible in the staging tests of tumbleweed.

Subtasks 15 (0 open — 15 closed)

action #76864: Adjust RAID test to the new UI changesClosedriafarov2020-11-02

Actions
action #77767: Adjust code for lvm+RAID1 scenario using libyui REST APIClosedriafarov2020-11-12

Actions
action #78007: Adjust partitioning_warnings for the UI changesResolvedoorlov2020-11-16

Actions
action #78016: Adjust tests for lvm-full-encrypt scenarioClosedJERiveraMoya2020-11-16

Actions
action #78088: Adjust lvm-encrypt-separate-boot test suite for the Expert Partitioner UI changesClosedJERiveraMoya2020-11-16

Actions
action #78091: Adjust lvm_thin_provisioning test for the UI changes in Expert PartitionerResolvedsyrianidou_sofia2020-11-17

Actions
action #78097: Adjust modify_existing_partition for the UI changesClosedriafarov2020-11-17

Actions
action #78100: Adjust split_usr scenario for the UI changes in the Expert PartitionerClosedJERiveraMoya2020-11-17

Actions
action #80204: Adjust lvm+resize_root scenario for the UI changes in the Expert PartitionerClosedriafarov2020-11-23

Actions
action #80206: Adjust msdos scenario for the UI changes in the Expert PartitionerClosedJRivrain2020-11-23

Actions
action #80216: Adjust home_encrypted scenario for the UI changes in the Expert PartitionerResolvedsyrianidou_sofia2020-11-23

Actions
action #80272: Adapt yast2_expert_partitioner (before: yast2_storage_ng) in ppc64le to use libyuiClosedJERiveraMoya2020-11-24

Actions
action #80636: yast2-storage-ng now shows a summary when exitingClosedJERiveraMoya2020-12-01

Actions
action #80766: Adjust detect_yast2_failures for the UI changes in the Expert PartitionerResolvedsyrianidou_sofia2020-12-07

Actions
action #80840: Implement setup for libyui REST API in the running systemClosedJERiveraMoya2020-12-08

Actions
Actions
Copy link
 #1

Updated by okurz over 3 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: btrfs+warnings
https://openqa.opensuse.org/tests/1475759

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #2

Updated by riafarov over 3 years ago

  • Description updated (diff)
Actions
Copy link
 #3

Updated by okurz over 3 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: btrfs+warnings
https://openqa.opensuse.org/tests/1534044

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #4

Updated by okurz over 3 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: btrfs+warnings
https://openqa.opensuse.org/tests/1587215

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #5

Updated by riafarov about 3 years ago

  • Status changed from New to Closed
Actions
Copy link

Also available in: Atom PDF