Introduction

The Test Case Dependency feature helps the QA 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.

Testers can effectively define, track, and manage test case dependencies to ensure correct test execution order for maximum coverage and efficiency.

The 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

1. Predecessor and Successor Relationships:

   • A predecessor test case can have multiple successor test cases at the same level.

   • If a test case has a successor, it cannot have a predecessor.

   • A successor test case can only have one predecessor.

   • If a test case has a predecessor, it cannot have a successor.

2. eSignature-Enabled Projects:

   • Test Case Dependency is allowed for both approved and unapproved test cases.

   • Only approved test cases will be linked to execution.

3. Linkage Rules:

   • Only independent test cases can be linked.

   • Shareable test cases cannot be linked independently, as they are not independent entities and cannot be executed on their own.

Archival and Deletion Rules:

1. Archiving Rules:

   • If a predecessor test case and its successors are linked within the same test suite and the predecessor is archived, the execution of successors will be blocked; it's recommended to remove 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:

1. Archiving and then deleting a predecessor test case ends its dependencies with successor test cases, treating the successors as independent test cases.

Enable Test Case Dependency

The Test Case Dependency feature ensures that test cases are executed in a specified order, especially when execution of one test case depends on the outcome of another. This approach helps in maintaining the integrity and reliability of test results.

To enable Test Case Dependency in a project, follow these steps:

1. Go to Project Management.

2. Select the Project.

3. Open the General Settings tab.

4. Enable the Define Dependency Between Test Cases option.

Configure Execution Status

QMetry allows users to configure how the execution statuses of predecessor test cases impact the execution and status of successor test cases. To set this up, navigate to Customization and select Execution Status on the sub-menu.

• Allow Execution of Successor: If selected, successor test cases can only be executed if their predecessor possess the execution statuses as per the selected checkboxes. “Passed” or “Not Applicable” statuses are selected by default and cannot be altered.

• Auto Propagate Status to Successor Test Case: Auto Propagation manages how status changes in the predecessor test case affect linked successor test cases. The behavior varies based on the initial status of the test case.

When Auto Propagate Status is ON:

• For “Blocked”, “Failed” or any status above Not Run, the successor test case status will be set to "Blocked."

• For Status “Not Run”, the successor test case status will be set to "Not Run".

• For statuses below “Not Run”, Auto Propagation does not apply.

When Auto Propagate Status is OFF:

• The successor test case status remains unchanged.

This feature ensures that linked test cases reflect the most accurate status updates automatically, based on the chosen configuration for Auto Propagation.

Define Test Case Dependency

Test case dependencies can be defined from the Test Case Module - Dependent Test Cases Screen, but only if this feature is enabled at the project level. To access the test case dependency screen, navigate to the Test Cases module and select Dependent Test Cases tab.

Link a Predecessor Test Case

The user can link only one predecessor to each test case. The predecessor's status will influence the successor's execution.

To establish a predecessor relationship for a test case:

1. Go to Dependent Test Cases tab.

2. Click Link Predecessor.

3. Choose the predecessor test case from Link Predecessor Test Cases To Define Dependency Screen.

4. Select the test case and click Link & Close.

Once a test case is linked as a "Predecessor" to the current test case, the current test case is designated as the "Successor," identifiable by a tag on the right side.

Tags

When the user links a successor to a test case, it automatically becomes a successor, and the tag “Successor” appears on the screen.

The linked predecessor is labeled as "Predecessor" and is shown on the predecessor test case's “Dependent Test Cases” screen.

Link Successor Test Cases

You can mark a test case as a predecessor and link multiple successor test cases to it.

To link Successor Test Case to a Test case, follow these steps:

1. Go to Dependent Test Cases tab of the successor test case.

2. Click the Link Successor button.

3. Choose the successor test case from the Link Successor Test Cases To Define Dependency Screen.

4. Select the test case and click Link & Close.

Link By Entity Key

The user can also link a test case as a predecessor or successor by using test case entity keys.

To link Test Cases as a successor or predecessor via entity key, follow these steps:

1. Navigate to the “Dependent Test Cases” Page of the successor test case.

2. Click the "Link By Entity Key" button.

3. Select the dependency type: Successor or Predecessor.

4. Enter the Test case entity keys to be linked.

5. Click on "Link" to complete the process.

Test Case List View

You can view the Successor and Predecessor count in the test case list view.

Add Successor and Predecessor Columns in List View

Open the Arrange Columns drop-down and select the Successor and Predecessor columns.

View Predecessor and Successor Counts in List View

The count of successor test cases and predecessor test cases is displayed on the screen.

View Linked Successors or Predecessors from List View

Click on the count in the Predecessor or Successor column to drill down and view the linked test cases.

Test Suite View

You can check dependent test cases for a test suite from Test Suites by going to the Test Cases tab.

View Successor/Predecessor Test Cases from Test Suite

In this screen, the successor and predecessor columns show the count of dependent test cases.

• Count in Green - All the successor test cases are linked to the test suite.

• Count in Blue - All the successor test cases of the predecessor test case are not linked to the test suite.

View Successor Test Cases for the Predecessor

Clicking on the successor count reveals the successor test cases for the predecessor. This allows users to identify which successor test cases are not linked to the test suite.

View Predecessor Test Cases for the Successor

Clicking on the predecessor count shows the details of the predecessor test case.

Test Execution Screen

Test Execution Detail View

