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
Updated by tjyrinki_suse over 3 years ago
- Subject changed from os-autoinst-distri-opensuse YAML schedule file comparison to [tools] os-autoinst-distri-opensuse YAML schedule file comparison
Updated by okurz over 3 years ago
- Subject changed from [tools] os-autoinst-distri-opensuse YAML schedule file comparison to [qe-core] os-autoinst-distri-opensuse YAML schedule file comparison
@tjyrinki_suse the SUSE QE Tools team does not own or commonly contribute to "os-autoinst-distri-opensuse". In my understanding still as defined in the SUSE QE teams restructuring ultimately QE-Core owns os-autoinst-distri-opensuse, this is your baby :) So you (your team) need to drive that. Of course SUSE QE Tools team members are happy to help on demand, e.g. for technical feasibilities, specific YAML support, etc.
Updated by jstehlik over 2 years ago
- Priority changed from Normal to High
bump up - not critical
note : Regular backlog sync of product/maint testcases - use metabase? - exclude yast
Updated by okurz over 2 years ago
This ticket was set to "High" priority but was not updated within the SLO period for "High" tickets (30 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives. First reminder: Please consider picking up this ticket within the next 30 days or just set the ticket to the next lower priority of "Normal" (SLO: updated within 365 days).