Document toolboxDocument toolbox

Header

Qualitia Remote Agent Installation and Configuration

Owned by Dhiraj Chandanshive (Unlicensed)
Last updated: Jun 15, 2022
3 min read

Along with the Azure DevOps Agent, you need to install and configure Qualitia Remote Agent which helps in establishing connection between Azure DevOps and Qualitia Servers.

This section covers procedures for installation and configuration of Qualitia Remote Agent.

Installing the Qualitia Remote Agent

 

Qualitia Remote Agent is a component that helps Azure DevOps agent to execute Qualitia automated test cases. Azure DevOps agent hosts Qualitia remote agent. The Qualitia Remote Agent helps to retrieve the published Qualitia test cases from the Qualitia Server to execute the test cases for the Azure DevOps .pipeline. During a pipeline execution, the results are pushed to Qualitia server for Real-Time Reporting.

Hence, Qualitia remote agent must be installed on the same system where Azure DevOps agent is installed. If you want to have parallel execution on a same computer, you can install and configure multiple Azure DevOps Agent.

To install the Qualitia Remote Agent:

  1. Log on to the system where Azure DevOps self-hosted agent in installed.

  2. Copy the IntegrationRemoteAgent folder from Qualitia Setup folder to any temporary location.

  3. Open the folder and double-click the QualitiaIntegrationRemoteAgent.exe.

  4. Post installation Qualitia - Integration Remote Agent icon will appear on desktop.
    You can set up the remote agent anytime based on the requirements. For more information about this, refer to Configuring the Qualitia Remote Agent section.

 

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:

  1. Click the Qualitia - Integration Remote Agent icon present on your desktop. 

  2. Do one of the following:

To execute test cases for a pipeline on web and mobile applications

Do the following in the order listed:

  1. Select the Project Type as Web/Mobile.

  2. Click the General Tab to configure the following settings:

    1. Under Integration Details, enter the Azure DevOps URL, in Server URL.
      Note: You can click Test Connection to verify whether the connection to Azure DevOps is successful.

    2. Under Dependency Path and Web/Mobile Settings, configure the required settings. For more details, refer to Configure the Project Settings.

  3. Click the Execution tab to configure the settings required to execute the test cases on web and mobile environments. For more details, refer to Configuring the System Execution Profile Settings for a Web/Mobile Project.

To execute test cases for a pipeline on desktop applications



Do the following in the order listed:

  1. Select the Project Type as Web/Mobile.

  2. Click the General Tab to configure the following settings:

    1. Under Integration Details, enter the Azure DevOps URL, in Server URL.
      Note: You can click Test Connection to verify whether the connection to Azure DevOps is successful.

    2. Under Dependency Path and Desktop Settings, configure the required settings. For more details, refer to Configure the Project Settings.

  3. Click the Execution tab to configure the settings required to execute the test cases on desktop environments

 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.









 

Footer