Project

General

Profile

Roadmap

SUSE QA tests - Milestone 31

about 10 months late (2020-02-21)

71%

71 issues   (45 closed — 26 open)

Related issues
action #47441: [functional][u] test code feedback - integrate bots to test distribution on github

openQA Project - Ready

Next tasks to be picked up by the QE tools team

79%

367 issues   (276 closed — 91 open)

Related issues
action #77944: Run "auto-review" more often but alarm less
action #78187: Import and enable Testreport data into SMELT
action #80414: [proof-of-concept] Extend "auto-review" for failed jobs as well, start with o3
action #80418: [learning] Fix parse errors in "openqa-investigate" "parse error: Invalid numeric literal at line 1, column 10"
action #80690: [qem] Testing of packages in different codestreams but in one incident

future

a "virtual" milestone that is never reached. Everything that is currently out of scope can go here. Place for new feature ideas, wishes, proposed improvements and changes which we could work on in the future but are not currently planned for.

52%

952 issues   (488 closed — 464 open)

Related issues
action #27621: [sle][functional][u] Test "motif" libraries are usable within SLE because customers use this "legacy" framework
action #29993: [tools][hard] Better handling of custom tags/labels/fields (was: Find a way to support logical combinations of search keywords in progress.o.o queries to e.g. list all "functional SLE15 fate issues")
action #34657: [functional][u][timeboxed:4h] Setup retrospective server based on https://github.com/funretro/distributed
action #43580: The RT product can be tested by release managers or developers before full SLE validation
action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15
action #44774: [functional][u] create a new test module valgrind for openQA