QA (public) » openQA Project (public) » openQA Tests (public)

Motivation¶

When we'll have separate job group, we need good understanding of what we have in it and what we want to have. By that we also can decide where how we want to test one thing and another.
There are many examples where we could be more efficient and gain time for increasing test coverage for more critical areas instead of covering e.g. firefox on all possible environments.
This also includes proper evaluation of the risks when not running certain test module.
As a starting point we already have test suites descriptions + test modules descriptions. But it's hard to identify which modules are executed where, and on which env do we cover certain setups. That is visible only in the openQA dashboard.

Suggestions¶

There is one team which uses testopia exactly for this purpose. We need to identify good format which could be reused among teams and used e.g. as a reporting template to visualize coverage per build.
Markdown is more preferable

Acceptance criteria¶

1. All existing test suites in the YaST job group have description
2. Test suite includes env description, executed test cases summary and purpose

NOTE: should be handled once we have current state of the job group, meaning after at least #42494 and #42503 are done.