LoadRunner and Performance Center
Showing results for 
Search instead for 
Do you mean 

Continuous Performance Testing Using Jenkins CI / CD Pipelines with LoadRunner

hilale on ‎01-26-2017 03:48 AM

This post was written by Yafim Kazak, HPE Jenkins plugin owner

yafim.jpg

 The HPE Jenkins plugin enables you to integrate LoadRunner performance testing in your product Jenkins build pipeline. Moreover it will share the results with all the relevant stakeholders from dev to upper management.

This post will guide you in creating your first Pipeline script in Jenkins using our plugin ( https://wiki.jenkins-ci.org/x/sAHqAw ), in addition to our previous guide on how to integrate performance testing in a regular Jenkins build job.

 

What’s a pipeline?

A pipeline is a job type that allows you to seamlessly set up and code your complete application lifecycle with a persistent record of the results and status. This is in contrast to a “freestyle” job, which requires a custom configuration to trigger several concurrent jobs, usually saving the record results and status separately within each job.

1-pipeline.png

 

 

 

For more information on pipelines, see the following links:

https://jenkins.io/doc/pipeline/

https://www.youtube.com/watch?v=ggzbqcf8PAU

 

Follow these steps to integrate performance tests in Jenkins pipeline:

Install the plugin:

If you are using Jenkins v1, the instructions may differ slightly.

Option 1:

  1. From your Jenkins home page, Click the Plugin Manager and go to the Available tab
    (as shown in following screenshot)

  2. Find the ‘HPE Application Automation Tools, select the box, and press “Download now and install after restart”.

  3. Wait for the installation process to finish and then restart the Jenkins master. 

2-jenkins.png

 

 

install_plugin_in_jenkins.gif

  

 Option 2:

  1. Alternatively, you can download the plugin from our official page (https://wiki.jenkins-ci.org/x/sAHqAw) and install it manually by uploading the downloaded file in the “Advanced” tab.

3-plugin info.png

 

  NOTE: Make sure you’ve installed the dependencies of the plugin to run pipeline as listed on our page https://wiki.jenkins-ci.org/x/sAHqAw.  (In Jenkins 2.00 or higher, they are usually installed by default.)

 

Now, let’s set up the pipeline script:

  1. Create a New Job / Item (or select an existing one), enter a name, select‘Pipeline’, and click OK.

  2. Write your pipeline script -

   Specify a working node that has a LoadRunner installation and set the stage (not must). Enter the stage and    node        arguments into the Script area as shown below. 

4-pipeline script.png

 3.  Click “Pipeline Syntax” to allow you to generate a command using the pipeline syntax generator.

 4.   From the Sample Step drop down list, select “loadRunnerTest”.

 5-LRscript.png

a.   Enter the absolute or UNC test path on the node machine.

b.   Select “Always archive and publish HP test reports (LR only)” from the Report archive mode drop down.

6-steps.png

 To specify LoadRunner-specific advanced settings, click “LoadRunner advanced Settings…”

7-advanced.png

  c.   Click “Generate pipeline script”.

8-generate.png

  

  d.   Copy the code to the clipboard.

  e.   Click “Back” to go to the previous screen.

  f.   Go to the Pipeline Script area and paste in the code after the node and stage.

  g.   Click “Save”. 

9-save.png

 

 5.   Press “Build now” and watch it run!

CreatePipelineJob.gif

 

 

Now, you can now review the run results in a few different ways:

·         Per Project (v5 new feature) – Compare LoadRunner results across builds:

10-per project.png

  

·         Per build: 

 a.   In the left pane under ‘Build history’, select the desired build.

11-per build.png

 

 b.    In the left pane, choose the Test Result link. The test results are organized by scenario name, SLA results, and the statistics of each SLA.

12-transaction report.png

 

     c.   Click thePerformance Report link to display the Analysis Summary report pages such as “Running Vusers”, “Hits per Second” and “Throughput within Jenkins“.

 

     d.   From the Transaction Summary link, you can review the transaction summary report

summary.png

Interested in more information about LoadRunner, Performance Center or StormRunner? Visit our activity community in the LoadRunner, Performance Center or StormRunner forums.

You Might Also Like:

To learn more about the Jenkins integration with LoadRunner, please visit the LoadRunner Help Center.

Stay up-to-date with the latest news on Twitter | LinkedIn | Facebook.

 

 

 

 

 

About the Author

hilale

Events
June 6 - 8, 2017
Las Vegas, Nevada
Discover 2017 Las Vegas
Join us for HPE Discover 2017 in Las Vegas. The event will be held at the Venetian | Palazzo from June 6-8, 2017.
Read more
Each Month in 2017
Online
Software Expert Days - 2017
Join us online to talk directly with our Software experts during online Expert Days. Find information here about past, current, and upcoming Expert Da...
Read more
View all