QA (public) » openQA Project (public) » openQA Tests (public) » qe-yam

Motivation¶

During the review of maintenance job group, we found the yast2 keyboard test failed when run keyboard with non-root user,
https://openqa.suse.de/tests/10096569#step/yast2_keyboard/32

check_screen("yast2-keyboard-ui", 5) sometimes the 5s is not enough, we can increase it to fix the issue.

[2022-12-07T02:43:45.230084+01:00] [debug] >>> testapi::_check_backend_response: match=yast2-keyboard-ui timed out after 5 (check_screen)
[2022-12-07T02:43:45.268607+01:00] [debug] tests/yast2_gui/yast2_keyboard.pm:86 called testapi::enter_cmd
[2022-12-07T02:43:45.268986+01:00] [debug] <<< testapi::type_string(string="exit\n", max_interval=250, wait_screen_change=0, wait_still_screen=0, timeout=30, similarity_level=47)
[2022-12-07T02:43:45.446326+01:00] [debug] tests/yast2_gui/yast2_keyboard.pm:87 called testapi::assert_screen
[2022-12-07T02:43:45.446724+01:00] [debug] <<< testapi::assert_screen(mustmatch="generic-desktop", timeout=90)

An increase of timeout seems the best candidate to fix the instability, but consider other option if this doesn't succeed.
libyui-rest-api doesn't apply here because the scope seems to be SLE 12 SP{4,5] where is not available.
Another consideration could be to avoid using gedit and open the module again and use the field 'Test' to test the current keyboard if that would simplify the flow and would make it more stable, but it is not needed if it is probe with 5,10 verification that is stable with the change of timeout.

Acceptance criteria¶

AC1: Make stable test yast2 keyboard