Versions Compared

Old Version 4

changes.mady.by.user ravi.chandran

Saved on

compared with

New Version 5

changes.mady.by.user ravi.chandran

Saved on

Key

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

Dry Running A dry run for a test case helps to validate whether all the steps of a test case execute are executed as expected.

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 and test case iterations as per the set of values defined in the associated Test Data explorer.

A test case dry run uses the settings defined Before you dry run a test case, ensure that you have configured the settings that you want in the Systems Execution Profile.

For more detailsinformation, refer to

...

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

  2. After the dry run completes, the test case execution report is displayed.
    For more details on the information of the Test Case report, refer to Test Case Iteration Detailed Report.

Info

  • If some steps failed, 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.0\WebDriver\ReportResources

  • The dry run test case execution report does not support logging a defect if you have integrated the associated Qualitia project with a defect management system such as Jira or TFS/Azure DevOps.
    You can also refer to Failure Summary to know why certain steps failed.The report is automatically saved at the following location:
    <LocalAppData>\QualitiaWDClient\app-8.0.0\WebDriver\ReportResources