action #29730
Updated by SLindoMansilla over 6 years ago
There are several test suite that use the same installation. If The execution time of those and the maintenance would be easier if we had the installation in a separated test suite that generates de a qcow2 image for with all pattern installed and the rest of the test suites that need it, we would have: - shorter execution times on productive instance (faster build feedback) - shorter execution times on QA engineers machines (machines less busy/blocked) - easier maintenance of test suites that need this qcow2 image. - Avoid redundancy problems on test suites that should perform the same installation by centralizing such installation into one test suite. The following test suites could ones boot using that from this qcow2 image: - allpatterns [[SLE-12-SP3](https://openqa.suse.de/tests/1058309)], [[SLE-12-SP4]()], [[SLE-15](https://openqa.suse.de/tests/1340478)] - sdk+allpatterns [[SLE 12-SP3](https://openqa.suse.de/tests/1058272)], [[SLE 12-SP4](https://openqa.suse.de/tests/1342731)], [SLE 15 (not available yet)] - we+allpatterns [[SLE 12-SP3](https://openqa.suse.de/tests/1058317)], [[SLE 12-SP4](https://openqa.suse.de/tests/1342682)], [SLE 15 (not available yet)] ## Acceptance criteria - **AC1:** There a new test suite that creates a qcow2 image with all patterns installed. ## Task 1. Create a new test suite. 2. Test is locally. 3. Enable it on OSD.