action #29730
closed[sle][functional][u][medium] New test suite create_hdd_gnome+all_patterns
0%
Description
There are several test suite that use the same installation.
If we had the installation in a separated test suite that generates de qcow2 image for 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 boot using that qcow2 image:
- allpatterns SLE-12-SP3, [SLE-12-SP4], SLE-15
- sdk+allpatterns SLE 12-SP3, SLE 12-SP4, [SLE 15 (not available yet)]
- we+allpatterns SLE 12-SP3, SLE 12-SP4, [SLE 15 (not available yet)]
Acceptance criteria¶
- AC1: There a new test suite that creates a qcow2 image with all patterns installed.
Task¶
- Create a new test suite.
- Test is locally.
- Enable it on OSD.
Updated by SLindoMansilla over 6 years ago
- Blocks coordination #29733: [epic][functional][u] Test suites that use "all patterns" boot from created qcow2 image added
Updated by okurz over 6 years ago
- Status changed from Workable to New
I don't understand the use case or benefit. Please elaborate.
Updated by jorauch over 6 years ago
- Subject changed from [sle][functional] New test suite create_hdd_gnome+all_patterns to [sle][functional][medium]New test suite create_hdd_gnome+all_patterns
- Status changed from New to In Progress
- Assignee set to jorauch
Updated by jorauch over 6 years ago
Important setting:
DESKTOP=gnome
ENABLE_ALL_SCC_MODULES=1
PATTERNS=all
Updated by jorauch about 6 years ago
Verification run on OSD:
https://openqa.suse.de/tests/1397275#
Updated by jorauch about 6 years ago
Verification run on O3: https://openqa.opensuse.org/tests/585030
Test suite created on OSD, need to wait for new build to verify it is actually triggered
Updated by jorauch about 6 years ago
Verification for PATTERNS=all:
https://openqa.suse.de/tests/1399842
Updated by jorauch about 6 years ago
- Description updated (diff)
- Status changed from In Progress to Feedback
Automatically triggered on OSD:
https://openqa.suse.de/tests/1404053
At least an all pattern installation suite should be created on O3
Updated by riafarov about 6 years ago
- Due date changed from 2018-01-30 to 2018-02-13
- Target version changed from Milestone 13 to Milestone 14
@jrauch, is o3 test suite only missing part here?
Updated by jorauch about 6 years ago
- Target version deleted (
Milestone 14)
Yes O3 is the only missing part, I am wondering if ENABLE_ALL_SCC_MODULES is really needed for all patterns?
Updated by jorauch about 6 years ago
- Due date deleted (
2018-02-13) - Status changed from Feedback to Workable
- Assignee deleted (
jorauch) - Target version changed from Milestone 14 to future
As discussed with okurz we do not have a current use case for these. Could make sense in the future whenever we need it, i.e. when we have any test that wants to test based on special patterns.
Updated by jorauch about 6 years ago
- Related to coordination #23454: [sle][functional][epic][sle15] Adapt former SDK tests to something equivalent for SLE15 added
Updated by jorauch about 6 years ago
- Copied to action #31108: [opensuse][functional][medium] New test suite all_patterns added
Updated by SLindoMansilla about 6 years ago
Why did you deleted the parent task?
Updated by okurz about 6 years ago
because the former parent task can be fulfilled without this task according to the ACs
Updated by okurz almost 6 years ago
- Subject changed from [sle][functional][medium]New test suite create_hdd_gnome+all_patterns to [sle][functional][u][medium] New test suite create_hdd_gnome+all_patterns
- Difficulty set to medium
Updated by okurz almost 6 years ago
- Target version changed from future to future
Updated by okurz over 5 years ago
- Status changed from Workable to New
Bulk action to set status back to "New" for older tickets which are in "future". They would need to be revisited in time when we come up with a defined plan and assign to a milestone.
Updated by okurz about 5 years ago
- Status changed from New to Rejected
- Assignee set to okurz
I think time has shown that we do not benefit from that currently. When we see a direct need we can bring this back up. However then we would do it differently after in the past months we have split out the YaST job group and image creation jobs plus post-install validations are conducted differently.