coordination #121837
Updated by JERiveraMoya over 1 year ago
#### Motivation Yam squad should take care at least For this new release of the following ALP areas: in December we should perform some initial manual testing. - **Web automation of D-Installer** Having a clear strategy We can split it in two session due to apply integration testing to D-Installer is becoming more relevant. Because testing the full installation workflow for at least TW and ALP due date is a time-consuming task closed and we need to find some new bugs ASAP. The problem build 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 expected, so testing 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 parallel could be covered as well, at least for ncurses. beneficial. - **Manual testing** Additionally for new releases of ALP from December and next year 2023 we should keep doing some manual testing. #### 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 each milestone #### Suggestion ALP documentation: https://documentation.suse.com/alp/all/single-html/alp/index.html Read this blog to kick off this process: https://yast.opensuse.org/blog/2022-12-05/d-installer-needs-you