Description

We work with lots of job groups on openQA, each containing dozen of test suites, each running a handful of perl modules. This is multiplied by various architectures.

It gets difficult to track where a specific test (aka perl module) is running and there is a risk over the years that schedule between different product or architectures may diverge.

Of course you can look at the actual scheduling configuration, but that got complicated as well, with various conditions and is mainly split between "main.pm" file and various YAML files.

Goals

Goal here is to look "from the other side", directly at some openQA job groups and list every perl module running for every job group and architecture, to more easily compare test schedule between different arch and products to only list differences. This could also be used to validate test schedule against a set of requirements, like a minimum set of tests that must always run for a specific product

Resources

I already started writing a small Golang tool here https://gitlab.suse.de/mgrifalconi/test-schedule-extractor/-/tree/master but needs refinement and possibly some integrated UI for visualization