Users can view test case dependencies on the test execution screen in both the Test Execution Detail View and the Test Execution Default View.

Test Execution Detail View

To view test case dependency from the test case detail view, navigate to Test Suites. Select Test Execution and click on Test Execution Detail View.

To access the Test Execution Detail view, perform the following steps:

1. Click on “Switch to Detail View” on the Top Right corner of the screen.

2. In the Detail View screen, click on the Test Case Entity Key and navigate to the dependent test cases tab

Test Execution Default View

You can also view test case dependencies from the Test Execution Default View.

To access the text execution default view, perform the following steps:

1. In the Default View screen, click on the Manage Columns icon and select the Successor and Predecessor columns.

2. The successor and predecessor columns in the test case run view display the counts of associated successors and predecessors.

3. Click on the count to navigate to the test execution screen. Users can view the relevant test cases under the Dependent Test Cases tab.

Test Execution Dependency

Test execution dependency refers to the order in which successor test cases within a test suite must be executed due to their reliance on the outcomes of predecessor test case.

Business Rules

• Same Test Suite vs. Different Test Suites:

  • Same Test Suite: Successor test case execution is restricted until its predecessor is executed, regardless of execution order.

  • Different Test Suites: Test cases are treated as independent; no execution dependency is enforced.

• Status Changes After Execution:

  • Already Executed Successor: If a Successor test case has been executed and its Predecessor is subsequently linked, the Successor’s status remains unchanged. The user cannot change Successor’s execution status until its Predecessor test case is executed, regardless of execution order.

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

• Copying Test Suites:

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

• Bulk Execution:

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

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

• Predecessor Failure or Blockage:

  • Status Modification: By default, successor test cases’ statuses cannot be modified if the Predecessor fails or is blocked. The status of the successor test case will automatically be set based on the Predecessor Test case or according to the status defined in the Configuration > Execution Status.

• Iteration Execution:

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

Example of Execution Dependency

Let us understand this with an example.

TC-139 is the Predecessor to TC-116 and TC-138. These test cases can be linked with the same test suite or can be linked to different test suites independently.

Here, all these test cases are linked with the same test suite, TS-35.

Execute Predecessor Test Case

To execute the predecessor test case, follow these steps:

1. Navigate to the test execution screen to execute interdependent test cases.

2. Users cannot execute the successor test cases (TC-138, TC-116) until their predecessor test case (TC-139) has been executed. Details of the predecessor test case can be viewed by hovering over the Execution Status of the successor test case.

3. Users will have the option to send an email notification to the assignees of the successor test cases, informing them that the executions are now unblocked. Select the checkbox to send the notification, or leave it unchecked otherwise.

Execute Successor Test Case

Once the predecessor is executed, the execution of the successor test cases is unblocked. Assignees can now proceed to execute the successor test cases.

→ When Auto Propagate Status to Successor Test Case is enabled: If the predecessor test case fails or is blocked, then the successor test cases will not be allowed to execute, and the status will be set to ‘blocked’.

→ When Auto Propagate Status to Successor Test Case is disabled: If the predecessor test case is ‘failed’ or ‘blocked’, the successor test cases cannot be executed and will be marked as "Not Run".

An alert message will appear upon selecting either "Failed" or "Blocked" status for the predecessor test case.

Unlinking Test Cases

There are two ways to unlink the linked predecessor/ successor test case:

• Directly click on the Unlink icon for the test case.

• Select the test case and click on the Unlink Selected button above.

Change Log

You can view the change log related to test case dependency in the Change Log Report under Audit Compliance.

Test Cases Dependency Report

The Test Case Dependency Report reveals relationships between test cases, helping testers and managers understand dependencies and plan execution. It aids in planning, prioritizing, and executing test cases to ensure comprehensive coverage and timely software delivery.

From the Home page, go to QMetry System Report and select Test Cases Dependency Report.

Trace by Test Cases

Users can generate the report for preferred test cases. Click on the Trace by Test Cases button at the top.

Users can apply filters to narrow down the list of test cases. Select the desired test cases from the filtered list and click "Apply" to generate a report for the selected test cases.

The report is generated for the selected test cases.

To reset the applied filter, click on the Reset button.

Test Case Execution Dependency Report

The Test Case Execution Dependency Report helps in understanding the order in which test cases should be executed and identifies any potential issues or bottlenecks in the testing process. This report is essential for test managers to plan and execute testing activities effectively. It is also helpful in ensuring comprehensive coverage and timely completion of testing processes.

From the Home page, go to QMetry System Report and select Test Cases Dependency Report.

Trace by Test Suite

Users can generate the report for preferred test cases by clicking on the Trace by Test Suite button at the top.

The following filters can be applied to shortlist the test suites:

• Dependency Type: Filter for Test Case Dependency Type, Successor or Predecessor. The test suites associated with the specific dependency type are displayed.

Select test suites from the displayed list and click Apply to generate the report for the selected test suites.

The report is generated, showing the test case details for the selected test suites.

To reset the applied filter, click on the Reset button.

Export Reports

Users can export test case dependency reports and test case execution dependency reports in two formats.

• XLSX format

• CSV format

The steps to exporting the reports are the same for both types of reports.

Steps to Export Report

• Click on the Cog icon ( ) and select the format to export the report details.

2. To see the progress of the test case export, go to the Scheduled Task section at the top by clicking on the icon.

3. Once the process is complete, click on the download icon to download the report.