Test Case Execution Dependency

Same Test Suite: You cannot execute a successor test case execution before executing its predecessor.

Different Test Suites: The system treats each test case as independent; no execution dependency is enforced.

Already Executed Successor: If you have executed a successor test case before linking a predecessor, the status doesn't change. You cannot update the successor’s status before executing the predecessor.

Not Run Status: Applies when the latest version of the Predecessor is marked as “Not Run” and the Successor is already executed.

Status Preservation: When copying a test suite, the Successor's status is preserved unless the copy is marked as "Not Executed."

Execution Screen: Successor test cases blocked by a predecessor cannot be selected for execution.

Bulk Execute: Successor test cases blocked by a predecessor can be selected, but execution is skipped, and their status remains unchanged.

Status Modification: By default, you can not modify a successor's execution status if the Predecessor fails or is blocked. The system sets the status of the successor test cases based on the Predecessor Test case or according to the status defined in the Configuration and Execution Status.

Linked Test Cases: The status of the Successor test case depends on all iterations of the Predecessor. The automatic propagation of status to the successor test case depends on the highest level of execution status priority of the linked predecessor test case.