QA (public) » openQA Project (public) » openQA Tests (public) » qe-yam

Motivation¶

As starting point we have 429 yaml files in schedule/yast after applying solution based on default without further adjustments. 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 Tumbleweed, 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). When the products are too different....well, perhaps this motivation is no so clear, but to do it in this way might help to understand what we test. Obviously we need to have less yaml files, that helps with the maintenance of the project.

This is referring to 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#

See ticket description for USBInstall in this epic for an example.

Acceptance criteria¶

AC1: Reduction of yaml files.
AC2: File additional tickets needed to get rid of the differences (very important not forget!)
AC3: Create documentation in Confluence about the strategies used to reduce number of files, like a check list to be compiled with the knowledge of each subtask for the next person to apply.