This post was written by Yafim Kazak, HPE Jenkins plugin owner
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.
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.
For more information on pipelines, see the following links:
Wait for the installation process to finish and then restart the Jenkins master.
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.
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:
Create a New Job / Item (or select an existing one), enter a name, select‘Pipeline’, and click OK.
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.
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”.
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.
To specify LoadRunner-specific advanced settings, click “LoadRunner advanced Settings…”
c. Click “Generate pipeline script”.
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”.
5. Press “Build now” and watch it run!
Now, you can now review the run results in a few different ways:
· Per Project (v5 new feature) – Compare LoadRunner results across builds:
· Per build:
a. In the left pane under ‘Build history’, select the desired build.
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.
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