QA » openQA Project » openQA Tests

okurz wrote:

riafarov wrote:

Motivation¶

As a developer I want to see test suite description on the test run page (not only in the job group overview)

Sounds like a distinct feature request for openQA itself. We can extract this into another ticket after we clarified some more details.

… and additionally include it in the bug template, so it's clear which scenario is it.

Could work when we access the description over a specfic route within openQA
Including it in bug report is one thing, other thing is to display this info on the job run. Any of those two will do the trick. Feature is based on the feedback from YaST team.

Sometimes, when bug is created, it's not clear what is the setup. On top it would be nice to have test module description to understand what the test does.
This information is already there and we can simply extract it.

Yes, it's already available by clicking on the test module name. If we would "extract it", where to put it? Publish on github pages linked to os-autoinst-distri-opensuse?
We have at least summary which is forced for each test module, so we can show it as a pop-up, for example.

It will also help to maintain proper description of the test suites and test modules.

What do you mean with "maintain" here? We do have a description of test suites, at least in functional. Should we have some automatic check for description and create a TODO page or alerts for undescribed test suites? We already have a check for test modules as part of os-autoinst-distri-opensuse so every test module must have a description, i.e. a "Summary:"-line.
Some test suites have to general description, on o3, for example. For test modules sometimes description doesn't match 100%, so there is space for the improvement.

sorry, seems you have messed up markdown formatting in your quoting. Please add blank lines to separate your answers from mine. In the email it looked ok but the ticket rendered in the browser does not show it correctly.

And based on your answers I think you can already create individual feature requests in the openQA project and probably also move this ticket there. What I do not see covered yet is a workflow how it can be ensured that all test suites have a description. The "test module description does not match 100%" IMHO can only be solved by a case-by-case update and looking for this in PR review.

\o/

See for the reason of tracker change: http://mailman.suse.de/mailman/private/qa-sle/2020-October/002722.html