coordination #121837
closed[saga] Testing ALP in Yam squad
0%
Description
Motivation¶
Yam squad should take care at least of the following ALP areas:
-
Web automation of D-Installer
Having a clear strategy to apply integration testing to D-Installer is becoming more relevant. Because testing the full installation workflow for at least TW and ALP is a time-consuming task and we need to find new bugs ASAP.
The problem is that openQA is not a good fit for checking the UI (driving the browser), although it is a good option for the rest.
Developers are working on this strategy in https://trello.com/c/x01mLJzy/3223-8-research-design-a-qa-strategy and Yam squad plan to collaborate closely with them. -
Automation of YaST in Container
It should be covered as well, at least for ncurses. -
Manual testing while no automation is available
Additionally for new releases of ALP from December and next year 2023 we should keep doing some manual testing. -
Automation of Cockpit ?
It shall be covered by different squads and need to be decided what web automation tool to use, upstream or the same for D-Installer. Therefore this area is not clear yet how much Yam squad will contribute.
Acceptance criteria¶
AC1: Create web automation for D-Installer
AC2: Create libyui-rest-api automation for YaST in a container
AC3: Perform manual testing of D-Installer for milestone when no automation is available.
Suggestion¶
ALP documentation: https://documentation.suse.com/alp/all/single-html/alp/index.html
Updated by JERiveraMoya over 2 years ago
- Tracker changed from action to coordination
- Subject changed from Initial manual testing for D-Installer (ALP December prototype) to [Epic] Initial manual testing for D-Installer (ALP December prototype)
- Description updated (diff)
Updated by JERiveraMoya over 2 years ago
- Subject changed from [Epic] Initial manual testing for D-Installer (ALP December prototype) to [Epic] Testing D-Installer and YaST in container in Yam squad
- Description updated (diff)
- Status changed from Workable to In Progress
- Assignee set to JERiveraMoya
Updated by JERiveraMoya over 2 years ago
- Subject changed from [Epic] Testing D-Installer and YaST in container in Yam squad to [Epic] Testing ALP in Yam squad
Updated by JERiveraMoya over 2 years ago
- Subject changed from [Epic] Testing ALP in Yam squad to [Saga] Testing ALP in Yam squad
Updated by JERiveraMoya over 2 years ago
- Subject changed from [Saga] Testing ALP in Yam squad to [saga] Testing ALP in Yam squad
Updated by szarate over 2 years ago
Here are some of the things I found during a quick installation test:
- alt + tab works (shouldn't imo)
- Too much time to start firefox
- Installer should accept urls for the ssh key (will it automount flash drives?)
- Installer should make clear that either root has a password or an ssh public key must be provided
- Disconnecting network cable during the installation breaks the installation
- Installing system without network results in not working system (installation completes in seconds)
- No clear information on how to get logs if something fails, or see the instalation progress
Updated by JERiveraMoya over 2 years ago
- Related to coordination #121855: [epic] Agama web interactive installation added
Updated by JERiveraMoya over 2 years ago
- Related to coordination #121858: [epic] Automation of YaST in Container added
Updated by JERiveraMoya over 2 years ago
- Status changed from In Progress to Rejected
Duplicated of #121933
Updated by JERiveraMoya over 2 years ago
- Related to deleted (coordination #121855: [epic] Agama web interactive installation)
Updated by JERiveraMoya over 2 years ago
- Related to deleted (coordination #121858: [epic] Automation of YaST in Container)