A dry run lets you validate whether the test case is executed as per the test requirement.
The dry runs are considered trial executions. Hence, their execution results are not displayed in Reports and Dashboard portal. A dry run covers all the task iterations and test case iterations as per the set of values defined in the associated Test Data explorer.
Before you dry run a test case, ensure that you have configured the settings in the System Execution Profile as per the requirements.
For more information, refer to the following topics:
Configuring the System Execution Profile Settings for a Web/Mobile Project
Configuring the System Execution Profile Settings for a Desktop Project
You can dry run a test case on a local environment only.
To dry run a test case:
Open a Test Case. To know how to open a test case, refer to Adding or Editing a Test Case Manually .
Click Run to dry run the test case.
To dry run a test case on mobile platform, ensure that you have configured the system requirements and settings in the associated execution profile.
For more information, refer to Requirements and Configuration Settings for Mobile Environments.You can start a dry run of a test case from any step for a desktop project only. You need to select the step from where you want to execute, right-click it, and select Execute from the Step.
If you want to stop the test execution at any step, click Stop.
After the dry run completes, the test case execution report is displayed.
For more details on the Test Case Execution report, refer to Test Case Iteration Detailed Report.
If some steps have failed in the dry run, you can refer to Failure Summary to know the reasons for their failure.
The associated test case report is automatically stored at the following location:
<LocalAppData>\QualitiaWDClient\app-8.0.x\WebDriver\ReportResources\1\ITR_xxx
You cannot log a defect from the dry run test case execution report even if the Qualitia project is integrated with a defect management system, such as Jira or TFS/Azure DevOps.