QA (public) » openQA Project (public)

Motivation¶

openQA tests already should provide all what is necessary to understand all relevant parameters to define a test and the test object. We should demonstrate such capability and reflect that accordingly in our documentation.

Acceptance criteria¶

• AC1: openQA documentation demonstrates how full traceability of tests can be achieved, e.g. test settings, assets, test code, program versions, etc.

Suggestions¶

• Review what our documentation covers for that topic so far
• Look up the according ticket or https://github.com/os-autoinst/openQA/blob/master/etc/openqa/workers.ini#L78 for recording all RPM package versions into tests
• Look into SUSE Carwos which might have good examples with tests pinned to specific git commits, see https://openqa.suse.de/group_overview/328
• Try out openQA yourself how tests can be fully traceable (not necessarily fully reproducible because one might miss old assets and such)
• Document what is missing for a demonstration use-case
• Consider creating a potential follow-up ticket for any cool ideas you have, e.g. "one-page traceability report" offered by openQA