QA » openQA Project » openQA Tests » qe-yam

Motivation¶

The mau-extratests-yast2ui testsuite is sometimes affected by bsc#1191112.
For now we should apply the same workaround that we used in poo#105046.

Scope¶

Affected modules are yast2_bootloader and yast2_instserver, currently scheduled in the mau-extratests-yast2ui_dev testsuite that runs in our development group

Acceptance criteria¶

AC1: Add workaround make the next screen visible in the affected areas
AC2: Reference bsc#1191112 as soft failure when applying the workaround

Suggestion¶

Send f10 to maximize and unmaximize the window n times, as done for example here. This forces the YaST screen to, at some point, refresh the proper content, and send_key_until_needlematch will match the needle then and succeed.
Care must be taken with send_key_until_needlematch, as the number of keys sent is one more than specified in the command arguments, so I would suggest you stick to odd numbers for the repetitions (eg 9 instead of 10 in the case of send_key_until_needlematch('yast2_control-center_wake-on-lan_overview', 'alt-f10', 9, 2);).
Otherwise the screen will not match because the window will be left maximized.

Further info¶

Fix the same problem if appear multiple times, but if it is a different issue, file a different ticket for it.
Since we have noticed this issue only for MU sp4, it might be worth it, at some point, to convert the mau-extratests-yast2ui testsuite to use libyui rest api. This would overstep the current refresh issue as the rest api would provide the correct screen information.
In that case this workaround would need to be reverted.