action #138473
Updated by rfan1 7 months ago
#### Motivation
As starting point we have 429 yaml files in `schedule/yast` after applying solution based on default without further adjustment. There is plenty of space for improvement and now we are in position to tackle individual test test suites without affecting much or break other areas.
One of the main motivation is to have a test case that can be run across products, sle, sle micro, openSUSE Tumblewee, openSUSE Leap, etc, so first we need to create `schedule/yam/test_cases/ . Inside this folder we will place our yaml that will be valid (in theory) for each product (we have to see what techniques we will use in each case to make this possible and we will document those).
This are all the installation, (we didn't go too far how to apply this for other than installation that contains steps and it fits quite well, so for now the scope are only the interactive installation, not AutoYaST ones):
https://openqa.suse.de/tests/overview?arch=&flavor=&machine=&test=&modules=accept_license&module_re=&distri=sle&version=15-SP5&build=102.1&groupid=129#
Let's go in the order that are displayed for example, first one is USBInstall, it has been done via https://progress.opensuse.org/issues/132971 poo#132971
#### Acceptance criteria
**AC1**: Kick off the reduction of yaml files except USBInstall,
**AC2**: Following the the steps mentioned in https://confluence.suse.com/pages/viewpage.action?pageId=1364165336
**AC3**: We may use this ticket as a parent one and create child jobs for different install scenarios
Back