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

Motivation¶

Avoid duplication of work and maintenance of test moduleS with needles and libyui REST API
Avoid testing the same multiple times in different groups.

For example, recently a new feature related with Apparmor was added and we anticipated the change fixing installation steps with libyui REST API in staging. Once it hits the product in YaST group, smoothly was applied. Nevertheless we had to fix installation test module with needles introducing yet another hack with environmental openQA settings, which is in fact the best option given the circumstances.

There is not need to do the work twice and maintain several versions of the same functionality, neither to run the steps of the installation in each single group. In YaST group those steps are already tested.

As a stable solution we have to possibility to use AutoYaST and publish images once the AutoYaST installation has finished, fulfilling the same purpose than the current interactive installation.

In this Epic we should track the tasks needed to support this migration in other groups, starting for example with Functional groups where multiple create_hdd_* jobs run. The idea is not to implement all those cases for other groups and more like support other groups, giving them some samples, ways to proceed and help in general.

Instead of migrating this image creation to YaST group, each group should retain its responsibility for those. In the future we might find better way, like an exclusive job group in openQA for image creationg so anyone can consume them and resposability is also clear there.

Acceptance criteria¶

AC1: Ensure AutoYaST installation can run successfully in different architecture
AC2: Support on removing duplicity of implementation and test steps of installation everywhere.
AC3: Responsibility of those new test suite should remain in the scope of respective teams.