QA Revolution

DevOps: Jenkins and UFT Integration

If you are thinking about creating smoke tests and incorporating those into your DevOps process that is a great idea.  We have recently tied Jenkins to UFT and are now able to run smoke tests through the Jenkins HP Application Automation plugin.  Incorporating automated smoke tests into your DevOps process helps to ensure that the applications are stable before testing begins.  Automating the smoke tests will ensure quick validation and help gain additional test coverage during this activity.

This plugin currently supports:
HP Unified Functional Testing 11.5x and 12.0x (QuickTest Professional and Service Test 11.50 capabilities)
HP Service Test 11.20 and 11.50
HP LoadRunner 11.52 and 12.0x
HP Performance Center 12.xx
HP QuickTest Professional 11.00
HP Application Lifecycle Management 11.00, 11.52, and 12.xx
HP ALM Lab Management 11.50, 11.52, and 12.xx
HP Quality Center 10.00, with the QuickTest Professional Add-in for triggering test sets

Configure the connection to your ALM server

  1. Go to the Jenkins Server home page
  2. Click the Manage Jenkins link in the left pane.
  3. In the Manage Jenkins Page click Configure System.
  4. In the Configuration tab, scroll down to the Application Lifecycle Management section.
  5. Click Add ALM server, if no server is currently configured.
  6. Specify a meaningful server name and URL. When specifying an ALM Server URL, use the full string: http:/myserver.mydomain:8080/qcbin

Running Tests Sets from ALM

Set up a job

  1. Go to the Jenkins Server home page.
  2. Click the New Job link or select an existing job.
  3. Enter a Job name (for a new job).
  4. Select Build a free-style software project and click OK.
  5. In the Project Configuration section scroll down to the Build section.
  6. Expand the Add build step drop-down and select Execute HP tests from HP ALM.
  7. Select one of the ALM servers that you configured in the previous step.
  8. Enter the server credentials, project and domain. Note: If you are using the ALM scheduler, it will run under the Jenkins agent user. For example, if Jenkins is running as a System user, the scheduler will run the tests as a System user. This will not affect test execution.
  9. Add the test set folders or specific test sets that you want to include, using the ALM path. To add multiple entries, click the down arrow on the right of the field and enter each item on a separate line. For example:
  10. Optionally, indicate a timeout in seconds after which the job will fail.
  11. Click Advanced to indicate a Run mode (local, remote, or planned host) If you specify a remote host mode, specify a host name. This must be a machine with a valid installation of the testing tool.
  12. Click Apply to save your changes and continue with more build steps. Click Save when you are finished adding build steps.

Set up the Post Build actions

  1. In the Post-build Actions section, expand the Add post-build action drop-down and select Publish HP test result.

Run the job

  1. Run or schedule the job as you would with any standard Jenkins job.

Review the results

  1. From the dashboard, click on the job.
  2. Click the Console link to view the ALM information.
  3. Copy the ALM link to your Internet Explorer browser and view the Test Set results from within ALM.

Hopefully this will help you with your DevOps processes and make your job much easier!

If you would like more information on Agile, DevOps or Software Testing, please visit my Software Testing Blog or my Software Testing YouTube Channel.

Ron Wilson