coordination #37958
closed
[epic] self-tests in os-autoinst-distri-opensuse for impact on staging test schedule
Added by okurz over 6 years ago.
Updated almost 3 years ago.
Category:
Feature requests
Estimated time:
(Total: 16.00 h)
Description
Motivation¶
Sometimes when a new test module is introduced – for example by new contributors which are mainly starting with new test modules and not changing existing ones – we forget in code review to think about if this module should be excluded from staging tests causing staging test failures, some frustration on side of SLE release managers and subsequently requests like #37826 which we should try to prevent because they make our life miserable. We should think about a way to prevent staging test breakage by unintentional introduction of new test modules into staging tests, e.g. using self-tests in os-autoinst-distri-opensuse. This test can have the additional benefit that we actually evaluate the test code before we deploy it to production where previously we had "trivial" failures but they could only be catched in production.
Acceptance criteria¶
- AC1: travis CI tests on PRs fail if new test modules are introduced to staging tests unintentionally
Suggestions¶
- Add a fitting openSUSE staging test vars.json to the repo for test purposes (could be copied from existing ones and stripped down to bare minimum what is needed or newly created)
- Add a call with
isotovideo _exit_after_schedule=1
to only evaluate the schedule and compare against a reference
- Add instructions to update the reference file whenever a change to the staging tests is actually intended
Further details¶
It might sound counter-intuitive to use a blacklist for excluding test modules from staging tests (loadtest "…" unless is_staging;
) and then define a whitelist for the test to check against but it might be a start towards #15132
- Copied from action #36523: [functional][y][medium] self-tests for https://github.com/os-autoinst/os-autoinst-needles-opensuse/ added
- Subject changed from [functional] self-tests in os-autoinst-distri-opensuse for impact on staging test schedule to [functional][y] self-tests in os-autoinst-distri-opensuse for impact on staging test schedule
- Due date set to 2018-10-09
- Target version changed from Milestone 18 to Milestone 19
@y-team I would be ok to move to u-team if you prefer, up to you
- Assignee set to riafarov
- Estimated time set to 13.00 h
I will clarify priority with okurz
- Due date deleted (
2018-10-09)
Do not have capacity in the current sprint.
- Due date set to 2018-10-23
- Target version changed from Milestone 19 to Milestone 20
- Due date deleted (
2018-10-23)
- Assignee changed from riafarov to okurz
- Target version changed from Milestone 20 to future
- Estimated time deleted (
13.00 h)
Discussed in the y-team's refinement, need to rethink by now because we want to improve test schedule structure as a whole anyway. I will try to split out e.g. "simple isotovideo run" and "more explicit staging tests"
- Subject changed from [functional][y] self-tests in os-autoinst-distri-opensuse for impact on staging test schedule to [functional][y][epic] self-tests in os-autoinst-distri-opensuse for impact on staging test schedule
- Status changed from Workable to Blocked
- Difficulty deleted (
medium)
- Assignee changed from okurz to riafarov
to track as stand-in as discussed
- Due date changed from 2019-04-09 to 2019-03-12
due to changes in a related task
- Due date changed from 2019-03-12 to 2019-04-23
due to changes in a related task
- Due date changed from 2019-04-23 to 2019-05-07
due to changes in a related task
- Due date changed from 2019-05-07 to 2019-05-21
due to changes in a related task
- Due date changed from 2019-05-21 to 2019-06-04
due to changes in a related task
- Due date changed from 2019-06-04 to 2019-07-16
due to changes in a related task
- Due date changed from 2019-08-13 to 2019-08-27
due to changes in a related task
- Due date changed from 2019-08-27 to 2019-09-10
due to changes in a related task
- Due date changed from 2019-11-05 to 2019-11-19
due to changes in a related task
- Due date changed from 2020-01-28 to 2020-02-11
due to changes in a related task
- Due date changed from 2020-02-11 to 2020-03-24
due to changes in a related task
- Due date changed from 2020-04-21 to 2020-05-05
due to changes in a related task
- Due date changed from 2020-05-05 to 2020-05-19
due to changes in a related task: #65432
- Project changed from openQA Tests to openQA Project
- Subject changed from [functional][y][epic] self-tests in os-autoinst-distri-opensuse for impact on staging test schedule to [epic] self-tests in os-autoinst-distri-opensuse for impact on staging test schedule
- Category deleted (
Enhancement to existing tests)
- Status changed from Blocked to New
- Assignee deleted (
riafarov)
Un-assigning myself as last ticket remaining is for the tools team.
- Category set to Feature requests
- Tracker changed from action to coordination
- Status changed from New to Resolved
- Assignee set to okurz
- Target version changed from future to Ready
All subtickets resolved. Latest one was #48389 with which we can fully cover AC1 and call this "Resolved"
Also available in: Atom
PDF