action #111066
closedQA - coordination #91646: [saga][epic] SUSE Maintenance QA workflows with fully automated testing, approval and release
Document suggested workflows for multiple teams reviewing openQA test results size:M
Description
Motivation¶
Within #91914 we have implemented notifications which can be configured per job group. Together with multiple other features teams can define their testing scope within job groups and review test results within their scope accordingly. So far we describe individual features within openQA documentation. We should extend the openQA documentation to explain the motivation and how to build a process around job groups.
Acceptance criteria¶
- AC1: The openQA documentation covers how multiple teams can efficiently work together with openQA
- AC2: Power users have been invited for feedback on the new guide
Suggestions¶
- A simple and small explanation in the openQA documentation is better than no documentation. So just describe how job groups can be used for teams and what current features relate to that
- Consider upstreaming information from https://wiki.suse.net/index.php/RD-OPS_QA/openQA_review#Workflow_for_SLES,_SLED_and_HA_as_an_example and https://confluence.suse.com/display/openqa/QEM+openQA+review+guide to the upstream openQA documentation
- Bonus: Remove redundant internal docs afterwards and link to external references
Updated by mkittler almost 2 years ago
- Subject changed from Document suggested workflows for multiple teams reviewing openQA test results to Document suggested workflows for multiple teams reviewing openQA test results size:M
- Description updated (diff)
- Status changed from New to Workable
Updated by livdywan over 1 year ago
- Subject changed from Document suggested workflows for multiple teams reviewing openQA test results size:M to Document suggested workflows for multiple teams reviewing openQA test results
- Status changed from Workable to New
Updated by livdywan over 1 year ago
Moving back into the estimation queue since we're not clear on the goal here
Updated by livdywan over 1 year ago
- Target version changed from Ready to future
Afer discussing this some more we're concluding that for the Tools team it makes less sense to come up with workflows since we're not the target audience, and it would be best for someone from another team to document their preferred workflows (and get support to upstream it from the Tools team if needed ofc).
Updated by okurz over 1 year ago
- Due date set to 2022-11-18
- Status changed from New to Feedback
- Assignee set to okurz
- Target version changed from future to Ready
Updated by livdywan over 1 year ago
- Subject changed from Document suggested workflows for multiple teams reviewing openQA test results to Document suggested workflows for multiple teams reviewing openQA test results size:M
Updated by okurz over 1 year ago
As soon as the PR is merged I can follow up with https://confluence.suse.com/display/openqa/QEM+openQA+review+guide?focusedCommentId=1119289385#comment-1119289385 and reference the upstream documentation in internal workflow descriptions
Updated by okurz over 1 year ago
- Due date deleted (
2022-11-18) - Status changed from Feedback to Resolved
http://open.qa/docs/#_suggested_workflow_for_test_review has the according information. https://confluence.suse.com/display/openqa/QEM+openQA+review+guide updated.