Integration with Jenkins

You can use the HCL OneTest™ UI - Functional Test to run tests on a Jenkins server.

To automate testing with Jenkins, you must configure Jenkins primary server and Jenkins secondary server. This configuration provides a single Jenkins installation on the Jenkins primary server to host multiple Jenkins secondary server for building and running tests. For more information about the Jenkins primary and secondary server relationship, refer to the Jenkins documentation.

You must install the required version of the HCL OneTest™ UI - Functional Test plugin on the Jenkins primary server, and install HCL OneTest™ UI on the Jenkins secondary server, where you create tests.

You can use either the Jenkins Freestyle project or the Pipeline project to run test assets from Jenkins. With Freestyle project, you can create a build step from the Jenkins UI to run the test assets. Whereas the Pipeline project uses a simple text scripts based on the Groovy programming language. You can define pipeline scripts during the configuration of the Pipeline project by using any of the following methods:

  • Pipeline script: In this method, you can directly enter a script in the field provided within the Jenkins UI or you can select a sample Pipeline script from the drop-down list.

  • Pipeline script from SCM: In this method, you can create a script with a Groovy editor and then commit the script file into the Git repository.

For more information about the Jenkins Pipeline, refer to the Jenkins documentation.

Refer to the following topics to learn more about integrating Jenkins with HCL OneTest™ UIin the Functional Test perspective: