action #122695
Updated by JERiveraMoya over 1 year ago
#### Motivation Despite Yam squad already have some test module that partially test some of the tabs in this YaST module, the idea is automate a clear user journey, so instead of doing some necessary actions via command line Yam squad will automate the very same actions via UI plus some additional check in the screen to verify that the module read properly the expected configuration and the validation of the fields that were changed. One On simple test going through Boot Code Options, Kernel Parameters and Booloader Options that will cover basic actions for all the architectures in ALP. The test case could just be implemented in a single test module with three blocks of code 1 - Verify with libyui-rest-api Boot Loader Settings: navigate through the 3 tabs verifying each option. Regarding why is efi for both machines, please read https://suse.slack.com/archives/C02A9423SRY/p1672908919913109 Probably we just need to enable this test for uefi, but let's see what is the answer... Notice that in [alp_default@uefi](https://openqa.opensuse.org/tests/2958575) after booting we start to do some configuration via command line, therefore for this scenario we will not run `transactional/host_config` (or at least some parts or it, so we can do similar actions that this module does but with the UI). 2 - Perform some actions with the module: 2.1 Nothing to change in Boot Code Options as only GRUB2 for EFI is a valid option for ALP 2.2 In Kernel parameters tab, go to Console resolution and select 1024x768 2.3 In Bootloader Options, go to Timeout in Seconds and select -1 3 - reboot and Validate changes in `/boot/grub2/grub.cfg` GRUB_GFXMODE=1024x768 GRUB_TIMEOUT=-1 #### Acceptance criteria **AC1**: Automate with libyui-rest-api using POM (without Controllers) **AC2**: POM should have 4 pages, including the navigation at the bottmon (on-going)