action #43289: [sle][functional][y] test fails in yast2_proxy - test does not reach correct record in Access Control Settings - openQA Tests (public) - openSUSE Project Management Tool

Actions

Copy link

action #43289

closed

coordination #39329: [sles][functional][s390x][y][epic] FIx yast2_ncurses testsuite for s390x

[sle][functional][y] test fails in yast2_proxy - test does not reach correct record in Access Control Settings

Added by mloviska about 6 years ago. Updated about 6 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

oorlov

Category:

Bugs in existing tests

Target version:

SUSE QA (private) - Milestone 21

Start date:

2018-11-02

Due date:

2018-11-20

% Done:

Estimated time:

5.00 h

Difficulty:

Description

Observation¶

openQA test in scenario sle-15-SP1-Installer-DVD-s390x-yast2_ncurses@s390x-kvm-sle12 fails in
yast2_proxy

Test does not reach the correct record because it was not ordered as third from the top as it is https://openqa.suse.de/tests/2231325#step/yast2_proxy/123.
It looks like needle https://openqa.suse.de/tests/2233072#step/yast2_proxy/136 is not correctly created since, it would match a record which is not selected/highlighted by yast2.

Acceptance criteria¶

yast2_proxy_acl_group_localnet-20181105, yast2_proxy_access_control_new-20181105 and yast2_proxy_acl_group_localnet-20180313 needles are removed and not used anymore
code is adjusted that correct entry is selected regardless of it's position in the list

Reproducible¶

Fails since (at least) Build 71.2

Expected result¶

https://openqa.suse.de/tests/2231325#step/yast2_proxy/123

Further details¶

Always latest result in this scenario: latest

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by okurz about 6 years ago

Subject changed from [sle][autoyast][functional] test fails in yast2_proxy - test does not reach correct record in Access Control Settings to [sle][autoyast][functional][y] test fails in yast2_proxy - test does not reach correct record in Access Control Settings
Target version set to Milestone 21

clearly y-team ticket, right?

Actions

Copy link

Updated by riafarov about 6 years ago

Subject changed from [sle][autoyast][functional][y] test fails in yast2_proxy - test does not reach correct record in Access Control Settings to [sle][functional][y] test fails in yast2_proxy - test does not reach correct record in Access Control Settings
Description updated (diff)
Status changed from New to Workable

I've created needles as before, so test passes now, but this part, as correctly stated by Martin is written in a way that it won't scale:

  # change subnet for 192.168.0.0/16 to 192.168.0.0/18
     wait_screen_change { send_key 'tab'; };
     wait_screen_change { send_key 'down'; };
     wait_screen_change { send_key 'down'; };
     assert_screen 'yast2_proxy_acl_group_localnet';

Actions

Copy link