Project

General

Profile

Actions
Copy link

coordination #39329

closed

[sles][functional][s390x][y][epic] FIx yast2_ncurses testsuite for s390x

Added by riafarov over 6 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
riafarov
Category:
New test
Target version:
SUSE QA (private) - Milestone 21
Start date:
2018-08-08
Due date:
2018-11-20
% Done:

100%

Estimated time:
(Total: 9.00 h)
Difficulty:

Description

User story

We want to check how yast modules behave on s390x. However, tests require adjustments: https://openqa.suse.de/tests/1897521#settings

yast2_proxy required just needles updates, but for failing vnc test seems that we have different behavior. As tests after vnc were not executed, most likely, other test modules will fail.

Acceptance Criteria

AC1: yast2_ncurses testsuite is running on o.s.d in functional

Subtasks 4 (0 open — 4 closed)

action #39332: [functional][y][easy] adjust or disable yast2_vnc for s390xResolvedJERiveraMoya2018-08-082018-10-09

Actions
action #42122: [functional][y][fast] adjust yast2_nis test module to be executed on s390xResolvedoorlov2018-10-082018-10-23

Actions
action #42692: [functional][y][sporadic] Stabilize yast2_http yast2_samba yast2_ftp yast2_vnc yast2_nis test suite on s390x for SLE 12Resolvedriafarov2018-10-182018-11-20

Actions
action #43289: [sle][functional][y] test fails in yast2_proxy - test does not reach correct record in Access Control SettingsResolvedoorlov2018-11-022018-11-20

Actions

Related issues 1 (0 open — 1 closed)

Copied from openQA Tests (public) - action #33865: [sles][functional][s390x][easy][y] Enable yast2_ncurses testsuite for s390xResolvedriafarov2018-03-27

Actions
Actions
Copy link
 #1

Updated by riafarov over 6 years ago

  • Copied from action #33865: [sles][functional][s390x][easy][y] Enable yast2_ncurses testsuite for s390x added
Actions
Copy link
 #2

Updated by riafarov over 6 years ago

  • Due date set to 2018-08-28

due to changes in a related task

Actions
Copy link
 #3

Updated by okurz over 6 years ago

  • Due date changed from 2018-08-28 to 2018-09-25

due to changes in a related task

Actions
Copy link
 #4

Updated by okurz over 6 years ago

  • Target version changed from Milestone 18 to Milestone 19
Actions
Copy link
 #5

Updated by riafarov about 6 years ago

  • Due date changed from 2018-09-25 to 2018-10-09

due to changes in a related task

Actions
Copy link
 #6

Updated by okurz about 6 years ago

  • Target version changed from Milestone 19 to Milestone 21
Actions
Copy link
 #7

Updated by oorlov about 6 years ago

  • Due date changed from 2018-11-06 to 2018-10-23

due to changes in a related task

Actions
Copy link
 #8

Updated by riafarov about 6 years ago

  • Status changed from New to Resolved
Actions
Copy link
 #9

Updated by okurz about 6 years ago

  • Assignee set to riafarov

you did the "Resolved", you can take the credits :)

Actions
Copy link
 #10

Updated by szarate about 4 years ago

  • Tracker changed from action to coordination
Actions
Copy link

Also available in: Atom PDF