Versions Compared

Old Version 2

changes.mady.by.user ravi.chandran

Saved on

compared with

New Version Current

changes.mady.by.user ravi.chandran

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Dry Run means executing the test case to validate whether the steps of A dry run lets you validate whether the test case executes as expectedis executed as per the test requirement.

The dry run runs are considered trial executions. Hence, their execution results are not considered official and hence they are not displayed in Reports and Dashboard portal. A test case dry run uses the settings defined in the Systems Execution ProfileA 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 detailsinformation, refer to the following topics:

Info

You can dry run a test case on a local environment only.

In the System Execution Profile, you can select the Keep Dry Run Reports checkbox to save the test case dry run report without overwriting the previous dry run reports.

To dry run a test case.:

  1. Open a Test Case. To know how to open a test case, refer to Adding or Editing a Test Case Manually .

  2. Click Run to dry run a the test case.
    Note: For testing on desktop applications, you

Info

...

  • 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.

  1. If you want to stop the test execution at any step, click Stop.

  2. After the dry run completes, the test case execution report is displayed.
    The report is automatically saved at For more details on the Test Case Execution report, refer to Test Case Iteration Detailed Report.

Info

  • If some steps have failed in the dry run, you can refer to Failure Summary to know the reasons for their failure.

  • If the Keep Dry Run Reports checkbox is not selected in the System Execution Profile, the associated test case report is automatically stored in the following location:
    <LocalAppData>\QualitiaWDClient\app-8.0.

...

  • x\WebDriver\ReportResources\1\ITR_xxx

...


  • In this case, when you dry run the same or another test case, this report is overwritten.

  • If the Keep Dry Run Reports checkbox is selected in the System Execution Profile, the associated test case report is automatically stored in the following location:
    AppData\Local\Qualitia\WD\Client\ResultPath\DryRun\<machinename>\<username>\<projectname>\<Buildname>\<Releasenumber>\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.