action #135575
Updated by leli 8 months ago
#### Motivation
Following the new [test matrix](https://mysuse-my.sharepoint.com/:x:/r/personal/chcao_suse_com/_layouts/15/doc2.aspx?sourcedoc=%7B0278E2B7-01AD-4E4F-B78F-00B05A53242F%7D&file=draft_sle15sp6-migration-matrix-20230602.ods&action=default&mobileredirect=true&cid=cd782e0a-f8ea-4e18-8070-0f5322c6d9fc), after all optimize work done for SLE12-SP5, we need cleanup the migration test from SLE12-SP5.
The idea is to compare with the test matrix, if not matched, verify whether something wrong for test suite name and setting, if yes then update it, if it is a unexpected old test suite then remove it.
Besides, take care whether something wrong in the test suite.
Ex:
Unexpected base test
- offline_sles12sp5_pscc_def:
testsuite: offline_sles12sp5_pscc_sdk_full \
This will cause the test suite of offline_sles12sp5_pscc_def with unexpected addon of 'sdk'.
We don't suggest to continue use old test suite in yaml file, so it is better to move such old test suite to yaml template instead.
#### Scope
migration daily job group(https://openqa.nue.suse.com/group_overview/265)
Migration milestone job group(https://openqa.nue.suse.com/group_overview/266):
#### Acceptance criteria
**AC1**: Cleanup for migration from SLE12-SP5.
Back