action #89866
Updated by riafarov about 3 years ago
Clients in scope here: * firstboot_language_keyboard * firstboot_keyboard As of now we mix testapi Once parent ticket is done and of REST API, and assert that pages are shown with assert_screen. Motivation have a solution which debug_label is stable solution. Listed clients share same controls (combobox with the keyboard languages), which supported, we can also then reuse could get rid of assert_screen for the normal installation page definition. We should find reliable way to assert that correct page is shown, either with `is_shown` approach we already use, or use `debug_label` property in the output json. following clients: welcome timezone hostname registration ## Acceptance criteria 1. firstboot_language_keyboard and firstboot_keyboard do not use openQA testapi in the tests