Project

General

Profile

Actions
Copy link

coordination #99306

open

[epic] Future improvements: Make reviewing openQA results per squad easier

Added by okurz about 3 years ago. Updated 6 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Feature requests
Target version:
QA (public, currently private due to #173521) - future
Start date:
2016-02-09
Due date:
% Done:

25%

Estimated time:
(Total: 0.00 h)

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 very convenient review workflow of relevant openQA test failures

Suggestions

  • 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)

Subtasks 16 (12 open — 4 closed)

action #17252: notifications to maintainer on failed modulesNew2016-02-09

Actions
action #92533: Module-centric test result overviewNew2021-05-11

Actions
openQA Tests (public) - action #92921: [tools][spike] Can we change or display job group structure for maintenance job groups to have one job group per team like for product validation and maybe specific products and versions below size:MResolvedmgrifalconi2021-05-21

Actions
action #92960: Add option to openqa-review to section by flavorWorkable2021-05-21

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

Actions
action #95878: Add filter on /tests/overview for search term in test suite descriptionNew2021-07-22

Actions
action #101457: Native per-module bug tagsNew2021-10-25

Actions
action #110632: Capture stderr of job_done_hooks as wellNew2022-05-04

Actions
openQA Infrastructure (public) - action #110920: Emails from o3 are rejected by mx2.suse.de for certain sender/recipients size:SResolvedtinita

Actions
action #111135: Enhance email notification message content for about failed and unreviewed jobs New2022-05-16

Actions
action #111215: Various improvements for email notification about unreviewed jobs size:MResolvedtinita

Actions
action #131279: [timeboxed:6h][spike solution] a single command line or openQA webUI search view to show all tests blocking an incident by squad size:SResolvedybonatakis

Actions
action #156547: A single API route to show all not-ok tests blocking a SLE maintenance incident size:MWorkable

Actions
action #156553: [timeboxed:10h][spike solution] openQA webUI search view to show all tests blocking an incident by squad - take 2Blockedokurz

Actions
action #157660: A single webUI search view to show all not-ok tests blocking a SLE maintenance incident size:MNew2024-03-21

Actions
action #162479: Carryover force_result softfailed not applied logicallyNew

Actions

Related issues 2 (1 open — 1 closed)

Copied from openQA Project (public) - coordination #91914: [epic] Make reviewing openQA results per squad easierResolvedokurz2021-05-25

Actions
Copied to openQA Project (public) - coordination #109647: [epic] Future improvements: Simpler investigation of openQA test failuresNew2021-04-26

Actions
Actions
Copy link

Also available in: Atom PDF