Test Case Dependencies
The Test Case Dependency helps the team efficiently manage the execution order of tests, ensuring a logical, organized, and streamlined testing process. This dependency refers to the relationship between two or more test cases where the execution of one test case depends on the successful execution of another.
Note
The Test Case Dependency feature is only available with the Advanced Features package.
Successor and Predecessor Relationships Between Test Cases
Predecessor Test Case: A test case that must be executed before another. The success of the predecessor is essential for the execution of the successor.
Successor Test Case: A test case that depends on the successful execution of a predecessor. It cannot be executed until its predecessor has completed successfully.
Business Rules
Archiving Rules
If you archive a predecessor test case that has successors in the same test suite, the system blocks the execution of the successors.
To avoid this, remove the dependencies before archiving.
Archiving a predecessor or successor retains their linkages, removable only upon test case deletion.
Archiving a predecessor with status "Failed," "Blocked," or "Not Run" blocks successor execution until unarchived or dependencies are removed.
Archiving a predecessor with status "Passed" or "Not Applicable" allows execution of successors.
Deletion Rules
Archiving and then deleting a predecessor test case ends its dependencies with successor test cases, treating the successors as independent test cases.
Operation
Will test case dependency be retained?
Project Clone
Y
Copy test cases in the same project
N
Copy test cases in other projects
N
Move test cases in the same project
Y
Move test cases to other projects
N