Project

General

Profile

Actions

coordination #66727

closed

openQA Tests - coordination #15132: [saga][epic] Better structure of test plans in main.pm

coordination #44360: [epic] Parameterize test suites within job groups

[epic] Define structure to define test suites not in openQA database

Added by riafarov almost 4 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2020-05-13
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)

Description

Motivation

As an openQA operators, we would like to have audit of all the changes applied to the test suites and use md for description.
openQA test suites became too big and without structure search sometimes produces too many results, as well as only plain text can be used for the test suites description.

Moving test suites definitions to yaml and storing it in git solves both problems, whereas there are limitations.
https://gitlab.suse.de/qsf-y/qa-sle-functional-y/-/merge_requests/193/diffs here is an example how test suites could be defined and then using aliases in all places where we want to enable it.
As of now, we need custom script as we cannot define any additional node not allowed in schema. Oliver has proposed allowing nodes starting with a dot, which can be put anywhere and ignored during parsing on openQA side.
Also, storing everything in job group makes yaml quite big, which either requires more efforts for each team to build yaml from multiple files, or if we could make openQA support another structure, then none of these hacks will be needed on the storing side.

In our team we though of using test suites in openQA database to define environment specific things, like HDDSIZEGB, HDDMODEL, etc. and move testing related ones to different place. As of now we already use yaml schedule files for that.


Subtasks 1 (0 open1 closed)

action #66781: hidden keys in yaml job templatesResolvedlivdywan2020-05-13

Actions
Actions

Also available in: Atom PDF