Project

General

Profile

Actions

action #72283

closed

coordination #71662: [epic][y] Improve managing/grouping test suites

Grouping of test suites in openQA

Added by JERiveraMoya about 4 years ago. Updated 11 months ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Target version:
-
Start date:
2020-10-06
Due date:
% Done:

0%

Estimated time:
Tags:

Description

Motivation

It is to have a way to group test suites in groups that are growing a lot so we can visualize it properly and we have everything in one place. Example where would be useful: our YaST group and in Tumbleweed as well to create section that could match somehow teams working in SLE.

Current approach

Currently it is possible to have separated groups which requires more maintenance in control version and you don't have everything in one place, and although you can play with a query and aggregate result by url we are looking for something more obvious in the UI. Another current approach is to use FLAVOR setting to do the grouping but it is a hack and bring issues when cloning from some ficticious flavor to another.

Proposal

Add a category/group/tag name to a test suite. When displaying it instead of nesting frames (which could be tricky for visualization), Inside of each flavor, we could create those sections allowing the use of slashes within the category name so the nesting would work similar to file system paths (nice to have: those sections could be expandable/contractable)
Assuming the existing hierarchy of the test results overview page is simply deduced from the job settings and a job is simply shown within a certain "Flavor: …" section if it has a job setting FLAVOR=…. It doesn't really matter where the flavor comes from (test suites, job templates, manually posted job, …). Maybe it makes sense to follow the existing approach, e.g. jobs which have the variable CATEGORY=… would be shown within a sub section "…" of the "Flavor: …" section.

Sketch of the idea

FLAVOR: Full
   > storage/raid
----------------------------------------
Test           aarch64 ..........
---------------------------------------
|  Test 1
|  Test 2
----------------------------------------
   > storage/lvm
|  Test 3
|  Test 4
---------------------------------------
FLAVOR: Online
...

Related issues 1 (1 open0 closed)

Related to openQA Project (public) - coordination #54806: [epic] Better user control over job group overviewNew2019-07-30

Actions
Actions #1

Updated by riafarov about 4 years ago

  • Target version set to future
Actions #2

Updated by riafarov about 4 years ago

  • Parent task set to #71662
Actions #3

Updated by JERiveraMoya about 4 years ago

Actions #4

Updated by riafarov about 4 years ago

  • Project changed from openQA Tests (public) to qe-yam
Actions #5

Updated by riafarov almost 4 years ago

  • Target version changed from future to SLE 15 SP3
Actions #6

Updated by riafarov almost 4 years ago

  • Status changed from New to Workable
Actions #7

Updated by JERiveraMoya over 3 years ago

  • Target version changed from SLE 15 SP3 to Current
Actions #8

Updated by oorlov over 3 years ago

  • Status changed from Workable to New
Actions #9

Updated by JERiveraMoya over 2 years ago

  • Tags set to YaST
  • Priority changed from Normal to Low

There is a recent feature to hide/show parallel children which use that collapse mechanism. We should refresh this research in the future.

Actions #10

Updated by JERiveraMoya over 2 years ago

  • Subject changed from [y] Grouping of test suites in openQA to Grouping of test suites in openQA
Actions #11

Updated by JERiveraMoya about 2 years ago

  • Target version changed from Current to future
Actions #12

Updated by JERiveraMoya about 2 years ago

  • Target version deleted (future)
Actions #13

Updated by JERiveraMoya 11 months ago

  • Status changed from New to Rejected

Backlog clean-up.

Actions

Also available in: Atom PDF