💾Manage Test Data for Offline Suite

This guide walks you through the process of managing test data for offline suites in the Qualitia Automation Studio (QAS).

📚Prerequisites

• Access to the QAS Client.

• An offline package saved on your computer.

• Basic familiarity with CLI operations.

Procedure

Edit Test Data for Offline Suite

You can edit test data for an offline suite either using Qualitia Client or test data Excel file present in Offline Suite folder.

Editing the Test Data using Qualitia Client

1. Open your test case from the client.

2. Access the Test Data explorer to edit.

3. Once done, re-create the offline suite. Refer to the section Work with Offline Packages.

Edit Test Data Using Test Data File

You can edit the test data directly in the Excel file located in the Offline Suite folder. However, it is recommended to edit through the Qualitia Client as it provides error alerts for incorrect data modifications.

In scenarios where access to Qualitia Client is limited, the offline suite provides flexibility by allowing you to directly modify test data through the Excel file present in Offline Suite folder.

After the offline suite is created, for every test case that contains test data, the associated test data as excel files are created in the same folder with the same names as given to their associated test cases. You can modify the test data such as replace the existing test data and enable or disable TC iterations.

📚Prerequisites

• An offline suite with associated test data.

• Basic knowledge of Excel and data formats.

Basics of Editing Test Data

You want to quickly adjust test data without altering the structure of the file.

Steps to Modify Test Data for an Offline Suite

1. Go to the Offline Suite folder.

2. Backup the test data file you want to edit.

3. Open the test data Excel file.

4. You can update the values for the below fields, as needed.

   1. TC Iteration: Shows the number for every TC Iteration. There must be at least one TC Iteration for executing the test case.

   2. Selection: Shows True for the enabled test case iterations; otherwise, it shows False. You can modify the values only for test case iterations.

   3. DataSetTag: Optionally, enter a label for identifying the dataset in the test case execution report. You can modify the values.

5. To add a TC iteration, insert a row with values for TC Iteration Number, Selection, and DataSetTag (optional).

6. For adding a task iteration, insert a row with values for associated parameters.

7. Save the Excel file after editing.

Execute Offline Suite on a Shared Drive

You can execute an Offline Suite present in a shared drive for web and mobile applications in one of the following ways:

• By mapping the shared drive to the local computer.

• Without mapping the shared drive to the local computer.

Execute a Shared Offline Suite by Mapping

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

1. Copy both the offline package and suite to the shared drive.

   1. Ensure you have the read and write permissions.

2. Map this shared drive to your local computer.

3. Update the offline suite settings, as required.

   1. For details, refer to Configuring the Settings for an Offline Suite.

4. To execute, follow one of these approaches:

   1. Using the Command Prompt, go to the mapped location and execute the offline package with the right command.

      1. For details, refer to section Executing Offline Suite using CLI Commands.

   2. Open the mapped driver and simply double-click the offline package (9.x.x jar).

Execute a Shared Offline Suite Without Mapping

To execute a shared drive without mapping the shared drive to the local computer:

1. Copy the offline package along with the offline suite to the shared drive.

   1. Ensure you have the read and write permissions.

2. Open the shared location and double-click the offline package (9.x.x jar).

Execute Offline Suite for Desktop Applications on a Shared Drive

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

Before you execute an offline suite for a desktop application, ensure that you have:

1. Installed UFT on the same computer from where you will execute the offline suite.

2. Mapped shared drive to local computer.

3. Copied offline package to shared drive with read and write access.

4. Copied TSR file in the local or shared drive and ensure you have access.

To execute offline suite for desktop applications on a shared drive:

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.

     • Execute the offline suite using the command line. For detailed instructions, refer to Configuring the General Settings.

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

Execute Offline Suites using CLI

Qualitia supports integration with Continuous integration tools like Jenkins, TeamCity, and Bamboo. It enables developers to find and solve defects in a code base rapidly and to automate testing of their builds.

When you want to execute your test cases using CI tools, you must set the CI_Tool property in the mapped execution profile.

If your test case is for mobile applications, Appium Server is internally hosted on Qualitia client. However, still you can use a custom Appium server if you want to test on another Appium version. 

Executing an Offline Suite from a Shared Drive without Local Mapping

Method: Direct execution from the shared drive. Steps:

1. Copy both the offline package and suite to the shared drive, ensuring you have read/write permissions.

2. Directly access the shared location and initiate the offline package by double-clicking on the 9.0.x jar file.

Execution using Continuous Integration Tools

Method: Integration via QAS settings.

1. Ensure QAS's capability to integrate with CI tools like

   1. Jenkins

   2. TeamCity

   3. Bamboo.

2. For mobile application tests, even though QAS hosts the Appium Server internally, use a custom Appium server for different Appium versions if needed.

3. Set the CI_Tool property in the mapped execution profile before starting.

Headless Executions:

Method: Browser-based testing without GUI.

Steps:

1. Recognize that headless executions run faster since they don't launch the browser UI. QAS supports this for Google Chrome and Mozilla Firefox.

2. To execute tests in headless mode:

   1. Via QAS Client/OfflineConfigManager:

   2. Open the associated execution profile.

   3. Choose the browser.

   4. Activate the respective headless setting, via CLI:

      1. For Chrome: java -jar qualitiaoffline-xxxx.jar googleChrome.chromeOptions.args=--headless

      2. For Firefox: java -jar qualitiaoffline-xxxx.jar firefox.firefoxOptions.args=--headless

Method: Setup via Qualitia Client or OfflineConfigManager.

Steps:

1. Open the associated execution for a test suite.

2. From the Browser list, select either Chrome or Firefox.

3. Check the Desired Capabilities checkbox.

4. Based on your browser choice:

   1. For Chrome:

      1. Select the chromeOptions checkbox.

      2. Check the args checkbox.

      3. Input --headless in the associated field.

   2. For Firefox:

      1. Select the firefoxOptions checkbox.

      2. Check the args checkbox.

      3. Input --headless in the associated field.

5. Click Ok.

Method: CLI-based execution for headless mode.

Steps:

1. Open the Command Prompt.

2. Navigate to the directory containing the offline package.

3. To run on Chrome, use: java -jar qualitiaoffline-xxxx.jar googleChrome.chromeOptions.args=--headless

4. For Firefox execution, input: java -jar qualitiaoffline-xxxx.jar firefox.firefoxOptions.args=--headless

🔧 Got a problem? Let’s fix!

1. Execution is getting aborted after triggering the suite for offline execution. “Fatal exception during execution”: You might get this error if the Test Case name contains slash (/). To successfully execute an offline suite, avoid using slash in the Test Case name.