In this article we will see how HP LR 11 AJAX Protocol helps us to save effort and time in Performance Testing. Performance Testing helps measure stability, speed and scalability of software applications in different scenarios. During the Test Scripting Phase of Performance Testing, the most time consuming effort is enhancements. The most critical step during enhancements is Correlations.
Correlations is nothing but capturing dynamic data, storing the value in a variable and passing the value to the server. HP recently released its latest LoadRunner version 11.0. This is a significant upgrade from HP, when compared to the previous version which was the LR 9.52, with many enhanced features and new protocols.
Before using HP LR 11.0 to script AJAX based applications, we use Web HTTP/HTML protocol, Web Click and Script or AJAX Click and Script for scripting. The Web HTTP/HTML protocol requires a lot of effort in correlations when compared with AJAX Click and Script Protocol. The Web Click and Script Protocol records the actions based on screen coordinates which requires more maintenance & rework effort, also it is not reliable. Correlations are not required in scripting with the AJAX TruClient Protocol.
Once recording of a business flow gets complete, the embedded script engine creates parameters, add control loops, create transactions, add comments and functions, automate suggestions of automated steps and change the level of object identification, etc.
I conducted some experiments to compare the average time taken in scripting with Web HTTP/HTML Protocol and with the new AJAX TruClient Protocol in LR 11.0. I considered different business scenarios with varying levels of complexity and mapped them to various enhancement factors.
Table 1 displays the average time of scripting in Web (HTTP/HTML) Protocol.
Average Time taken in Scripting with Web HTTP/HTML Protocol
|Business Complexity||Transactions||Data Parameterization||Rendezvous Points||Correlations||Error Handling||Total|
* Time is in minutes
Table 2 displays the average time of scripting using AJAX TruClient Protocol in LR11.0
Average Time taken in Scripting with AJAX TruClient Protocol in LR11.0
|Business Complexity||Transactions||Data Parameterization||Rendezvous Points||Error Handling||Total||Effort Saved Percentage (%)|
* Time is in minutes
I have deducted the time taken in Correlation and calculated the Effort Saving Percentage for each business flow type.
% of Effort Saved by using AJAX TruClient Protocol = (Effort spent on Web (HTTP/HTML) – Effort spent AJAX TruClient) / Effort spent on Web (HTTP/HTML)) * 100
We can see that the average effort saved % in scripting with AJAX Tru Client Protocol in LR 11.0 is 34.97%
Chart 1 is a graphical representation of the total effort spent for scripting using Web (HTTP/HTML) and AJAX TruClient Protocol in the different business flow complexities.
The experiment above demonstrates how the LR11.0 AJAX TruClient Protocol requires less effort as we do not have to correlate in scripting for AJAX based applications.
The only disadvantage of AJAX TruClient Protocol is that your application under test should be compatible with Mozilla Firefox.
- Measuring Client-side performance using Performance APIs - September 19, 2017
- Unboxing HPE LoadRunner 12.55 - August 20, 2017
- Measure Client-side Performance using Lighthouse - August 10, 2017
- Perf Calculator – free iOS app for performance testers - July 16, 2017
- How to performance test AngularJS or ReactJS applications? - June 25, 2017