Configuring the Qualitia Remote Agent
After you have successfully install Qualitia remote agent, you can configure it to integrate to Qualitia project for automating test cases.
To configure the Qualitia Remote Agent:
- Click the Qualitia - Integration Remote Agent icon present on your desktop.Â
- Do one of the following:
To execute test cases for a pipeline on web and mobile applications | Do the following in the order listed:
|
To execute test cases for a pipeline on desktop applications | Do the following in the order listed:
 For more details, refer to Configuring the System Execution Profile Settings for a Desktop Project. |
Â
Points to Know
General
- For Capture Screenshot, if you select Fail or Defect checkbox, or both of them, you can view the associated screenshots in Azure DevOps. After the test case executions in the pipeline, open Azure DevOps, go to Result Tests > Attachments, you can now view the screenshots of steps as per the selected execution status (Fail, Defect, or both).
- The custom actions compiled with Java 7 or earlier versions might not work as expected. Recompile those custom actions again with Java 8.
For Web ApplicationsÂ
- All the latest browser drivers are shipped with Qualitia.Â
- Gecko Driver can be used for versions before FF-48 but Mozilla does not guarantee 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.
- For more information on the Selenium Server Jar, click here.
For Mobile Application
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 a new simulator each time to perform test case execution.
Android Devices:
- If UDID is not specified, test cases will be executed on the last connected device.
- Entering incorrect UDID results in failing test case execution.