Automatically skip test case when one of their dependencies failed
When a test case fails, it is common that all other test cases that rely on the fonctionnality that was tested to also failed. In that case, it is often difficult to figure out what is the 'real' failure that should be examined. To avoid a test case failure to cascade, the framework should allow to indicate that a given test case depends on other test cases, some test suites, or some test groups. In case of test case failure, all test cases that depends on it are automatically skipped, with a status detail clearly indicating the cause.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Drafting
- Series goal:
- Accepted for 0.2-monitor
- Implementation:
- Not started
- Milestone target:
- v0.2.3
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
- Needs to define precisely how dependency are declared: how do you refer to another test case ?
- Needs to define precisely test status in case of dependent failure.
Work Items
Dependency tree
* Blueprints in grey have been implemented.