action #41546

[functional][y] Change architecture checks with functionality of the #33388 to detect VNC installation

Added by riafarov over 1 year ago. Updated about 1 year ago.

Status:WorkableStart date:25/09/2018
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Enhancement to existing testsEstimated time:3.00 hours
Target version:QA - future
Difficulty:
Duration:

Description

Motivation

Outcome of discussion in the PR:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/5806#discussion_r220089043

To enable yast2_vnc on s390x we checked for architecture, even though, it should be the same path for any remote VNC connection.
Not to forget where to apply the solution, we have this ticket.

Acceptance criteria

  1. VNC based tests are detected in generic way and arch variable is not used in yast2_vnc

Related issues

Related to openQA Tests - action #39332: [functional][y][easy] adjust or disable yast2_vnc for s390x Resolved 08/08/2018 09/10/2018
Blocked by openQA Tests - action #33388: [functional][u][easy][pvm] Implement proper split from ot... Resolved 17/02/2019

History

#1 Updated by riafarov over 1 year ago

  • Parent task deleted (#33388)

#2 Updated by riafarov over 1 year ago

  • Blocked by action #33388: [functional][u][easy][pvm] Implement proper split from other backends added

#3 Updated by coolo over 1 year ago

  • Project changed from openQA Project to openQA Tests

#4 Updated by okurz over 1 year ago

  • Category set to Enhancement to existing tests

#5 Updated by JERiveraMoya over 1 year ago

  • Related to action #39332: [functional][y][easy] adjust or disable yast2_vnc for s390x added

#6 Updated by okurz over 1 year ago

  • Due date set to 06/11/2018

#7 Updated by riafarov over 1 year ago

  • Estimated time set to 3.00

#8 Updated by riafarov over 1 year ago

  • Due date deleted (06/11/2018)

No capacity in S29

#9 Updated by okurz about 1 year ago

  • Target version changed from Milestone 20 to future

Also available in: Atom PDF