Project

General

Profile

Actions

coordination #33859

open

[qe-core][sles][functional][saga][s390x] Review s390x Bugs found by IBM and see what can be implemented in the future

Added by mgriessmeier over 6 years ago. Updated over 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
New test
Target version:
SUSE QA (private) - Milestone 32
Start date:
2018-03-27
Due date:
% Done:

100%

Estimated time:
(Total: 10.00 h)
Difficulty:

Description

User Story

In late february coolo and me were visiting the IBM Regression Testing team in Böblingen to talk about test coverage and unification of our testcase into openQA.
There were two main topics in this meeting. One was about how we can integrate the automated testcases conducted by IBM into openQA (this discussion is still ongoing).

The second, more relevant topic atm, was to talk about Bugs in SLE* which were found by IBM and to see which of the executed scenarios are covered on our side and which are not. It turned out that we lack a lot of test-scenarios and therefore missed some bugs in the product

This ticket is about to collect all those bugs and act on them by creating subtasks for implementing those scenarios step-by-step

Further information

using tags to define those further:

  • [INFRA] - needs to be clarified with Ihno or Gerhard, e.g. Hardware component/setup on system level is missing, blocks other tags
  • [YAST] - Affecting a YaST module, extending YaST module tests for s390x
  • [MANUAL] - Can be verified manually in first place
  • [AUTOMATE] - eligible for being automated in the future
  • [FIXED] - bug is verified fixed

Network

Access & Package*

System hangs

Devices

Others


Subtasks 5 (0 open5 closed)

coordination #33862: [sles][functional][epic][s390x][yast][y] Review and extend test coverage of YaST2 modules on s390x Resolvedriafarov2018-03-27

Actions
action #33865: [sles][functional][s390x][easy][y] Enable yast2_ncurses testsuite for s390xResolvedriafarov2018-03-27

Actions
coordination #37315: [sle][functional][s390x][yast][y] Review and extend test coverage of YaST2 modules on s390x - epic end trackerRejectedriafarov2018-06-13

Actions
action #39344: [functional][y][s390] create new test suite for yast dump moduleResolvedJRivrain2018-08-08

Actions
action #54239: [functional][y][s390x] test fails in yast2_lan_restart_devices: bond slaves doesn't show any entriesResolvedriafarov2019-07-15

Actions

Related issues 1 (0 open1 closed)

Related to openQA Tests (public) - action #11922: [sle][functional][s390][yast][y][hard] Add AutoYaST tests for s390Resolvedriafarov2016-05-112018-04-24

Actions
Actions #2

Updated by mgriessmeier over 6 years ago

note that this user story is not fully described yet

Actions #3

Updated by mgriessmeier over 6 years ago

  • Description updated (diff)
Actions #4

Updated by mgriessmeier over 6 years ago

  • Related to action #11922: [sle][functional][s390][yast][y][hard] Add AutoYaST tests for s390 added
Actions #5

Updated by mgriessmeier over 6 years ago

  • Due date set to 2018-04-10

due to changes in a related task

Actions #6

Updated by okurz over 6 years ago

  • Subject changed from [sles][functional][saga][s390x] Review s390x Bugs found by IBM and see what can be implemented in the future to [sles][functional][saga][s390x][u] Review s390x Bugs found by IBM and see what can be implemented in the future
Actions #7

Updated by mgriessmeier over 6 years ago

  • Description updated (diff)
Actions #8

Updated by okurz over 6 years ago

  • Due date changed from 2018-07-03 to 2018-12-31

due to changes in a related task

Actions #9

Updated by okurz over 6 years ago

  • Target version changed from Milestone 21+ to Milestone 21+
Actions #10

Updated by okurz almost 6 years ago

  • Status changed from New to Blocked
  • Assignee set to okurz
  • Target version changed from Milestone 21+ to Milestone 25

-> #33862

Actions #11

Updated by okurz over 5 years ago

  • Assignee changed from okurz to mgriessmeier

@mgriessmeier to track as stand-in as discussed.

Actions #12

Updated by riafarov over 5 years ago

  • Due date changed from 2019-06-30 to 2019-07-23

due to changes in a related task

Actions #13

Updated by mgriessmeier over 5 years ago

  • Target version changed from Milestone 25 to Milestone 26
Actions #14

Updated by riafarov over 5 years ago

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

due to changes in a related task

Actions #15

Updated by riafarov over 5 years ago

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

due to changes in a related task

Actions #16

Updated by mgriessmeier over 5 years ago

  • Target version changed from Milestone 26 to Milestone 27

ongoing

Actions #17

Updated by mgriessmeier over 5 years ago

removed due date to prevent email spam

Actions #18

Updated by riafarov over 5 years ago

  • Due date changed from 2019-09-24 to 2019-06-30

due to changes in a related task

Actions #19

Updated by riafarov over 5 years ago

  • Due date changed from 2019-06-30 to 2020-02-04

due to changes in a related task

Actions #20

Updated by mgriessmeier about 5 years ago

  • Target version changed from Milestone 27 to Milestone 29
Actions #21

Updated by mgriessmeier almost 5 years ago

  • Target version changed from Milestone 29 to Milestone 32
Actions #22

Updated by riafarov almost 5 years ago

  • Due date changed from 2020-02-04 to 2020-04-07

due to changes in a related task

Actions #23

Updated by riafarov over 4 years ago

  • Due date changed from 2020-04-07 to 2021-01-12

due to changes in a related task

Actions #24

Updated by SLindoMansilla over 4 years ago

  • Assignee changed from mgriessmeier to SLindoMansilla
Actions #25

Updated by SLindoMansilla over 4 years ago

  • Due date changed from 2021-01-12 to 2018-03-27

due to changes in a related task: #33862

Actions #26

Updated by SLindoMansilla over 4 years ago

  • Due date set to 2021-01-12

due to changes in a related task: #33862

Actions #27

Updated by szarate about 4 years ago

  • Tracker changed from action to coordination
  • Status changed from Blocked to New
Actions #29

Updated by tjyrinki_suse about 4 years ago

  • Subject changed from [sles][functional][saga][s390x][u] Review s390x Bugs found by IBM and see what can be implemented in the future to [qe-core][sles][functional][saga][s390x] Review s390x Bugs found by IBM and see what can be implemented in the future
Actions #30

Updated by SLindoMansilla over 3 years ago

  • Assignee deleted (SLindoMansilla)

No time to work on this :(

Actions #31

Updated by slo-gin over 2 years ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions

Also available in: Atom PDF