action #152873
Updated by JERiveraMoya 3 months ago
#### Motivation Have full version control of our For migration power VM test, it still use the old test scenarios. Example: suites in https://openqa.suse.de/admin/test_suites, which is not suggested and hard to maintain, more important is that these test suites are not in gitlab control. Ex: ``` - online_sles15sp3_pscc_basesys-srv-ltss_def_full_y_pre: settings: +SCC_REGCODE_LTSS: xxx SCC_ADDONS: base,serverapp,ltss testsuite: online_sles15sp3_basesys-srv_all_spvm_pre - online_sles15sp3_pscc_basesys-srv-ltss_def_full_y: settings: +SCC_REGCODE_LTSS: xxx MIGRATION_METHOD: yast SCC_ADDONS: base,serverapp,ltss START_DIRECTLY_AFTER_TEST: online_sles15sp3_pscc_basesys-srv-ltss_def_full_y_pre testsuite: online_sles15sp3_pscc_base-srv_all_full_spvm ``` 'online_sles15sp3_basesys-srv_all_spvm_pre' and 'online_sles15sp3_pscc_base-srv_all_full_spvm' comes from https://openqa.suse.de/admin/test_suites. Watch out #### Scope This should include test suites for some test suite that inherit from other test suites, we should also remove those dependencies, power VM in all should be `testsuite: null`. Migration job groups. (Just need confirm split action for the job groups template already done) #### Acceptance criteria **AC1**: All migrations Replace the included old test suite use anchor/alias instead of db/ui definitions suites with anchor.