coordination #108224
Updated by JERiveraMoya about 2 years ago
#### Motivation We still rely on legacy tests for most of the YaST modules, wasting a lot of time in re-needling when theme/fonts change and the logic of these tests many times is just a simple navigation showing options, not a real test case. As starting point we will do the following: - Decide YaST modules to target. YaST developers gathered some stats to know which one could be more important for customers). - Depending on time, resources and interest, we may write down test cases for those selected (in similar fashion we did with the steps in the installation) and just select a few interesting test cases, 2 or 3 to automate them in a new test suite (or existing one, depending on the the case). todo ### Acceptance criteria **AC1**: a subset of YaST modules is selected to be automated **AC2**: Automate using libyui REST API.