action #44030
closedcoordination #15132: [saga][epic] Better structure of test plans in main.pm
[functional][y] Extend the use of scheduling test parameters
0%
Description
Motivation¶
As we have test variables INSTALLATION_VALIDATION=<modules> and SCHEDULE=<modules> in os-autoinst now, as well as EXIT_AFTER_START_INSTALL=0|1 and INSTALL_ONLY=0|1 and INCLUDE_MODULES and EXCLUDE_MODULES we might want to either extend EXIT_AFTER/INSTALL_ONLY to also work with <modules> or also extend to be able to schedule "group of tests", e.g. functions which then call multiple lines with "loadtest"
Acceptance criteria¶
- AC1: groups of tests can be scheduled/unscheduled easily with test parameters, e.g. as already with INSTALL_ONLY
Updated by okurz about 6 years ago
- Subject changed from [functional][y][epic] Extend the use of scheduling test parameters to [functional][y] Extend the use of scheduling test parameters
Updated by okurz almost 6 years ago
- Due date set to 2019-02-12
pre-fill last sprint in M22 with all tickets within milestone not yet assigned to sprints
Updated by riafarov almost 6 years ago
- Due date deleted (
2019-02-12)
I'm not sure what is the purpose of this one. I would rather invest time in solving main.pm problem for generic case and then aim grouping checks.
Also, this grouping might bring us to the state we got with extra_tests*, where we don't clean up system properly and it affects further tests making investigation quite complex.
Updated by okurz almost 6 years ago
- Target version changed from Milestone 22 to Milestone 25
so let's look into this later after some further experiments with better test plan structure
Updated by riafarov over 5 years ago
- Status changed from New to Rejected
- Assignee set to riafarov
We decided to go yaml way, which can be used. Scheduling becomes trivial in this case.