Our legacy site: www.webwob.com   

Continuous Integration (CI) with HP LoadRunner

   legacy pages

This page outlines all the processes that we have had to re-work to get a reliable, secure, CI/CD workflow. We need to check scenario settings for example, make sure test data is managed and watch out for test environment setup, such as DB scaling.

     LoadRunner CI/CD      *_LR_CI_*      LR_CI_+      Email_out      Email_in      Cookies 1      TUTORIAL      sprintf      debug      VUgen      Kill -9      disk space      AWS S3      dig (DNS++)      substitute      curl with timings      LR_Jenkins_graphs     

LoadRunner Scripts and Scenarios

Build scripts

Build scenarios

Store scripts and scenarios in git



Test data

Use a VTS server to store general data

Setup VTS server with ports per project

Define VTS ports per project on wiki

Build data preparation scripts


General Jenkins jobs

Build Jenkins jobs to check scenario details

(Have to manage injectors and edit lrs files accordingly)

Build Jenkins jobs to check analysis settings

Jenkins setup for git pull back to defined folder

(Update controllers with git – so we can pull every time – add to path)


AWS Management

Update LR slaves (LR version, Jenkins setup, Git, VTS)


AWS API bash for up and down boxes to keep costs down

AWS boxes setup for larger soak tests – large C drive



To Do list

CI graphs (Jenkins jmeter plugin)

Build Jenkins Deployment jobs for Atlassian Bamboo projects

Develop pipelines

85, 90 and 95 percentiles run at end of test

Jenkins trend graphs for all those above

DynamoDB scaling up and down with options

HTML reports linked to releases (need to get them working consistently)

Edit scenarios with bash to check/change the base location of scripts

Re-install LoadRunner as Administrator to give full access to the file system and fix the analysis performance issues.


Final Steps

Show controllers when running CI tests. This is for colleagues to be able to carry on with dev work.

DEPLOY to PROD – CD (Continuous Deployment). Bamboo could allow us to do this now.

Run Jenkins on boxes from command line - and trigger from shortcut with 'Run as administrator' set under 'Advanced' (to enable controller front end to be displayed):
    [ java -jar C:\Program Files (x86)\Jenkins\jenkins.war --httpPort=80 ]