action #75319
Updated by szarate over 3 years ago
## Observation For many tests that use `consoletest` as a parent module, which don't rely on the screen, and don't use key combinations like `ctrl+d` or `ctrl+c`, we could save a lot of time and typing failures by switching to the more reliable `serial_terminal` which, when is not available for a particular backend, will simple default to the root console. A good starting point would be the modules scheduled in the `textmode` scenarios. ## # Tasks * In the textmode scenarios, see which modules are inheriting from `consoletest` that don't rely on assert_screen or key combinations * Replace the `select_console 'root-console';` call for a `$self->select_serial_terminal;` call, on the list of modules given by the previous search ## AC * All modules within the textmode scenarios are using serial terminal when possible. * Those modules inheriting form consoletest, that can't use the serial terminal, are mentioned in this ticket openQA test in scenario sle-15-SP3-Online-aarch64-wsm+dev_tools+textmode@aarch64 fails in [apache_ssl](https://openqa.suse.de/tests/4883833/modules/apache_ssl/steps/10) ## Test suite description Maintainer: dheidler - Run php tests for Web Scripting Module ## Reproducible Fails since (at least) Build [54.1](https://openqa.suse.de/tests/4795120) ## Expected result Last good: [53.2](https://openqa.suse.de/tests/4794738) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=aarch64&distri=sle&flavor=Online&machine=aarch64&test=wsm%2Bdev_tools%2Btextmode&version=15-SP3)