action #66781
closedopenQA Tests - coordination #15132: [saga][epic] Better structure of test plans in main.pm
coordination #44360: [epic] Parameterize test suites within job groups
coordination #66727: [epic] Define structure to define test suites not in openQA database
hidden keys in yaml job templates
0%
Description
Motivation¶
See #66727 . To reuse same settings among multiple scenarios we can use YAML anchors on one scenario to reuse. However this can make it non-obvious where common settings are defined if the list of scenarios grows as well as needs the defining points to be complete scenarios. With hidden keys like in gitlab CI as defined in https://docs.gitlab.com/ee/ci/yaml/#hide-jobs we can have explicit places where we can find templates to be reusable in multiple scenario definitions
Acceptance criteria¶
- AC1: scenario names with leading dot are not scheduled as tests
- AC2: definitions from scenarios with leading dot can be reused in other scenarios
Suggestions¶
Probably we do not need to change anything in the YAML schema but just ignore the hidden scenarios from evaluating the complete schedule