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

Motivation¶

See #109187
It is done for SLE-15-SP{3,4} in #109214. Let's try to reuse the same AutoYaST profile for the rest of the products in maintenance.
mru-install-desktop-with-addons | mru-install-minimal-with-addons

Previous experience indicated that any minimal failure/mistake setting this basically cascade to all job group, for that reason it is better to do in Development job group. Then we will file another ticket to deploy this in YaST MU job group.

Scope¶

Test suites with external dependencies: mru-install-desktop-with-addons & mru-install-minimal-with-addons
Products: rest of the products in maintenance.
Architectures: for the minimal is running in three architectures, aim for all of them if possible.

Acceptance criteria¶

AC1: New AutoYaST test suites are created in 'YaST Maintenance Updates - Development' openQA job group corresponding to mru-install-desktop-with-addons & mru-install-minimal-with-addons.
AC2: Copies of the chained dependencies of test suites mru-install-desktop-with-addons & mru-install-minimal-with-addons which are in YaST MU job group will be set to new AutoYaST test suites in 'YaST Maintenance Updates - Development' job group
AC3: If we cannot reuse the AutoYaST profile created for SLE-15-SP{3,4} consider to reduce the scope of products or architectures to migrate to AutoYaST.

Suggestions¶

• Reuse knowledge from previous task: #107674 #109187
• We could reuse very likely the AutoYaST profiles created for SLE-15-SP3.
• We should rename all test suite creating AutoYaST image to autoyast_create_* so we can distinguish better between old and new things regardless of the job group, maintenance or product as it might be confusing.