Actions
coordination #163919
open[epic] Create automation setup for testing Agama
Start date:
2024-07-15
Due date:
% Done:
55%
Estimated time:
(Total: 0.00 h)
Description
Motivation¶
Prepare automation to have MVP ready for Beta 1 (29th Nov), see schedule
Tasks will include (but not an exact list):
- Sync of agama iso in O3
- Integration with openQA to boot in all the architectures.
- Basic script/profile that perform default installation of Tumbleweed interactive/unattended.
- In the case of the interactive, break out the script using Page Object Model (POM) for code reuse and maintainability.
- Once Agama will be available in IBS, perform previous activities to install a default SLES 16.
What is out of scope:
- Automate any scenario different from the default installation, all these activities are related with the setup, what to test is another big task (epic) to think about it, for example, a default installation with Agama doesn't have much value, other than to serve as regression, in SLES 16 testing should use images created directly in IBS to test such a scenario where nothing is tweaked in the configuration of the system to be installed.
Acceptance criteria¶
- AC1: Automation of a default installation of Tumbleweed with Agama is running in O3 for each build created in OBS.
- AC2: Automation of a default installation of SLES 16 with Agama is running in OSD for each build created in IBS.
- AC3: Automation is designed aiming for rereusability and maintainability of code (ie using POM).
- AC4: Interactive installation will be controlled by a web testing tool + openQA and unattended installation will be controlled by openQA.
Updated by lkocman about 2 months ago
Please be aware of https://progress.opensuse.org/issues/163355
Actions