Skip to main content

Overview

Dependencies ensure tests run in the correct sequence, maintain proper state management, and handle cleanup operations effectively.
Dependencies are only contained within a Test Suite. Tests in different suites cannot have dependency relationships.

Types of dependencies

Parent Dependencies

Parent dependencies ensure tests run sequentially, where child tests only run if the parent test passes.How Parent Dependencies work:
  • Tests run in the order specified by the dependency arrows
  • Each test can only have one parent
  • If a test fails, subsequent tests will not run (except for teardown tests)
  • Each test must complete before the next one begins
  • This ensures data consistency and proper state management between tests

Teardown Dependencies

Teardown dependencies are cleanup tests that always run regardless of whether their connected test passes or fails.How Teardown Dependencies work:
  • Teardown tests can connect to multiple parent tests
  • They always run regardless of connected test pass/fail status
  • Ensures proper cleanup and resource management
  • Prevents resource collision on subsequent test runs

How to connect dependencies

1

Navigate to Test Suite

Navigate to your Test Suites and select the suite where you want to add dependency relationships between tests.
Navigate to Test Suite
2

Open the test side peek

Click on a test to open the test side peek window, which displays the test details.
Open the test side peek
3

Switch to Dependencies

From Test Details, switch to the Dependencies tab. This is where you configure test dependencies and teardown options.
Switch to Flow View
4

Define your objective

Determine which tests should have dependency relationships.For example, identify your parent test like “Add Items to Cart”, child tests such as “Complete Checkout” and “Add Second Item to Cart”, and your teardown test like “Clear Cart and Logout”.
5

Add parent dependency

Configure the parent-child relationship between tests to control execution order.
1

Open child test

Open the test you want to add as your child. For example, open “Complete Checkout” test.
Open Child Test
2

Access Dependencies

Switch to the Dependencies tab within the test side peek window.
Access Flow View
3

Select parent test

Under Add a Test Dependency, select the test you want to make your parent.For example, select “Add Items to Cart” from the dropdown.
Select Parent Test
4

Save the test

Click Save Test to apply the parent dependency configuration.
6

Mark teardown test

Configure a test to function as a teardown test that always runs regardless of other test results.
1

Open teardown test

Open the test you want to designate as the teardown test. For example, open “Clear Cart and Logout” test.
Open Teardown Test
2

Access Dependencies and enable the teardown option

Navigate to the Dependencies tab in the test side peek window. Check Mark this test as a Tear Down test and click Save Test to apply the teardown designation.
Access Flow View and enable Teardown Option
7

Connect teardown to parent

Link your teardown test to the tests that need cleanup operations.
1

Open the parent test and access Dependencies

Navigate to the test you want this teardown test to connect to. For example, open “Add Items to Cart” test. Switch to the Dependencies tab within the test side peek window.
Open Parent Test and access Flow View
2

Add teardown connection

Click the Add a Tear Down Test dropdown and select your designated teardown test from the list.
3

Save the test

Click Save Test to establish the teardown connection.
8

View the dependency graph

After saving all tests, navigate to the Dependencies of the test suite.The graph shows parent, child, and teardown connections. Drag between node handles to change a connection, then save or discard your edits.
View dependencies in Flow View

Dependency chains in run results

When tests in a dependency chain launch together, the test run result page shows a dependency chain pill. The pill shows where the viewed run sits in the chain and the status of each member.
  • Click the pill to open a popover of the chain, with rows indented per branch so forks are visible.
  • Open the dependency tree page to see the full chain for the viewed run as a graph, including teardown tests.
  • The pill also appears in the review flow, so you can jump between runs in the same chain while reviewing.
The pill appears when at least two chain members ran together. It is not shown on public shareable links. For a retry, the chain shows the members of that retry round. A test rerun on its own has no chain pill. See Retries with dependencies.

Connection to snoozed tests

Snoozed tests are temporarily disabled tests that won’t run in your test suite. When you snooze a test that has dependencies:
  • Child tests dependent on the snoozed test will not run
  • The entire dependency chain below the snoozed test is paused
  • This prevents failures from tests that depend on setup from the snoozed test
To resume the dependency chain, unsnooze the parent test.