Project

General

Profile

action #86099

coordination #72889: [qe-core][qem][epic] QAM move job groups, test suites, medium types to git, and then restructure QAM testing to be more easily comparable to product QA

[qe-core][qem] Move osd test suites to git

Added by apappas 11 months ago. Updated 26 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Start date:
2021-01-12
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

The JobGroups used by qem jobs largely use the same test suites across multiple groups and products. That means that they can't be easily defined inline in the JobGroup yaml. So a similar process with the JobGroups CI for saving and updating them off the osd instance is needed.

History

#1 Updated by apappas 11 months ago

  • Status changed from New to In Progress

#2 Updated by cdywan 11 months ago

The MR says "archive" in the title. But I guess you'll want to process YAML to include test suites, going by the ticket description?

#3 Updated by apappas 11 months ago

The archive is because qem doesn't own all the test suites it uses. We can't force other people to use our CI, so we are going to just archive those. Those that start with qam/mau will be overwritten from the CI all the time, so that any changes from the UI will be ignored.

#4 Updated by apappas 11 months ago

I should also add that the main goal of this, is to have a record of them and the changes done to them.
We also can't (obviously/easily) inline the test suites to the JobGroups, because we are using the same test suite in lots of places.

#5 Updated by tjyrinki_suse 10 months ago

  • Assignee set to apappas

#6 Updated by apappas 9 months ago

A bit of documentation regarding the current design.
(This is also on gitlab and confluence)

For the purpose of this project testsuites, are the database entries that are
retrievable at $openqa_instance/api/v1/test_suites in JSON form. We divide
testsuites in two types, those that were owned by QEM and whose name starts with
qam or mau (QEM suites) and the rest (common suites). QEM suites are defined
at ./TestSuites/qem/ and are to be edited there, not OSD. Common testsuites
are stored at ./archive/TestSuites/common and are meant to be edited
elsewhere, on OSD or where their maintainer decides.

Testsuite CI

When a MR is done that edits the QEM testsuites, the CI runs
verify_testsuites.yml. That checks whether:

  1. the QEM testsuites, that are required by the JobGroups, are stored in the proper directory.
  2. the common testsuites, that are required by the Jobgroups, are stored in the archive directory.
  3. that all testsuite JSONs are canonical and "pretty".

After the MR is merged in to the main repo, the post_testsuites.pl script
sends only the QEM testsuites to OSD.

The archival of the common testsuites is not done automatically at the moment
but will be automated in the future.

#7 Updated by tjyrinki_suse 9 months ago

  • Target version set to Ready

#8 Updated by tjyrinki_suse 9 months ago

  • Target version changed from Ready to QE-Core: Ready

#9 Updated by tjyrinki_suse 9 months ago

  • Target version changed from QE-Core: Ready to Ready

#10 Updated by szarate 9 months ago

  • Target version changed from Ready to QE-Core: Ready

#11 Updated by tjyrinki_suse 7 months ago

  • Category set to Infrastructure

#12 Updated by apappas 4 months ago

  • Status changed from In Progress to Feedback

This has been reorganized into a new MR. Before it is merged I plan to propagandize it in the department because it will affect many teams.

#13 Updated by szarate 4 months ago

  • Subject changed from [qe-core][qem] Move test suites to git to [qe-core][qem] Move osd test suites to git

#15 Updated by apappas 3 months ago

This has been alive for three weeks so I would say it is resolved.

#16 Updated by apappas 3 months ago

  • Status changed from Feedback to Resolved

#17 Updated by tjyrinki_suse 26 days ago

Useful to link this https://gitlab.suse.de/qa-maintenance/qam-openqa-yml/-/merge_requests/163 here as well with the review discussion.

Also available in: Atom PDF