HP Application Automation Tools

Skip to end of metadata
Go to start of metadata

Plugin Information

Plugin ID hp-application-automation-tools-plugin Changes In Latest Release
Since Latest Release
Latest Release
Latest Release Date
Required Core
Dependencies
3.0.5
Mar 23, 2014
1.509.4
Source Code
Issue Tracking
Maintainer(s)
GitHub
Open Issues
Effi Bar-Shean (id: n/a)
Avishai Moshka (id: mrmann)
Oren Schwartz (id: orens)
Daniel Petisme (id: n/a)
Romain Seguy (id: n/a)
Ofir Shaked (id: ofirshaked)
Amit Bezalel (id: amitb)
Daniel Schreiber (id: n/a)
Liron Tzabari (id: liron_tzabari)
Usage Installations 2013-Apr 125
2013-May 157
2013-Jun 178
2013-Jul 195
2013-Aug 209
2013-Sep 245
2013-Oct 250
2013-Nov 271
2013-Dec 263
2014-Jan 335
2014-Feb 351
2014-Mar 388

This plugin 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.

This plugin is open source. If you identify any issues or want to submit enhancement requests, please use JIRA. The component for this plugin is the ALM component. Your feedback and involvement will allow us to stabilize and enhance the capabilities of the plugin.

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 and 12.00
 * HP Performance Center 12.00
 * 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

If you are working with Quality Center 10.00 or earlier, and QuickTest Professional 9.x or 10.x, use the Quality Center Plugin.

User Guide

You can run client side-or server-side (Default or Functional) test sets and build verification suites from Application Lifecycle Management (ALM) or functional tests from the file system.

Prerequisites

  1. Java version 6 or higher. To verify your Java version, go to http://www.java.com/en/download/installed.jsp.
  2. ALM/Quality Center client installed the machine that will run the tests. To check if you have a client installed, follow the instructions on this page:   http://<your_server>:8080/qcbin/TDConnectivity_index.html

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:
    Root\testfolder1\testset_a
    Root\testfolder1\testset_b
    Root\testlab_folder
    


  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.

Running Server Side tests using HP ALM Lab Management

If you have Lab Management activated in ALM, you can run server-side tests from functional test sets and build verification suites. After setting up the test sets and build verification suites, you can configure a Jenkins build step to execute your tests.

 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 using HP ALM Lab Management.
  7. Select one of the ALM servers that you configured in the previous step.
  8. Enter the server credentials, project and domain. 
  9. Select a Run Type from the drop down menu (functional test set or build verification suite).
  10. Enter the ID of your run entity (either the test set ID or the build verification suite ID).
  11. Optional: Enter a description of the build step.
  12. Enter a duration (in minutes) for the timeslot. The minimum time is 30 minutes.
  13. Optional: If you have defined an AUT environment configuration in ALM, you can enter the ID here in order to execute your timeslot with specific AUT parameters.
    If you have CDA configured in ALM and want to implement it for this timeslot, select the Use CDA for provisioning and deployment checkbox and enter your CDA details.

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.

Running Functional Tests or LoadRunner Scenarios from the File System

 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 file system.
  7. For LoadRunner scenario tests, click the LoadRunner-Specific Settings button and specify the following settings:
    1. Controller Polling Interval. The interval in seconds by which to poll the Controller for the scenario status. The default is 30 seconds.
    2. Scenario Execution Timeout. The total time in minutes to allot for the execution of all listed scenarios. After this time, the Controller process will be terminated. The default is 10 minutes.
    3. Ignore Errors Containing. During the run, ignore errors contain one of the following strings. For example: Error: CPU usage for this load generator has exceeded 80%. Enter each string on a separate line.
  8. In the Tests box, enter a test with its full absolute path, or a folder or MTB containing one or more tests or LoadRunner 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.
  9. Optionally, indicate a timeout in seconds after which the job will fail in the Timeout box. 
  10. 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.
  2. 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

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 Build Artifacts link to view the results zip files.
  3. Extract the zip file.

For functional tests:
In functional tests, the extracted zip file contains the result files, viewable in the Run Results Viewer. To view the results:

  1. Open the Run Results Viewer and select File > Open.
  2. In the Open dialog box, select Results XML file and navigate to the Results.xml file in the folder that you extracted.
  3. Click Open and view the results.

For LoadRunner tests:
In LoadRunner scenario tests, the extracted zip file contains the following:

  • LRR folder – The Controller raw result folder, viewable in LoadRunner Analysis.
  • LRA folder – The Analysis session folder, viewable in LoadRunner Analysis.
  • HTML folder - HTML reports in two subfolders, IE and Netscape, in their respective formats.
  • SLA.xml – An XML report showing the status of the SLA in the test.

Note for LoadRunner tests: The pass and fail criteria for LoadRunner scenario tests are based on the LoadRunner Service Level Agreement (SLA). If you do not define an SLA, the scenario will fail. For details, see the HP LoadRunner User Guide.

Running Performance Tests using HP Performance Center

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 using HP Performance Center.
  7. Optional: Enter a description of the build step.
  8. Enter a PC Server (Hostname or IP address)
  9. Enter the server credentials, project and domain.
  10. Enter the Test ID and the Test Instance ID. To get the IDs, go to PC Web UI (MyPC) > Test Lab perspective > Performance Test Set table.
  11. Choose a post run action (Collate Results/Collate and Analyze/Do Not Collate)
  12. Enter a duration for the Ad-Hoc timeslot. The minimum time is 30 minutes.
  13. Choose whether to use VUDs licenses.
  14. Choose whether to consider the run SLA status for determining the build-step status. Unless this option set, the build-step will be labeled as Passed as long as no failures occurred.

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.
  2. Select a report archive mode.

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 PC run information.
  3. When the Collate and Analyze option is set as the post run action, the Performance Center HTML report can be viewed and downloaded directly from Jenkins via the Build Artifacts or Test Result options.

Tips and Troubleshooting

Stopping Tests

If your job includes UFT, QTP, or Service Test tests running on a remote ALM/QC machine (run mode = run remotely), you should manually stop the test execution.

Slaves and Testing Tools Installation

For best performance, it is recommended to install the testing tools and ALM/QC on slave machines, and not directly on the Jenkins server.  For instructions on configuring slave machines, see
https://wiki.jenkins-ci.org/display/JENKINS/Step+by+step+guide+to+set+up+master+and+slave+machines.

On the Jenkins slave machine, make sure the the Jenkins Slave service is not logged in with the Local System account. To function properly, it should log in with an account the has administrator privileges.

Labels

Edit
plugin-hp-application-automation-tools plugin-hp-application-automation-tools Delete
plugin-misc plugin-misc Delete
plugin-scm plugin-scm Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Add Comment