action #13702
closedtests can fail when typing too long scripts in one go
0%
Description
observation¶
see in http://lord.arch/tests/4810#step/hostname/14
the long line in tests/console/hostname.pm
assert_script_run "if systemctl -q is-active network.service; then systemctl reload-or-restart network.service; fi";
is typed incompletely. I am running the same tests over and over again in hunt for a different issue and the reported issue seems to happen in 2 out of currently about 30 runs.
problem¶
The string to type is too long without intermediate waiting which can cause the typing to be incomplete.
suggestion¶
Split up super long strings and ensure they are written out before continuing to type, e.g. as we do in type_string_very_slow. Also https://github.com/os-autoinst/os-autoinst/pull/584 could help.
Updated by okurz over 7 years ago
- Project changed from openQA Tests to openQA Project
Updated by coolo over 7 years ago
the problem is that wait_screen_change does not help here. Let's assume you type 20 characters and wait for the screen change - which would succeed after the 6th character. And then you continue...
Updated by okurz@suse.de over 7 years ago
Well, I didn't expect wait_screen_change to help, rather something like the echoing of characters. How would a human user do it? He would wait for the echoing. What about an implicit wait_still_screen(1) after every 30 characters? In most cases it would not hit at all as we type less
Updated by coolo over 7 years ago
well, waiting for the echo is easier if you have proper OCR - as humans happen to have ;)
Updated by coolo over 6 years ago
- Status changed from New to Resolved
we have measures to do that in type_string now - not by default though