action #56777
closed
coordination #56267: [epic][qe-core][functional] openSUSE welcome message is not properly handled
[functional][u] test fails in installation - openSUSE Welcome not handled in installation module after autoyast
Added by StefanBruens over 4 years ago.
Updated over 4 years ago.
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 28
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-autoyast_gnome@64bit fails in
installation
Acceptance criteria¶
- AC1: There is a function to check and close the openSUSE welcome popup when a user logs in in a graphical session.
- AC2: The function is properly used in scenario opensuse-Tumbleweed-DVD-x86_64-autoyast_gnome@64bit (this removes urgency)
- AC3: The function is properly used in any openSUSE scenario where a user logs in in a graphical session (Tumbleweed, JeOS, KDE, GNOME, IceWM, etc)
Tasks¶
- Create the function as opensusebasetest.pm method.
Reproducible¶
Fails since (at least) Build 20190909 (current job)
Expected result¶
Last good: 20190907 (or more recent)
Further details¶
Always latest result in this scenario: latest
- Subject changed from test fails in installation - openSUSE Welcome not handled to [functional][u] test fails in installation - openSUSE Welcome not handled in installation module after autoyast
- Parent task set to #56267
- Related to action #38423: [sle][functional][u][hard] Refactor first_boot to unify duplicated behavior for remote backend added
The module installation is doing both the work of wait_install and first_boot. If the behavior would have been done separately, the issue could be resolved by just scheduling the module opensuse_welcome.
- Priority changed from Normal to High
- Description updated (diff)
- Status changed from New to Workable
- Priority changed from High to Urgent
- Target version set to Milestone 28
- Estimated time set to 42.00 h
- Status changed from Workable to In Progress
- Assignee set to zluo
- Priority changed from Urgent to High
take over and check current status.
- Priority changed from High to Urgent
restart some autoyast tests on o3 and check these test results later.
- Status changed from In Progress to Resolved
- Priority changed from Urgent to High
- Status changed from Resolved to Workable
Acceptance criteria are not fulfilled.
It is a matter of time until another module in another scenario fails again and then we have a lot of microcode spread on every module for graphical session. Just passing is not an option. We have also cases where other needles fail due to the window. Remember the click to close window when a background window matches in gnucash. And now we are are letting this race condition happen on any module.
The openSUSE welcome popup needs to be handled properly:
Closed the first time it appears with checkbox "Show on next startup" out.
In this autoyast scenario, this has to be handled here: http://f40.suse.de/tests/5270#step/installation/10
So that the popup doesn't appear in any of the following modules:
- Status changed from Workable to In Progress
- Status changed from In Progress to Feedback
- Status changed from Feedback to In Progress
- Status changed from In Progress to Feedback
- Status changed from Feedback to Resolved
Also available in: Atom
PDF