Project

General

Profile

Actions

coordination #153928

open

coordination #99303: [saga][epic] Future improvements for SUSE Maintenance QA workflows with fully automated testing, approval and release

[epic] Ideas from SUSE QE Tools workshop 2024-01-19 Filter openQA todo-jobs on /tests belonging to groups, review teams, etc

Added by okurz 4 months ago. Updated 29 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)

Description

Ideas

  • allow to search or filter by time in /tests page
  • As a test module maintainer or reviewer I would like to see all occurences of job modules failures
  • As a reviewer of test modules I would like to be able to use the webUI to apply the same label or bugref to multiple jobs from a filtered view like https://openqa.opensuse.org/tests/overview?modules=boot_windows&modules_result=failed&todo=1&result=failed&distri=opensuse&version=15.6&build=1.295&groupid=82# showing multiple jobs all failing in the same module (not wanting to use the CLI openqa-label-all)
  • SLE maintenance incident tests have builds like :$id:$package_name which sorts one package update after another unrelated one so /tests/overview page can not be easily used for reviewing all current incident test failures. To address that different ideas
    • use /tests to review
    • not group by build (by foursixnine)
    • schedule SLE maintenance incident tests with "$id" and "$package" in the flavor, not the build -> old ticket #95857

Subtasks 1 (0 open1 closed)

openQA Project - action #154261: [spike][timeboxed:20h] batch commenting on all openQA jobs, e.g. involving a specified SLE maintenance incident in webUI size:MResolvedmkittler

Actions

Related issues 4 (3 open1 closed)

Related to openQA Project - action #134933: Filter openQA todo-jobs on /tests belonging to one "review squad" size:MResolvedkraih2022-11-02

Actions
Related to QA - coordination #95857: [epic] QAM incident tests: Fix "next & previous", latest results and label carry-overWorkable2021-07-22

Actions
Related to openQA Project - coordination #99306: [epic] Future improvements: Make reviewing openQA results per squad easierNew2016-02-09

Actions
Related to openQA Project - coordination #154771: [epic] Improved test developer user experienceNew2024-02-29

Actions
Actions #1

Updated by okurz 4 months ago

  • Related to action #134933: Filter openQA todo-jobs on /tests belonging to one "review squad" size:M added
Actions #2

Updated by okurz 4 months ago

  • Related to coordination #95857: [epic] QAM incident tests: Fix "next & previous", latest results and label carry-over added
Actions #3

Updated by okurz 4 months ago

  • Related to coordination #99306: [epic] Future improvements: Make reviewing openQA results per squad easier added
Actions #4

Updated by okurz 4 months ago

  • Related to action #154261: [spike][timeboxed:20h] batch commenting on all openQA jobs, e.g. involving a specified SLE maintenance incident in webUI size:M added
Actions #5

Updated by okurz 4 months ago

  • Subtask #154261 added
Actions #6

Updated by szarate 3 months ago

Actions

Also available in: Atom PDF