This Blog Post and the related YouTube Video describes how to integrate a simple Java API (JAR file) into LoadRunner (VuGen script). This post explores selecting the JDK version, sample API, Setup VuGen, Create the VuGen Script and running the script. All of the source code can be downloaded from my GitHub account.
A guide for setting website response times
I have come to the start of the second week of the major HR system upgrade engagement. While working with the customer we identified conflicting performance requirements. We are now working on decoding the response time requirement.
The documented non-functional requirement for response time is:
“The application response times will be equal or better than the existing application”Read More »
Conflicting non-functional requirements
I have just started a new Performance Test engagement on a major upgrade to an HR system and as with 90% of my engagements the non-functional application requirements are contradictory. An example is these requirements:
- The system must support 5,000 concurrent users
- The system must support 1-page requests per second
How to monitor AIX CPU with HP Sitescope \ Loadrunner
How you can monitor AIX LPAR CPU with HP Sitescope for use with HP Loadrunner?
IBM AIX (Advanced Interactive eXecutive) is a series of proprietary Unix operating systems. AIX supports a wide variety of hardware platforms. AIX is used is several industries and in my experience with performance testing can be difficult to monitor CPU utilisation due to how AIX shares hardware resources across LPARS and how monitoring application are setup to gather this data. LPARS are the roughly equivalent to Virtual Machine just on much larger hardware in some cases.Read More »
HPE Truclient and how to correlate dynamic data from the HTML Code via web_reg_save_param Function.
What is TruClient
The first few blog entries I will produce is around HPE Load Runner not quite so new, Ajax Web 2.0 HTML protocol, HPE Truclient.
This protocol promises to remove all correlation requirements for load testing. The protocol scripting interface is within a web browser. Users/Testers can see the results within the same web browser window used to develop the script, in real time as the script executes.
You must be logged in to post a comment.