Versions Compared

Key

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

Introduction: For Software Development Engineers in Test (SDET), executing tests offline provides flexibility, especially when there's no immediate access to the main software or in environments with limited connectivity. This guide will walk you through the process of working with offline suites in the Qualitia Automation Studio (QAS) using CLI commands.

 

📚Prerequisites:

  • Access to the Qualitia Automation Studio (QAS) Client.

  • An offline package saved on your computer.

  • Basic familiarity with Command Line Interface (CLI) operations.

🔂 Process Flow:

Executing Offline Suite using CLI Commands

You want to run tests offline using command prompt due to limited access to the QAS client.

  1. open the Command Prompt.

  2. Navigate to the location of your saved offline package.

  3. Input: java -jar qualitiaoffline-8.6.x.jar to execute the offline package with the default settings.

  4. However, if you wish to override certain settings:

    1. Mapped Execution Profile: Enter the location of the execution profile you want in the following ways:

      1. The location of the execution profile must be enclosed by double inverted commas.

      2. It must be the first argument. For example: java -jar qualitiaoffline-8.6.x.jar "D:/ABCsettings.JSON"

    2. Offline Suite: Enter the location of the offline suite as SuitesDir="Suite_Path". For example, java -jar qualitiaoffline-8.6.x.jar SuitesDir="D:/OfflineSuite/Suite1

    3. Environment Variable: Enter environment variables and their associated values in the format java -jar qualitiaoffline-8.6.x.jar env.var1=value1 env.var2=value2. Here var1 and var2 denote environment variables, and value1 and value2 denote the associated values. For example, java -jar qualitiaoffline-8.6.x.jar env.username=john.smith env.password=12345

    4. Other Parameters defined in the Selected Execution Profile: Enter the parameters preceded by their hierarchy in name=value format as command-line arguments. For example, to use a specific version of Google Chrome, enter the command line argument as follows:

      java -jar qualitiaoffline-8.6.x.jar googleChrome.version=81.0.1.36 In this example, googleChrome is the topmost parameter and then version. You can provide multiple property=value pairs separating them with space, as shown in the following example:
      java -jar qualitiaoffline-8.6.x.jar googleChrome.version=81.0.1.36 PageTimeoutInSeconds=10

      If you are overriding the mapped execution profile enter it as the first argument, as shown in the following example:

      java -jar qualitiaoffline-8.6.x.jar "D:/ABCsettings.JSON" googleChrome.version=81.0.1.36 PageTimeoutInSeconds=10

      If a key has a dot in its name, you need to put backslash before the dot such as chrome.chromedriverVersion, which is under androidChrome, as shown in the following example:
      java -jar qualitiaoffline-8.6.x.jar androidChrome.chrome\.chromedriverVersion=83

  5. Press Enter to initiate the offline suite execution.

Viewing an Offline Suite Execution Report

After running the tests, you need a comprehensive report to analyze the results.

...

you can manually upload the locally saved report.

Editing the Test Data for an Offline Suite

Before re-running tests or for a different testing scenario, you might need to change some test data.

...

Info

 Qualitia recommends using the Qualitia Client because it displays ❌ error message when change in test data is incorrect.

 

Editing Test Data in Offline Suite Test Data File

In scenarios where access to the Qualitia Client is limited, the offline suite provides flexibility by allowing you to directly modify test data. This guide simplifies the process for you, ensuring that they can quickly and effectively adapt their test cases as needed.

...

You want to execute tests located in a shared location, either for collaborative purposes or due to infrastructure constraints. You can run an offline suite in a shared drive for web and mobile applications in two ways: by mapping the shared drive to a local computer or without mapping.

Executing a Shared Offline Suite by Mapping the Shared Drive

For a more seamless experience, you might prefer mapping the shared drive to your local system.

...

Info

Note: You cannot execute an offline suite using the command prompt by specifying the complete UNC (Shared location).

Offline Suite Execution for Desktop Applications on a Shared Drive

You can execute an offline suite present in a shared drive for desktop applications.

...

  1. Configure the offline suite as per the requirements. For detailed instructions, refer to Configuring the System Execution Profile Settings for a Desktop Project.

  2. Do one of the following: 

    • Open command prompt, navigate to mapped drive location that contains the offline package and offline suite

    • Navigate to the mapped drive location that contains the offline package and the offline suite and double-click the offline package (9.x.x jar).

Executing Offline Suites & Integrating with CI Tools

 

Introduction:

This guide offers SDETs a clear path to execute offline suites stored on shared drives and integrate them with various Continuous Integration (CI) tools.

Executing an Offline Suite from a Shared Drive without Local Mapping:

Method: Direct execution from the shared drive. Steps:

...

Info

Note: Using the command prompt with the full UNC path for execution isn't supported.

Execution using Continuous Integration Tools:

Method: Integration via QAS settings.

...