coordination #43769
closed
[functional][y][epic] Use inter-machine dependencies to ease our review
Added by okurz over 5 years ago.
Updated over 3 years ago.
Category:
Enhancement to existing tests
Target version:
SUSE QA - Milestone 28
Estimated time:
(Total: 2.00 h)
Description
Motivation¶
With #40415 we can use inter-machine dependencies to prevent the same error to popup on different machines by making machines depend on others
Acceptance criteria¶
- AC1: The openQA test plans in the scope of QSF for all our supported products have been reviewed and inter-machine dependencies have been applied where useful
Suggestions¶
- Go over the all scenarios within the YaST job group of one product and find candidates of scenarios where we consider the value of running them in parallel is low versus the effort of needing to review them all, e.g. when they fail all in the same step
- Depending on the product you looked at crosscheck if the inter-machine dependencies you thought about would conflict with the scenarios in other job groups
- Add the dependencies to the test suites
Further details¶
See http://open.qa/docs/#_inter_machine_dependencies for documentation of the new feature.
- Due date set to 2019-02-12
pre-fill last sprint in M22 with all tickets within milestone not yet assigned to sprints
- Description updated (diff)
- Status changed from New to Workable
- Due date deleted (
2019-02-12)
I believe this feature cannot be used as is, as will require separate testsuites for the settings. Alternative would be to enable in the machines settings. E.g. do not trigger any job on hyper-v unless same job worked on 64bit.
Why would we need "separate testsuites for the settings"? Also, you removed the due date so most likely we will only see this ticket again during the M22 review. I don't see the point in this because I doubt we will have any more knowledge by then. so, should we re-schedule it for a specific sprint, reject or move to future and wait for better times? :)
- Target version changed from Milestone 22 to Milestone 23
- Due date changed from 2019-03-26 to 2019-06-04
due to changes in a related task
- Target version changed from Milestone 23 to Milestone 25
- Due date changed from 2019-06-04 to 2019-05-21
due to changes in a related task
- Due date changed from 2019-05-21 to 2019-06-04
due to changes in a related task
- Target version changed from Milestone 25 to Milestone 27
Waiting for the test suites templates available in openQA, then should be possible to set intermachine dependencies without duplicating test suites.
- Subject changed from [functional][y][u][epic] Use inter-machine dependencies to ease our review to [functional][y][epic] Use inter-machine dependencies to ease our review
- Status changed from Workable to Blocked
- Assignee set to riafarov
- Target version changed from Milestone 27 to Milestone 28
Alright, we got the change, so I will create item to come up with a list of scenarios.
- Status changed from Blocked to Resolved
- Tracker changed from action to coordination
Also available in: Atom
PDF