action #37504
Updated by riafarov about 3 years ago
## Motivation As of in the code in system_role test module we have ``` assert_screen 'system-role-default-system', 180; ``` which helps only with synchronization of the actions, but doesn't help as we have needles for each role and it will match even if wrong role is pre-selected. Therefore, we should assert pre-selected role per our expectation and depending on the role/modules selected. For the start, let's limit scope of the ticket to validate different default roles: * Textmode * Gnome * HA (addon scenario where we add HA module, e.g. addon-module-ftp) * Minimal ? (might be that we act on patterns) ## Acceptance criteria **AC1:** No generic solution needle is used to assert default pre-selected role **AC2:** Default pre-selected role is verified per requirements (depending on product, role, activated modules)