You are using an older browser that might negatively affect how this site is displayed. Please update to a modern browser to have a better experience. Sorry for the inconvenience!

Cross browser testing using Jenkins with Parallel Execution

Jenkins is a Continues integration testing tool. It is an open source automation server used to build a software, test and deploy the software. There are many plugins are available in Jenkins tool.


  1. Jenkins supports Continuous integration testing.
  1. It supports test libraries, including Selenium.
  1. It is an open-source automated integration tool.
  1. It provides simple and very detailed test reports.
  1. Deploys directly to production or test environments.


  • Before you install Jenkins, you will need to install Java SDK.
  • Robot framework with Python. Test cases should be pushed to Github branch.

Jenkins Installation: 

  1. Download the Jenkins standard version from the following website
  1. You would be able to run Jenkins from the Command Line by opening a Command Prompt and browsing.
  1. War files downloaded to local folder. Then set the environment variable.
  1. Run Jenkins server and enter the Jenkins password authentication key.
  1. Execute the command below in the command window.

Java -jar Jenkins. War –httpPort=8080 (we can choose our own http port)

After finishing the Jenkins installation, open the browser and enter the local host domain ‘http://localhost:8081’.

Manage Jenkins Plugins:

cross browser testing

Click the Manage Jenkins sidebar menu and then click manage plugins link. Search the Robot framework plugins and installed the plugins by opening the available tab in the Manage Plugins menu.

Building A New Multi configuration Project: 

Open the Jenkins in browser by using command prompt and then create new jobs.

Enter your project name and choose project job execution method.

cross browser testing

Source Code Management: 

Choose the Source code management as Git and then enter your source code management repository URL path. Specify the git branch location in the Branch specified section by clicking Add branch button. In this section, the master branch is updated as default branch.

Gitgub Location:

Step 1: 

cross browser testing


cross browser testing tools

Build Triggers: 

After completing the source code management set up, select the automation triggers times. There are five types of triggers method. We can use the Poll SCM method.

cross browser testing tools

Here the Poll SCM build trigger option is used to check every project’s frequency configured on your source code management.

Configuration Matrix:

The Configuration matrix section is used to define the job execution process. Configuration Matrix has three different job execution method.

Click the Add Axis button and then enter your user defined axis. Enter your test execution browser list.

cross browser testing tools

Build Environment and Build step: 

There are four types of options are available in this section. Here, we can select our build environment setup.


Build method is used to choose the job execution method. Go to the Add build step dropdown and then choose the ‘Executes Windows batch command’ method and then enter the following command.

pybot –variable BROWSER: $BROWSER *.txt

For example (pybot –variable BROWSER:$BROWSER Service_cloud.txt)

cross browser testing tools

Post-build Actions 

This action is used to publish your test results after your job execution. Here, there are multiple types of build actions are available. Click the Add-post build action drop down and then select Publish Robot Framework test results action.

cross browser testing tools

Enter the output directory location for this job execution and then enter the build result threshold values. Finally, click the Save button. The project is saved, and the project details will be displayed on the Jenkins dashboard.

Test Execution:

Click the project in the dashboard and then run the test by clicking ‘Build Now’ option.

cross browser testing tools

The test has been executed parallel in multiple browsers at the same time. At the end of the test execution, it provides the detailed test results in the project page dashboard.

Test Report: 

Build history is displayed on the left side and the test results are displayed on the project home page with detailed reports including whole versions of build execution result. Also, it generates the console output.

Report 1: 

cross browser testing tools

Console Output: