coordination #162545
opencoordination #162539: [saga][epic] future ideas version for version control features within openQA
[epic] Further ideas for openQA scenario definitions fully in git
100%
Description
Further ideas¶
for all other SUSE QE squads¶
- Conversion script to be usable (in theory) for os-autoinst-distri-opensuse -> proof of concept exists, we shouldn't plan to continue for now
for QE tools¶
Add a version to the existing scenario definitions (so that we can introduce breaking changes in a subsequent version) -> we should only do that if we implement any specific breaking feature
Help with better reusing bigger schedule definitions: Add a
defaults
for scenario definitions with settings, like in https://gitlab.suse.de/tinita/kernelqa-openqa-yaml/-/commit/4fdd7ff6b61cb7343202f1bf0f73c5953f1a6cb9#9e43e18bae06f0c8e143b0b63b2ab2fdfd4b2013_0_6Add support for re-using testsuites from another file -> for this we want to be explicit which scenarios inherit from test suites and which don't, hence our proposal:
=openqa_from_bootstrap: # our proposal for looking up existing testsuites
Decide on a good format based on tinita's script proposal
Add the extension ideas from #155218-22 into the existing scenario definitions implementation, e.g.
=(openqa_from_bootstrap)_but_different: # proposal for testsuite look-up with custom name for job template with additional settings
Support other ideas from #155218 from tinita, e.g.
- specifying the architecture e.g. with an @
- the architecture in
prod-ver-flavor-arch1
is duplicated because it's already under aarch1
key
Updated by okurz 6 months ago
- Copied from coordination #154780: [epic] openQA scenario definitions fully in git added