action #153007
Updated by JERiveraMoya 7 months ago
#### Motivation As follow-up of #132971 for certain scenarios we don't need to run this system preparation test module. They exists for stability to wait for the system load is acceptable to go on and are important for children jobs, or test module using serial console or even some networking that would require hostname. Doesn't look the case of usb_install, where we could have just the validation part and no more, representing perfectly the test case. https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/schedule/yam/test_cases/usb_install.yaml#L7-L10 Unfortunately we cannot represent the actions here, because they are part of os-autoinst but still would be good enough to have the validation identifying the test case. #### Acceptance criteria **AC1**: Check that removing preparation test module test is stable for Online/Full medium running 10x **AC2**: Remove this test suite from https://openqa.suse.de/admin/test_suites and add it to https://gitlab.suse.de/qe-yam/openqa-job-groups/-/blob/master/JobGroups/test_suites.yaml **AC3**: Rename in all places that makes sense installation_booting_from_usb, for example in the test suite name. #### Additional information we should correct this `test_suite: null` https://gitlab.suse.de/qsf-y/qa-sle-functional-y/-/merge_requests/539/diffs#14b5739fca83e73d73bda6c083b58b96f0fd3bdc_821_827 and being able to share as much as possible settings in test_suites.yaml in job group ci. For that we most likely will need to create one anchor for description (so we don't forget each test suite should have a description) and and anchor for the settings, in that way we can merge the keys later maximizing the sharing.