action #54839

action #15132: [saga][epic] Better structure of test plans in main.pm

[functional][y] Use new yaml structure for test suites to define different schedules for different env

Added by riafarov 8 months ago. Updated 7 months ago.

Status:ResolvedStart date:30/07/2019
Priority:NormalDue date:24/09/2019
Assignee:riafarov% Done:

0%

Category:Enhancement to existing tests
Target version:QA - future
Difficulty:
Duration: 41

Description

Motivation

As of now, when we have even small differences in the schedule, we have to clone the test suite (like we did for RAID tests). When #44360 is resolved, we will be able to reuse same test suite template and provide different settings on medium-machine layer making it simpler to manage for the different backends.

History

#1 Updated by riafarov 7 months ago

  • Status changed from Blocked to Feedback

We have applied solution for SLE 15, waiting for the new build to see if I've missed anything. If not, we can migrate SLE 12 job group too.

#2 Updated by riafarov 7 months ago

  • Status changed from Feedback to Resolved

Both job groups are migrated. I've cleaned up RAID tests to reuse original test suites. Staging is also migrated and works fine using yaml schedules.

Also available in: Atom PDF