action #42572
closed[migration] big testsuite duplication with architecture specific variants
0%
Description
Observation¶
https://openqa.suse.de/admin/test_suites has many test suites which has bad impact on openQA performance, is hard to maintain and is impeding other teams, e.g. to find according test suites. One example of many testsuites are architecture specific variants in testsuites. One example is the migration job group for SLE12SP4 in https://openqa.suse.de/admin/job_templates/151 with examples like
migration_offline_sle12sp2_all_modules_full_update
migration_offline_sle12sp2_all_modules_fullupdate_aarch64
migration_offline_sle12sp2_allpatterns_fullupdate
migration_offline_sle12sp2_allpatterns_fullupdate_aarch64
migration_offline_sle12sp2_allpatterns_zVM
migration_offline_sle12sp2_allpatterns_zVM_preparation
migration_offline_sle12sp2_fullupdate
migration_offline_sle12sp2_ltss_allpatterns_fullupdate_ppc64le
migration_offline_sle12sp2_ltss_allpatterns_fullupdate_s390x
migration_offline_sle12sp2_ltss_allpatterns_fullupdate_x86_64
Suggestion¶
Just define one testsuite for all architectures, backends, machines, products and do the differentiation in the test code.
Updated by sunyan over 5 years ago
- Status changed from New to Rejected
Oliver, as we just talked, all SLE15 SP1 test cases have been optimalized, and we need to balance the effort resource between changing code and changing setting. I reject this ticket since test cases of SLE15 SP1 is on good shape, but please feel free to
reopen it or file another ticket if you see something we could improve. Appreciate your suggestion!