Web tests, such as selenium tests, can be conducted on distant slave workstations using the master-slave and selenium suite plugin installation. The methods below demonstrate how to use this configuration to perform remote tests.

Step 1 Ensure that your master-slave configuration is in place. Navigate to your master Jenkins server. Navigate to Manage Jenkins > Manage Nodes. The DXBMEM30 identifier identifies the slave machine in our node list. Both the master and slave workstations in this scenario are Windows machines.

Step 2 – For the DXBMEM30 slave machine, click on ‘Configure’.

Step 3 − Ensure that the launch method is put as ‘Launch slave agents via Java Web Start’

Step 4 − Now, go to your slave machine and open a browser instance to your Jenkins master instance from there. Then select Manage Jenkins > Manage Nodes. Navigate to DXBMEM30.

Step 5 − Click on ‘DXBMEM30’ instance.

Step 6 − Scroll down to find the ‘Launch’ option to Start ‘Java Web Start’

Step 7 − A Security Warning will be displayed to you. Select the Acceptance checkbox and then press the Run button.

You can now see a ‘Jenkins Slave window’ opened and connected.

Step 8 − Setting up your tests to run on the slave. You must guarantee that the job being created is only intended to perform the Selenium tests.

Make sure the option 'Restrict where this project can be run' is chosen in the task configuration, and enter the slave node's name in the Label expression.

Step 9 − Ascertain that the Selenium component of your job is configured. You must ensure that the slave machine has both the Sample.html and the selenium-server.jar files.

After completing all of the preceding steps and clicking Build, this project will perform the Selenium test on the slave machine as planned.