Versions Compared

Old Version 7

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.

...

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 that you want in the Systems System Execution Profile as per the requirements.

For more information, 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 the test case.

Info

  • If you To dry run a test case for a Desktop project, you can start from any stepon 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.

  1. If

...

  1. you want to

...

  • Click No to avoid any data loss in the UFT test cases. You need to save the UFT test case, and close the UFT and then dry run the test case again.

  • Click Yes to continue with the dry run of the test case.

  1. (Optional) Click the Stop button to stop the test case execution at any step, click Stop.

  2. After the dry run completes, the test case execution report is displayed.
    For more details on the information of 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.

  • The If the Keep Dry Run Reports checkbox is not selected in the System Execution Profile, the associated test case report is automatically stored at in the following location:
    <LocalAppData>\QualitiaWDClient\app-8.0.0x\WebDriver\ReportResources\1\ITR_xxx
    The In this case, when you dry run test case execution report does not support logging a defect if you have integrated the associated Qualitia project 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.

...