Header

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

You can execute the test cases using an offline package after configuring settings accordingly. This gives you the provision to trigger suite execution using any machine in the network. You do not need to move the offline package to different machines to execute it.

You can do it in the following two ways:

Normal Remote Execution

This option can be used when you are aware of the remote machine details where you wish to execute your test cases.  You need to choose to execute offline package on a remote machine with specific details.

Qualitia uses the selenium-standalone-server-jar for test case executions on the target remote machine.

To run selenium-stand- alone jar:

  1. Download the selenium-standalone-jar on the target machine where you want to execute test cases.

  2. Download the drivers corresponding to the offline execution browser (chromedriver, IEdriverServer, and so on) and store it in the same location where the Selenium-stand-alone-jar is saved.

  3. Open the Command Prompt window and navigate to the location where offline jar is located.

  4. Do one of the following:

    • If the execution browser is Iexpore and Selenium sever standalone version is 2.xx.x, execute following command: java -jar selenium-server-standalone-2.45.0.jar - Dwebdriver.ie.driver="D:\Data\Testing\Apps\IEDriverServer.exe”.

    • If the execution browser is Iexpore and selenium sever standalone version is 3.xx.x, execute following command: java -Dwebdriver.ie.driver="D:\Data\Testing\Apps\IEDriverServer.exe" -jar selenium-server-standalone-3.0.1.jar

Configuring the Settings for a Normal Remote Execution

Once you download Selenium-stand-alone jar and browser drivers, you need to change some settings.

Either you can create an execution profile to execute on the remote environment or edit an existing execution profile for execution on remote environment.

For detailed instructions on using execution profiles,  refer to Working with Execution Profiles.


To configure the settings for a Normal Remote Execution:

  1. Do one of the following:

    1. To execute from a Qualitia client, open the associated execution profile.

    2. To execute an offline suite, do the following in the order listed:

      1. Open the offline package folder.

      2. From the Configuration Manager folder, and double-click the Qualitia Offline Configuration Manager. 

      3. Do one of the following;

        1. Click Browse next to Select the Suite Directory, and then locate and select the offline suite.

        2. Enter the location path of the offline suite folder, and press Tab.

    3. Under the Select the profile to edit, select the execution profile created to execute on remote environment.

    4. Select the associated execution profile that is defined to execute on remote environment.

    5. From the Mapped Execution Profile list, select the execution profile you have opened.

  2. Set the ExecutionEnvironment as Remote.

  3. Set the RemoteURL value to a valid remote URL that is IP and port of remote machine.
    For example: RemoteURL=http://192.168.25.123:4445/wd/hub

  4. Click Save.

Suite Execution

Execute the test suite or offline suite you have configured. To know how to execute an offline package, refer to Work with Offline Package.


  • In case you have multiple versions of java, Qualitia uses the version set against the "JAVA_HOME" system variable under System Properties settings of your computer.

  • To execute mobile test cases using Selenium grid, make sure that Appium server is up and running on the designated node.

Remote Execution through Selenium Grid

What is a Hub?

The Hub is the main command center for managing which machines your test will run on. This is where you can see list of all the available nodes currently running in your grid environment (Remote Execution Environment).

What is a Node?

A Node is a machine that you register with your Hub. By registering with Hub, the Hub now knows about the Node and any configuration information you used when you registered the node.

In order to perform remote execution through Selenium grid, you need to configure Hub and Node in the network.

Creating a Hub in the Network

A Hub can be created in the network following the steps mentioned below.

  1. Decide a machine in the network to register as hub (with IP, for example, 192.168.25.6).

  2. Download the Selenium-server-standalone jar file on Hub machine.

  3. Open Command Prompt and navigate to the location where Selenium-server-standalone-jar is saved.

  4. Execute command "java -jar selenium-server-standalone-2.xx.0.jar -role hub -port 4445".


Create Node and Register to Hub

Once a hub is created in the network, you can select multiple machines to act as its nodes. Registering nodes include the following steps.

  1. Download the Selenium-server-standalone jar file on the node machine.

  2. Launch the command prompt and navigate to the location where Selenium-server-standalone jar file is saved.

  3. Execute command "java -jar selenium-server-standalone-2.xx.x.jar -role node –hub http://hubIP:4445/grid/registerr".

You can bundle your IEServerDriver.exe, Geckodriver.exe, or ChromeDriver.exe running while registering to Hub.

Configuring the Settings for Execution through Grid

Prior to executing test cases in remote execution in the Selenium grid, you need to configure settings accordingly. Here are some important points to keep in mind when configuring settings for remote execution in the Selenium grid.

  • Selenium server jar version used in Qualitia offline package and downloaded at remote machines including Hub and Nodes must be the same all over.

  • Java needs to be installed and configured in the computer’s environment path.

  • Port number used for the hub is changeable and the default port number is 4444.

  • As hub selects a node for execution at its own at run time, you cannot provide details for specific OS / Platform.

  • To know more about how to setup Selenium grid hub and node, you recommend using the Selenium grid links given below.

Either you can create an execution profile to execute on the remote environment or edit an existing execution profile. For more information, refer to Working with Execution Profiles.

To configure the settings for executing through Selenium Grid:

  1. Do one of the following:

    • To execute the test suite from a Qualitia client, open the associated execution profile.

    • To execute the offline suite, do the following in the order listed:

      1. Open the offline package folder.

      2. From the Configuration Manager folder, and double-click the Qualitia Offline Configuration Manager. 

      3. Do one of the following;

        1. Click Browse next to Select the Suite Directory, and then locate and select the offline suite.

        2. Enter the location path of the offline suite folder, and press Tab.

      4. Under the Select the profile to edit, select the execution profile created to execute on remote environment.

      5. Select the associated execution profile that is defined to execute on remote environment.

      6. From the Mapped Execution Profile list, select the execution profile you have opened.

  2. Set the ExecutionEnvironment as Remote.

  3. Set the RemoteURL value to a valid remote URL that is IP and port of remote machine.
    For example: RemoteURL=http://192.168.25.123:4445/wd/hub

  4. Set the GridPlatform value to a valid platform where you want to execute test cases. For example: Set the GridPlatform=Win10.

  5. Click Save.

Suite Execution

Execute the test suite or offline suite you have configured. To know how to execute an offline package, refer to Work with Offline Package.


  • In case you have multiple versions of java, Qualitia uses the version set against the "JAVA_HOME" system variable under System Properties settings of your computer.

  • To execute mobile test cases using Selenium grid, make sure that Appium server is up and running on the designated node.


  • No labels