Versions Compared

Key

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

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:

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 https://qualitia.atlassian.net/wiki/spaces/QAS82/pages/2681539278/Adding+a+Test+Case+Manually .

  2. Click Run to dry run the test case.

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

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

    A scenario in Qualitia is a collection of test cases, which are part of the same module of the application under test (AUT). 

    For example, User Management is a module in your AUT, then you can create a scenario in which you can define multiple test cases that automates the scenarios related to User Management such as adding a user, editing a user, deleting a user, and so on.

    Adding a Scenario

    Perform the following steps to add a scenario.

    To add a scenario:

    1. From the Expand Menu, click Develop.
    2. In the left pane, click the Scenarios node as shown in the following figure:
      Image Added
    3. Click the Add Scenario button (Image Added).
    4. Enter Scenario Name and Scenario Description.
    5. Click Save
    6. You can now add new test cases. 

    Editing a Scenario

    Perform the following steps to edit a scenario.

    To edit a scenario:

    1. From the Expand Menu, click Develop.
    2. In the left pane, click the the scenario that you want to delete, and then select the Edit Scenario button (Image Added).
    3. To know how to edit a scenario, refer to Adding a Scenario.

    Deleting a Scenario

    You cannot delete a scenario that contains a test case. If you do not want a scenario, you can move all the existing test cases of the scenario to another scenario, and then delete that scenario.

    To delete a scenario:

    1. From the Expand Menu, click Develop.
    2. In the left pane, click the scenario that you want to delete, and select the Remove Scenario button (Image Added).

    On the Page:

    Table of Contents