The Qualitia remote agent links Qualitia with HP-ALM.
It allows you to:
- Export Qualitia tests cases into ALM
- Arrange them into ALM test sets
- Run test cases from ALM, and
- Store their results into ALM.
Using this agent, engineering and test teams that use ALM can implement the seamless integration of manual test cases managed by ALM with Qualitia automation test cases.
To install Qualitia-ALM Remote Agent:
- Navigate to the folder where you have kept Qualitia Installables.
- Copy the the QCRemoteAgent to the machine where you want to install it.
- Double-click Setup.exe.
- Installation wizard appears and completes the installation process.
You have to add General, Dependency, Execution, and Platform related settings for the remote agent. - On your Desktop, double-click Qualitia Remote Agent.
- Fill up the details in General, Dependency, Execution, and Platform sections as described below.
General
From this section, you can provide Project, Database, and License Server related settings.
| Project Name | Enter the name of the Qualitia project which you want to integrate to ALM. |
|---|---|
| Database Server | |
| Type | Select the database server from the drop-down list: SQL Server and MySQL. |
| Authentication Type | Select the authentication type: Windows Authentication or SQL Server Authentication This field is applicable for SQL server only. |
| Server: Port | Enter the Server and the Port IDs. Default port is 3306 for MySQL and 1433 for SQL. |
| User Name | Enter database server user name. |
| Password | Enter database server password. |
| SVN Server | |
| SVN Client | Select the version of SVN Client you are using. |
| User Name | Enter the SVN Server user name. |
| Password | Enter the SVN Server password. |
| License Server Host/IP Address | |
| Host/IP Address | Enter the IP address or the host name of the server where you have installed License Service. By default, License service is deployed with the installation of Qualitia Server. |
Dependency
From this section, you add paths to all the dependencies such as project path, report path and so forth.
Dependency | |
|---|---|
| Project Path | Select the folder where your project is saved on the local machine. |
Report Path | Select the folder where you want to save all your execution reports. |
Log Path | Select the folder where you want to save logs. |
| XML Path | Enter the path where you want to save the execution XMLs. |
| Custom Action Repository Path | Select the folder where your Custom Action Repository exists. Multiple paths should be separated with semi-colon (;) and the last path should be ended by semi colon (;). |
AutoIT Install Path | Select the folder where have installed AutoIT. For more information about this, click here. |
Java 8 Install Path | Select the absolute path where you have installed Java 8 (java.exe). |
| Selenium Server Jar Path | Select the absolute path to the Selenium Server JAR. |
Execution
The Execution section under Configuration Settings window allows configuring settings related to test case execution.
Execution | |
|---|---|
Wait Mode | Select Wait Mode from the drop-down list. Default is Explicit. |
| Timeout | Enter the maximum time to wait (in seconds) for the object to load on the page when executing the test case. Default is 10. This option is available for Explicit wait mode only. |
| Sync Time | Enter the maximum time to wait (in seconds) for an object to load when executing the test case. Default is 20. This option is available for Implicit wait mode only. |
| Polling Interval | Enter the polling interval in milliseconds. Default is 100. |
| Page Timeout | Enter maximum time to wait (in seconds) for the page to load when executing the test case. Default is 20. |
| Report Logs | Select appropriate options for which you want to save logs when executing test cases. |
| Screen Capture Mode | Select the screen capture mode: Desktop or Browser. Default is Desktop. |
| Fail Step on Screenshot Failure | Selecting this option fails steps if browser screenshot is not captured when executing test case. This option is available only if the screen capture mode is selected as Browser. |
| Highlight Active Element | Select this option if you want to highlight the element on which action is being performed from the application under test during test case execution. |
| Optimization Mode (Experimental) | Selecting this option eliminates object level waits and improves performance when executing Qualitia test cases. Deselect this option if you experience failures for your test suites created before v5.2. |
| Show Report After Execution | Selecting this option launches test case execution report after the execution is complete. |
| Ignore Angular Synchronization | Select this option if you want to disable Angular synchronization with the page before performing any action. This may cause test case failure and should be used only when necessary. |
| Capture Snapshots on | Select options for which you want to capture screenshots while executing test cases. You can select multiple options. |
| CI Tool | Select the CI Tool from the drop-down list (if you use any). You can execute Qualitia bot using CI Tools. For more information about this, refer to the Execution using Continuous Integration Tools section. |
New Browser for Every | Select when you want to launch new browser; for every Suite or for every Testcase. This is applicable for Web (Desktop and Mobile) applications only. |
- Browser drivers are shipped with Qualitia. You may find on the following path: C:\Users\<User Name>\AppData\Local\QualitiaWDClient\app-4.x.x\WebDriver\Selenium.
- If browser is selected as Firefox, user should point to Gecko Driver on the location mentioned above.
- Gecko Driver can be used for versions before FF-48 but Mozilla does not guarantee a flawless executions on versions before FF-48.
- To execute test cases on Firefox v48 and above, select Selenium server 3.0 (on the execution tab) and select the Gecko Driver path.
- Safari executions are now supported on Mac Sierra or later using Apple’s Safari driver.
- For IE only versions 9 and above are supported as Microsoft has stopped supporting earlier versions.
- The custom actions compiled with Java 7 or earlier versions might not work as expected. You might need to compile them again with Java 8.
- For more information on the Selenium Server Jar, click here.
Configuring Platform Settings
The Platform section under Configuration Settings window allows configuring settings related to test case execution platform.
| Desktop Web | |
|---|---|
| Browser Type | Select the browser which you want to use for test case execution from the drop-down list. |
Browser Driver Path | Select the browser driver path based on the browser selected above |
Browser Profile Path | Select the browser profile path if you want to execute test with specific browser profile. |
| Mobile | |
Server: Port | Enter Appium server and port details. Default is 127.0.0.1: 4723. |
Platform | Select platform for test case execution: Android or iOS. |
UDID | For Android: Enter the device ID. For iOS: Enter device identifier on which you want to execute test cases. For more information about this, please refer to the How to Identify UDID in Frequently Asked Questions (FAQs). |
Mobile Browser | Select the mobile browser on which you want to execute test cases. |
Execute on Mobile Web | Select this option if you want to execute test on the mobile device. |
| Native Object Sync Time | Enter the number of seconds for which Appium will wait for a native object to appear. Default is 2. |
For iOS Devices:
- Qualitia users can keep this field empty and specify the Device Name + Platform Version in iosdc.properties file.
(Located at: %LocalAppData%\QualitiaWDClient\app-<version\WebDriver\config) - Device name is mandatory.
- If Platform version is not specified, Appium considers the latest platform version (for example, 10.3) and creates new simulator each time to perform test case execution.
For Android:
- If UDID is not specified, test cases will be executed on the last connected device.
- Entering incorrect UDID results in failing the test case execution.
