Project

General

Profile

coordination #91914

QA - coordination #91646: [saga][epic] SUSE Maintenance QA workflows with fully automated testing, approval and release

[epic] Make reviewing openQA results per squad easier

Added by okurz 3 months ago. Updated 5 days ago.

Status:
Blocked
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2016-02-09
Due date:
% Done:

0%

Estimated time:
(Total: 0.00 h)
Difficulty:

Description

Motivation

As a squad team member, I want to be able to more easily review Maintenance and Tumbleweed job group related test failures that are relevant to my squad.

Acceptance criteria

  • AC1: Squad members have access to a convenient review workflow of relevant openQA test failures

Suggestions

  • Send out Rocket.Chat notifications via GitLab CI
  • Use custom hook scripts
  • Consider a custom view for the web UI
  • Extend openqa-review with filter parameters (blocklist/passlist) on test suite name
    • but I doubt teams would be able to maintain a blocklist/passlist including all the test suites that they are interested in or not interested in, maybe test modules would work -> "Extend openqa-review with filter parameters (blocklist/passlist) on test module maintainers"?
  • Automatic checks for
    • Maintainer in each test suite
    • Maintainer in each job template
    • Maintainer in each job group
    • No orphaned tests (not reviewed in any squad)
  • Have some page where you can choose the squad and then see its related tests for each SLE version

Subtasks

action #17252: notifications to maintainer on failed modulesNew

action #91605: notifications about failed and unreviewed jobs - but using Rocket.ChatWorkable

action #92533: Module-centric test result overviewNew

action #92960: Add option to openqa-review to section by flavorWorkable

action #93065: "parallel_failed" jobs show up on /tests/overview?todo=1 but these do not need a labelWorkable

action #95278: Making option to filter by job group(s) on /tests/overview more prominentNew


Related issues

Related to QA - action #52655: [epic] Move openqa-review from cron-jobs on lord.arch to a more sustainable long-term solutionBlocked2021-04-19

Related to QA - action #93710: Reference individual openqa-review reports in gitlab CI artifacts, e.g. using gitlab pagesResolved

Copied from openQA Project - coordination #91467: [epic] Surface openQA failures per squad in a single placeBlocked2021-04-232021-07-28

History

#1 Updated by okurz 3 months ago

  • Copied from coordination #91467: [epic] Surface openQA failures per squad in a single place added

#2 Updated by okurz 3 months ago

  • Description updated (diff)

#3 Updated by MDoucha 2 months ago

  • Related to action #92533: Module-centric test result overview added

#4 Updated by okurz 2 months ago

  • Description updated (diff)
  • Status changed from New to Blocked
  • Assignee set to okurz
  • Target version changed from future to Ready

#5 Updated by okurz about 1 month ago

  • Related to action #52655: [epic] Move openqa-review from cron-jobs on lord.arch to a more sustainable long-term solution added

#6 Updated by okurz about 1 month ago

  • Related to action #93710: Reference individual openqa-review reports in gitlab CI artifacts, e.g. using gitlab pages added

Also available in: Atom PDF