coordination #169654
Updated by JERiveraMoya 12 days ago
#### Motivation After working on the basic setup in https://progress.opensuse.org/issues/163919 which includes some basic test scenarios, let’s track in this epic all the remaining work to: - Enable other architecture/backend combination. - Test suites to be created for testing products using Agama. - Logs retrieval. - etc. #### Acceptance criteria * **AC1** : Test coverage satisfies customer needs according to documentation and and also satisfies stakeholders, PMs, YaST developers, and other QE squads. * **AC2** : Test suites are created for all the architectures. * **AC3** : Test suites are created with focus on SLES 16 but should be enabled as well for Leap when no much additional effort is required. * **AC4** : Test suite for interactive installations will use a browser automation tool (ie puppeteer) in order to scale properly. #### Additional information * Positioning document https://docs.google.com/document/d/14x17zZDWGiMYQgAi1zX7EFKE3OldivqNE4GUlHg7Dgg/ * high level epic: https://jira.suse.com/browse/PED-8770 * PM requirements for deployment: https://docs.google.com/document/d/1mMhca-nTnHgPUhcO2VCjB03lYKRQBV1TZufIsmZ5-kM/edit?tab=t.0 * Technical description based on requirements (written by YaST developers): (not sure who wrote it): https://docs.google.com/document/d/1M3nUhY32ppqZMiv6WoY4bMPXmB9UEf1w14tDQW2SrlU/edit * YaST Yast team confluence page on this topic with a lot of subpages: https://confluence.suse.com/display/YAST/Installer+for+SLES+16+and+SLES+for+SAP+Applications+16