Actions
coordination #40481
closed[functional][y][epic] Use boot into images for all scenarios, where possible and run extra tests after installation on OSD
Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Enhancement to existing tests
Target version:
SUSE QA (private) - Milestone 21
Start date:
2018-10-09
Due date:
2018-10-23
% Done:
100%
Estimated time:
(Total: 8.00 h)
Difficulty:
Description
Motivation¶
To create separate YaST job group where we can focus on YaST specific components, we should do installation in the YaST group, and then perform extra tests using published image.
For the bare-metal machines, where it's not possible we should ensure basic installation works and use chained job, so basic installation is a per-requisite for the advanced tests.
Acceptance criteria¶
- All non INSTALLONLY scenarios use created images for testing, if supported
- If images are not supported, create chained job which performs at least basic installation as a precondition for the advanced scenario on specific environment
Suggestions¶
We have ~300 test suites. We need to identify our scope first, and then convert them. One by one.
Actions