action #40475

Updated by okurz over 1 year ago

## Motivation
We agreed that we should focus on YaST more as it's developed internally and close feedback loop.
Basic idea is to do QA with backlog which is synced with development. It includes integration testing, as we currently do, but more focused on YaST and being a precondition for other tests if installation doesn't work.
It will allow us to test features during the development and provide feedback, so it's cheaper and easier to change things. Additionally, it will prevent broken build from reaching integration testing when multiple QA teams will be affected



## Acceptance Criteria
* **AC1:** separate job group for QA SLE YaST team; this should concern o.s.d
* **AC2:** We know how the openSUSE community, including release managers of Leap and Tumbleweed, would like to benefit from this (and if they see this as a benefit)
* **AC3:** We have a clear list of test scenarios which the QA SLE YaST team owns
* **AC4:** The purpose of each test scenario owned by the Y team is described

##
Tasks
Short-term: split job group, take responsibility for the review, set it as a precondition for other functional tests. If installation is broken, there is not much sense in testing other components.
Establish process to judge overall product quality.
Long-term: sub-team joins SysMgmt team for the QA and helping to establish earlier testing

*Recommendation:* Take care of better communication around this change (as discussed in f2f conversation - perhaps even a simple set of slides. We hate them. But we need to get the message across)

## Further points
* reduce scope for the reviewer (better focus), hence better understanding of the tests
* will be easier to involve YaST team and collaborate with them
* not much benefits for U-subteam, but definitely no harm
* potentially will affect collaboration between subteams, learn HPC/HA experience

## Acceptance Criteria

- separate job group for QA SLE YaST team; this should concern o.s.d
- figure out how and if openSuse community, including release managers of Leap and Tumbleweed, would like to benefit from this (and if they see this as a benefit)
- create a clear list of test scenarios which the QA SLE YaST team owns
- describe the purpose of the test scenarios owned by the Y team
- take care of better communication around this change (as discussed in f2f conversation - perhaps even a simple set of slides. We hate them. But we need to get the message across)

Back