A new version of Qualitia Automation Studio for Web and Mobile 7.2.x is now available. We highly recommend you upgrade. Find more details here.
Qualitia Remote Agent Configuration
- Sagar Dubewar (Unlicensed)
Dependency
From this section, you add paths to all the dependencies such as project path, report path and so forth.
By default, Qualitia auto-creates and sets values for these fields. You may further update directories based on the requirements.
Dependency | |
|---|---|
| Project Path | This is the directory where Qualitia stores all the project-related data on the local system. |
Report Path | This is the directory where Qualitia stores all the report-related data on the local system. |
Log Path | This folder stores all the execution logs which you can use for troubleshooting in case there are any problems during test case linking and execution. |
| XML Path | This is the path where all the execution XMLs are stored. |
| Custom Action Repository Path | Select the folder where your Custom Action files exist. 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. |
Java Path | Select the absolute path where you have installed Java 8 (java.exe). This can be either Oracle JDK / Open JDK. |
| Selenium Server Jar Path | Select the absolute path to the Selenium Server JAR. This is set by default. In case you want to use different version of jar, you may change it here. |
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 test cases. 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 to 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 Qualitia automation version 5.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. |
| Build Number | Enter the build number based on the project requirements. |
| Release Number | Enter the release number based on the project requirements. |
- All the latest browser drivers are shipped with Qualitia.
- 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.
Platform
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 seconds. |
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 test case execution.
Not finding what you need?
