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 an Offline Suite using CLI Commands
· Use Case: You want to run tests offline using command prompt due to limited access to the QAS client.
· First, open the Command Prompt.
· Move to the location of your saved offline package.
· Input: java -jar qualitiaoffline-8.6.x.jar to execute the offline package with the default settings.
· However, if you wish to override certain settings:
· For a custom execution profile, use: java -jar qualitiaoffline-8.6.x.jar "Path_to_JSON"
· To specify a different offline suite: java -jar qualitiaoffline-8.6.x.jar SuitesDir="Path_to_Suite"
· For custom environment variables: java -jar qualitiaoffline-8.6.x.jar env.var1=value1 env.var2=value2
· And for other specific parameters in the execution profile, follow the hierarchy as in java -jar qualitiaoffline-8.6.x.jar parameter=value.
· Press Enter to initiate the offline suite execution.
Viewing an Offline Suite Execution Report
· Use Case: After running the tests, you need a comprehensive report to analyze the results.
· Instantly check the results on the Real Time Reporting Portal.
· Additionally, the offline suite creates a detailed summary report based on the location set in the Qualitia Offline Configuration Manager's General Settings tab.
· If the report isn't available on the Real Time Reporting Portal after completion, you can manually upload the locally saved report.
Editing the Test Data for an Offline Suite
· Use Case: Before re-running tests or for a different testing scenario, you might need to change some test data.
· One way to modify is through the Qualitia Client:
· Open your test case from the client.
· Access the Test Data explorer to edit.
· After changes, recreate the offline suite.
· Alternatively, you can also edit the test data directly in the Excel file located in the Offline Suite Folder. But, using the Qualitia Client is recommended as it provides error alerts for incorrect data modifications.
By following this guide, SDETs can efficiently set up, execute, review, and modify offline tests in QAS, ensuring a versatile and adaptable testing process.
Editing Test Data in Offline Suite Test Data File
Introduction:
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 SDETs, ensuring that they can quickly and effectively adapt their test cases as needed.
Prerequisites:
· An offline suite with associated test data.
· Basic knowledge of Excel and data formats.
Process Flow:
Basics of Editing Test Data
· Use Case: You want to quickly adjust test data without altering the structure of the file.
· Don't add or remove columns, or change the column order.
· Use $NULL$ where you don't want to set a value for a parameter.
· Delete rows for unwanted task or test case (TC) iterations.
10. Steps to Modify Test Data for an Offline Suite
· Use Case: You need to adjust the test scenarios based on new requirements.
· First, go to the offline suite folder.
· Backup the test data file you'll edit.
· Open the test data Excel file.
· From the third row, tweak values as needed. The first row shows tasks in grey, with the second row detailing their parameters.
· To add a TC iteration, insert a row with values for TC Iteration number, Selection, and DataSetTag (optional).
· For adding a task iteration, insert a row with values for associated parameters.
· Always save the Excel file after editing.
11. Executing Offline Suite on a Shared Drive
· Use Case: 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.
12. Executing a Shared Offline Suite by Mapping the Shared Drive
· Use Case: For a more seamless experience, you might prefer mapping the shared drive to your local system.
· Copy both the offline package and suite to the shared drive ensuring you have read and write permissions.
· Map this shared drive to your local computer.
· Adjust the offline suite settings as needed. For a detailed guide, look into "Configuring the Settings for an Offline Suite".
· To execute:
· Use the Command Prompt, navigate to the mapped location, and execute the offline package with the right command.
· Or simply double-click the offline package (8.6.x jar) in the mapped drive.
By following this guide, SDETs can efficiently manage, adjust, and execute their test scenarios, ensuring accurate results even in offline or shared environments.
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.
Prerequisites:
13. Familiarity with Qualitia Automation Studio (QAS).
14. Knowledge of Continuous Integration tools like Jenkins, TeamCity, and Bamboo.
15. Access to the offline package and suite for execution.
Process Flow:
Executing an Offline Suite from a Shared Drive without Local Mapping:
Method: Direct execution from the shared drive. Steps:
· Copy both the offline package and suite to the shared drive, ensuring you have read/write permissions.
· Directly access the shared location and initiate the offline package by double-clicking on the 8.6.x jarfile.
· Note: Using the command prompt with the full UNC path for execution isn't supported.
Running Offline Suite for Desktop Applications on a Shared Drive:
Method: Local execution after mapping. Steps:
· Before starting:
· Install UFT on the computer meant for execution.
· Map the shared drive locally.
· Copy the offline package to the shared drive with appropriate permissions.
· Ensure the TSR file is available and accessible.
· Configure the offline suite. For more details, see "Configuring System Execution Profile for Desktop Projects".
· Choose either:
· Use the command prompt, navigate to the mapped drive with the offline package and suite, and initiate using commands.
· Or, directly access the mapped drive and start the offline package by double-clicking the 8.6.x jarfile.
Execution using Continuous Integration Tools:
Method: Integration via QAS settings. Steps:
· Ensure QAS's capability to integrate with CI tools like Jenkins, TeamCity, and Bamboo.
· For mobile application tests, even though QAS hosts the Appium Server internally, use a custom Appium server for different Appium versions if needed.
· Set the CI_Tool property in the mapped execution profile before starting.
Headless Executions:
Method: Browser-based testing without GUI. Steps:
· Recognize that headless executions run faster since they don't launch the browser UI. QAS supports this for Google Chrome and Mozilla Firefox.
· To execute tests in headless mode:
· Via QAS Client/OfflineConfigManager:
16. Open the associated execution profile.
17. Choose the browser.
18. Activate the respective headless setting.
· Via CLI:
· For Chrome: java -jar qualitiaoffline-xxxx.jar googleChrome.chromeOptions.args=--headless
· For Firefox: java -jar qualitiaoffline-xxxx.jar firefox.firefoxOptions.args=--headless
· Note: Xvfb on Linux isn't supported anymore. Use the methods mentioned for headless execution on Linux.
Method: Setup via Qualitia Client or OfflineConfigManager.
Steps:
19. Open the associated execution for a test suite.
20. From the Browser list, select either Chrome or Firefox.
21. Check the "Desired Capabilities" checkbox.
22. Based on your browser choice:
· For Chrome:
· Select the chromeOptions checkbox.
· Check the args checkbox.
· Input --headless in the associated field.
· For Firefox:
· Select the firefoxOptions checkbox.
· Check the args checkbox.
· Input --headless in the associated field.
23. Click "Ok".
Method: CLI-based execution for headless mode.
Steps:
24. Open the Command Prompt.
25. Navigate to the directory containing the offline package.
26. To run on Chrome, use:
· java -jar qualitiaoffline-xxxx.jar googleChrome.chromeOptions.args=--headless
27. For Firefox execution, input:
· java -jar qualitiaoffline-xxxx.jar firefox.firefoxOptions.args=--headless
In conclusion, this guide ensures that SDETs have the tools and knowledge to execute offline suites, integrate with CI tools, and utilize headless executions effectively.