action #91656
opencoordination #102906: [saga][epic] Increased stability of tests with less "known failures", known incompletes handled automatically within openQA
coordination #88229: [epic] Prevent unintended test coverage decrease
action #91509: [spike-solution]Easy way to check and compare coverage in multiple openQA instances
[qe-core] os-autoinst-distri-opensuse YAML schedule file comparison
0%
Description
Motivation¶
Most of SUSE openQA contributors have selected to use YAML schedule files per openQA scenario in comparison to previously using a shared schedule definition where differences would all be noted down explicitly. This obviously over time introduced the problem of differing coverage which was made more significant with #54839 which of course helped to mitigate short-term pain because teams "felt" as if they would step less on each other's toes. But now the pressure grows to keep the schedules aligned where it makes sense.
Acceptance criteria¶
- AC1: static checks in os-autoinst-distri-opensuse ensure that schedules do not differ further unnecessarily
- AC2: Differences in schedules can be accepted with commented reasons