action #47921
closed[functional][y] Apply new scheduling mechanism for any installation scenario in YaST job group which is also executed on o3
0%
Description
Motivation¶
So we got 3 PoC solutions, which do work already, but none of them solves all the problems (which happens mainly in dreams). It's time to continue and one make step further.
Here are PoCs:
- https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6741
- https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6329
- https://github.com/mudler/openqa_testloader_workshop
As a test developer, I would like to easily modify and control schedule of the test suites. I also would like not to affect all existing test suites when enabling additional module.
From https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6329 we should borrow test for yaml format validation. https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6741 has couple of points not addressed. We mainly just need to make it extendable, so other features like setting variables in yaml (is available here: https://github.com/mudler/openqa_testloader_workshop) can be developed.
Suggestion:
Use simple scenarios to start with.
Acceptance criteria¶
- New declarative scheduling mechanism is applied for a single test suite which is executed on osd ond o3
- Solution is reusable and available for all test developers
- Solution is documented, describing syntax and usage