coordination #119836
Updated by JERiveraMoya over 1 year ago
#### Motivation Yam squad wants to use the solution that developed recently and that has had a limited use for now. The are two important goals that can be achieved using this solution: - Reduce the number of yaml files - Being able to represent the test case using one file for all the products. The solution includes flows, but we should avoid it at least at the beginning and see if we really need them. Documentation: https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/declarative-schedule-doc.md#5-use-default-flow-to-yaml-schedule #### Scope YaST product and YaST maintenance AutoYaST is out of scope, basically we will cover all that has already libyui-rest-api enabled for interactive installations. #### Acceptance criteria **AC1**: Create all necessary default files per architecture and backend to be used by test suites in YaST job group **AC2**: Adapt all the test suites in YaST job group to be based on a default file **AC3**: Implement some new feature along the way if needed #### Suggestions For now there is not much thought about how the solution would work for test suites after installation, so let's focus on interactive installations. installation.