action #124610
coordination #121876: [epic] Handle openQA review failures in Yam squad - SLE 15 SP5
Catch regression when sending right key when switching to tab Bootloader Options in ncurses
0%
Description
Motivation¶
Catch regression when sending right key when switching to tab Bootloader Options in ncurses
Related ticket: https://progress.opensuse.org/issues/124430
Related bug: https://bugzilla.suse.com/show_bug.cgi?id=1208266
In Yam job group we run https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/installation/bootloader_settings/disable_boot_menu_timeout.pm
which is using libyui-rest-api which interact directly with the UI widget via some id, and not sending keys.
To catch this regression we could create a new test module with similar functionality than disable_boot_menu_timeout but navigating right using testapi, so it will be an hybrid. This will enable other squad to move to AutoYaST having piece of mind that this test case is covered.
Anyway this kind of testing is a corner case, just with the introspection provided by the libyui-rest-api we can catch most of the stuff, but it is true that we should maintain some basic testing with needles and shortcuts using testapi, for that in Yam job group we have the off-line installation and some multi-machine scenario which do not work with libyui-rest-api.
This only happens in textmode (ncurses) and the offline scenario runs in qt, but we shouldn't create new test suite for it, but incorporate it in existing test coverage.
Acceptance criteria¶
AC1: Create new test module which use libyui-rest-api for everything except for that step to go 'right'
AC2: Enable this test module in some existing textmode scenario in YaST job group
AC3: Enable this test module in some existing textmode scenario in Staging job group #124676
Related issues
History
#1
Updated by JERiveraMoya 3 months ago
- Related to action #124430: Right key doesn't reach the SUT when switching to tab Bootloader Options added
#2
Updated by JERiveraMoya 3 months ago
- Description updated (diff)
#3
Updated by JERiveraMoya 3 months ago
- Description updated (diff)
#5
Updated by tinawang123 3 months ago
- Assignee set to tinawang123
#6
Updated by tinawang123 3 months ago
- Status changed from Workable to In Progress
#8
Updated by JERiveraMoya 3 months ago
- Priority changed from Normal to High
#9
Updated by JERiveraMoya 2 months ago
Current build or the next should contain the fix:
https://bugzilla.suse.com/show_bug.cgi?id=1208266
#10
Updated by JERiveraMoya about 2 months ago
I checked Kernel changelog in the installed system and contained the commit mentioned in SR,
therefore I reopened the P1.
#11
Updated by JERiveraMoya about 1 month ago
- Priority changed from High to Normal
#12
Updated by tinawang123 13 days ago
- Status changed from In Progress to Resolved