Integrate UFT with Jenkins Guide

1 Introduction
This document will guide you how to deploy Jenkins (Ver Windows) and how to do continuous
integration by using HP Application Automation Tools with Jenkins. The plugin “HP Application
Automation Tools”(Ver 2.02) allows Jenkins to trigger HP tests such as: Test sets on Application
Lifecycle Management, tests saved on the file system from Unified Functional Testing, QuickTest
Professional, or Service Test, and LoadRunner scenarios.

About this Plugin

This plugin allows you to trigger an HP test as a build step and present the results in the Jenkin's
UI, similar to JUnit.

This plugin currently supports:

* HP Unified Functional Testing 11.50 (QuickTest Professional and Service Test 11.50 capabilities)
* HP Service Test 11.20 and 11.50
* HP LoadRunner 11.52
* HP QuickTest Professional 11.00
* HP Application Lifecycle Management 11.00 and 11.52
* HP ALM Lab Management 11.50 and 11.52
* HP Quality Center 10.00, with the QuickTest Professional Add-in for triggering test sets

2 Deploy Jenkins (Ver Windows)

2.1 Deploy JAVA and Tomcat environment

You can find all necessary installation packages from the remote link.
a) Install jdk, double click “jdk-6u45-windows-i586.exe”.
b) Unzip “apache-tomcat-7.0.47.zip” to “C:\Apache”.

2.2 Configure Environment Variables

Set System Environment Variables as below:
a) JAVA_HOME = C:\Program Files (x86)\Java\jdk1.6.0_45
CATALINA_HOME = C:\Apache\apache-tomcat-7.0.47
b) Update “%Path%”. Add “%JAVA_HOME%\bin” and “%CATALINA_HOME%\bin” to “%Path%”.
2.3 Start Tomcat and Publish Jenkins
a) Copy “jenkins.war” to “C:\Apache\apache-tomcat-7.0.47\webapps”
b) To run “C:\Apache\apache-tomcat-7.0.47\bin\startup.bat” to start the Tomcat application
in cmd.

c) If the message “Jenkins is fully up and running” pops up at the screen. It means the
Jenkins has been published successfully.

Jenkins Local URL:

http://localhost:8080/jenkins
 Jenkins Remote URL:
http://Hostname:Port(or IP address:Port)/ Jenkins
(such as “http://c0005226.itcs.hp.com:8080/jenkins”)

d) If you prefer, you can update the Jenkins Services configuration to “Automatic Started”.

3 Install the Plug-in of HP Application Automation Tools

a) Login to Jenkins.
b) Click the link “Manage Jenkins” -> “Manage Plugins”, then click “Advanced” tab.
c) Enter the Server “web-proxy.rose.hp.com” and Port “8088”, then click “Submit”.

d) Click “Available” tab.

e) Filter the name “HP Application Automation Tools”.
f) Click on the Install checkbox and click on the “Download Now and Install After
Restart“ button.
4 Configure Jenkins

4.1 Set up a job

Once the add-in is installed and you have restarted Jenkins:
a) Click on the “Jenkins“ -> “New Job“ menu option.
b) Enter a Job Name (such as “UFT”), and click on the ”Build a free-style software project
option”. Click “OK”.

c) Under the your new project’s configuration scroll down to the “Build“ section and click on
the “Add build step“ and click on the Execute “HP tests from file system“ option.

d) In the Tests box, enter a test with its full absolute path, or a folder or MTB containing one or
more tests or scenarios. To specify multiple entries, click the down arrow on the right of
the field and enter each test path on a separate line. Make sure that the paths are
 accessible from all machines in the local network. For example, if you want to run these
case as below:

ECS-1711a_Server Configuration_Check Password_Commercial

Non_Authority_Assign_Role
You must configure the tests box like the following graph. Of course, you can configure
“C:\Vivi_AT\AT SourceCode\BPT” when you’re fully running all of the cases in “BPT” folder.

e) Optionally, indicate a timeout in seconds after which the job will fail in the Timeout box.

4.2 Set up the Post Build Actions

a) Under the ”Post-build Actions” section click on the ”Add post-build action” and
select ”Publish HP tests result”.

b) Select an archiving option for the test run results:

* Archive test run results for failed tests - save test results for failed tests only
* Always archive test run results - always save test result reports
* Do not archive test run results - never save the test results
 c) ”Apply” and ”Save” your settings.

5 Run Job
Click “Build Now”.

6 Check Result
a) Click “Job Link” -> “Console Output” to see the “Console Output”.
b) According to the above graph, the report is gotten at the path of “C:\Vivi_AT\AT
SourceCode\BPT\ECS-1711a_Server Configuration_Check Password_Commercial\Report”,
you can check the detail report by using “Run Results Viewer”
c) You can also download the detail your local env.