action #113492: Create equivalent yast2_firewall test module based on libyui-rest-api - qe-yam - openSUSE Project Management Tool

Actions

Copy link

action #113492

closed

coordination #121885: [epic] Enable libyui-rest-api for YaST modules

Create equivalent yast2_firewall test module based on libyui-rest-api

Added by dimstar over 2 years ago. Updated about 2 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

coolgw

Target version:

Current

Start date:

2022-07-12

Due date:

% Done:

Estimated time:

Description

Observation¶

Originally filed as product bug for validation (https://bugzilla.suse.com/show_bug.cgi?id=1201054) but the conclusion is that the previous behavior was as unexpected as the new one.
So in any case, the test should be adjusted to perform the right thing.

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-yast2_gui@64bit fails in
yast2_firewall

Motivation¶

As it is recommended in the bug, we should consider here to create a separate version of this test module using libyui-rest-api.
The UI in this module is quite hard to test with shortcuts and needles.
This test module is mixing susefirewall2 with firewalld.
New qt version will reach soon SLE and other products when we will see the same failure. Seems that the \n triggers this different behavior.

Scope¶

Tumbleweed and SLE

Acceptance criteria¶

AC1: Create equivalent test module to yast2_firewall using libyui-rest-api with Pages needed.

Suggestions¶

Ignore the paths of code related with susefirewall2 when adapting the code.
Consider skip the Controller part of the design.

Actions

Copy link

Updated by maritawerner over 2 years ago

Project changed from openQA Tests (public) to qe-yam
Category deleted (~~Bugs in existing tests~~)

Actions

Copy link

Updated by openqa_review over 2 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: yast2_gui
https://openqa.opensuse.org/tests/2481996#step/yast2_firewall/1

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

The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
The openQA job group is moved to "Released" or "EOL" (End-of-Life)
The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions

Copy link

Updated by rainerkoenig over 2 years ago

Tags set to qe-yast-refinement

Actions

Copy link

Updated by JERiveraMoya over 2 years ago

Description updated (diff)
Target version set to Current

Actions

Copy link

Updated by JERiveraMoya over 2 years ago

Subject changed from Keyboard sequence not matching in yast2_firewall to Create equivalent yast2_firewall test module based on libyui-rest-api

Actions

Copy link