action #48074
closed[functional][y] test fails in yast2_hostnames
0%
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-DVD-aarch64-yast2_gui@aarch64 fails in
yast2_hostnames
Test suite description¶
Maintainer: zluo, riafarov
Test for yast2 UI, GUI only. Running on created gnome images which provides both text console for ncurses UI tests as well as the gnome environment for the GUI tests.
Temporarily added YAST2_GUI_TERMINATE_PREVIOUS_INSTANCES to see if helps. This variable triggers code which terminates all yast2 processes before starting new one. (see poo#26104).
Reproducible¶
Fails since (at least) Build 20190111
Expected result¶
Last good: 20181231 (or more recent)
Further details¶
Always latest result in this scenario: latest
It seems that Ok button is not validated as expected. (See cursor on downlo|ad-srv)
Updated by riafarov about 5 years ago
- Subject changed from test fails in yast2_hostnames to [functional][y] test fails in yast2_hostnames
- Due date set to 2019-03-12
Updated by okurz about 5 years ago
- Related to action #46232: [functional][y] test fails in yast2_hostnames - too tight grep pattern? added
Updated by okurz about 5 years ago
- Target version set to Milestone 23
Added oorlov as watcher.
@oorlov as you last changed the test module. Do you have an idea if this is a recent test regression?
Updated by ggardet_arm about 5 years ago
Leap 15.1 aarch64 is also affected: https://openqa.opensuse.org/tests/858173#step/yast2_hostnames/15
Updated by oorlov about 5 years ago
- Status changed from New to Feedback
- Assignee set to oorlov
I've checked the issue and found out that my changes did not relate to that fail.
Needle was changed on the 13th of February. 'yast2_hostnames_changed_ok' needle is used with 'assert_and_click' function. It should match just 'Ok' button by the current test design. But now it matches the changed fields. As a result it clicks on the wrong place in the dialog.
I've changed the needle for TW and Leap and restarted the jobs.
Updated by ggardet_arm about 5 years ago
Updated by oorlov about 5 years ago
Yes, I see. It is because I did not remove the wrong needles. They matched first. I'll remove them and restart the jobs again.
Updated by oorlov about 5 years ago
- Status changed from Feedback to Resolved
Passed on both Tumbleweed and Leap