Jenkins uses plugins to extend its functionality and integrate with other tools. To run Ranorex Studio tests in Jenkins, you must install and configure the required plugins. Some plugins are mandatory for Ranorex integration, while others are optional and provide additional functionality. Depending on your Jenkins installation, some of these plugins may already be installed. This article explains how to access plugins in Jenkins, which plugins are required or optional, and which configurations are needed for Ranorex integration.
Access plugins in Jenkins
To open the plugin manager in Jenkins:
Click Manage Jenkins
In the plugin manager:
- Installed plugins are listed on the Installed tab.
- Plugins available for download are listed on the Available tab. You can use the filter field to search for a specific plugin.
Required and optional plugins
The following plugins are relevant for integrating Ranorex Studio with Jenkins.
Ranorex Test Execution Plugin
Install this plugin so Jenkins can recognize and process Ranorex Studio test execution.
MSBuild Plugin
Install this plugin so Jenkins can compile and build the Ranorex Studio solution before test execution.
GitHub Plugin
This plugin is optional and is often preinstalled.
Use this plugin if your Ranorex Studio solution is stored in a GitHub repository. It allows Jenkins to access GitHub-hosted projects. If you use another repository provider, you may need a different plugin instead.
JUnit Plugin
This plugin is optional and is often preinstalled.
Use this plugin if you want Jenkins to publish test results in JUnit format. This is useful when Ranorex reports are converted for Jenkins reporting.
Configure plugins
Some plugins require additional configuration before they work correctly with Ranorex Studio.
Configure Ranorex Test Execution Plugin
- Click Manage Jenkins
- Click Configure System
- In the Ranorex Integration section, enable Summarize arguments in Console output.
- Click Save
Configure MSBuild Plugin
- Click Manage Jenkins.
- Click Global Tool Configuration.
- Click Add MSBuild.
- Enter a sensible name for the build.
- Enter the path to your local .NET installation.
- Click Save.