Run tests using a CI system
The procedure below focuses on Jenkins, but you can apply the same concepts to most CI systems.
Note: If you are running UFT Developer tests from Jenkins, you can track the tests in ALM. For details, see the ALM Help Center.
Install the UFT Developer runtime engine and your AUT on the slave.
If your tests were created in the context of a unit testing framework (such as NUnit or JUnit), make sure that the relevant framework's runner is also installed on the slave computer.
Deploy the UFT Developer tests (DLLs/JARs) to the slave computer.
Configure the Jenkins slave to maintain an active Windows session. This is needed so that the UFT Developer runtime engine can access the UI elements of your AUT during the run.
For non-Web applications:
On the slave computer, start the UFT Helper service from: Computer > Manage > Services and Applications > Services.
Note: Make sure the service starts before the UFT Developer runtime engine.
In the Engine tab of the UFT Developer Settings dialog box, under Runtime Settings, enter the user name and encrypted password of the slave computer.
To generate the encrypted password, run the following command line from the slave computer and copy the encrypted string to the clipboard:
<UFT Developer installation>\bin\PasswordEncryption.exepasswordToEncrypt
Note: The encrypted password is based on the computer where you run the utility, so make sure to generate the password on the computer where you plan to use it.
Configure your Jenkins job to run your UFT Developer tests.
For example if your tests were created in the context of an NUnit project, your build step may look like this:
<NUnit Path>\bin\nunit-console-x86.exe" "%PATH_TO_TEST_PROJECT_DLL%\DLLFileName.dll
- Optional. Configure your job to archive the UFT Developer HTML report files, so that they are available in Jenkins for each build of your job. You can also customize your job to include a direct link to the UFT Developer report file for each build.
- UFT Developer blog: Integrating UFT Developer with Jenkins—in just a few simple steps