Load Runner 12.53

Basically Load Runner 12.53 is a better version of Load Runner 12.5.In Load runner 12.5 many drawbacks are there like:

If we want to fire API call we have to write api function by manually.

In the previous version Load runner is not compatible with Linux.

Browser compatible with Google Chrome,Mozilla Firefox,Internet Explorer.

Jankin's plugin

If we want to test some GIT repository projects so we have to import the project in load runner.

To cover all drawback and some limitations Finally Load Runner 12.53 Released!

Features

Main Focus On this Release

• Git integration in VuGen
• 64-bit replay support in various Java protocols and C Vuser protocol
• New PCoIP (remote access) protocol
• Enhanced SAPUI5 recording in TruClient
• HTTP Video Streaming (HTML5, HLS) support
• HTTP/2 support
• REST step-builder editor in VuGen
• JSON manipulation APIs
• Web - HTTP/HTML and Mobile Application - HTTP/HTML protocol unification
• Linux load generator improvements
• Enhancements to Java-based protocols

Git integration in Vugen: Basically this functionality is used for to test the Git project.now,if we want to test the git project direct import option is available in load runner.before that we have to import the git project by manually.

To import the Git project

Go to Version Control>>Git Options>>Import From Remote Repository

After this option window will display like this:

In this window basically we have 
Remote Repository URL:From which repository we want to import the project.
Repository name:What is the repository name.
Local path:In local system where we want to save the project.

By using these options easily we can import our project.

New PCoIP (remote access) protocol:
This protocol is used for remote display protocol for delivering remote desktop and applications.PC over IP uses the User Data gram Protocol(UDP),an alternative to the Transmission Control Protocol(TCP).PCoIP delivers bitmaps by encoding them on a remote host and then streaming to the client,transmitting only regions of the screen that change from frame to frame.From the client perspective ,it's almost as if the client is watching a movie of the desktop's activities that's being created in a real time. PCoIP can handle multimedia and graphics-heavy applications, but it does increase the CPU load on the remote host.
In Load runner We can use this protocol as a multiple protocols Like:
Flex+PCoIP
Web HTTP/HTML+PCoIP and so on......
Go to File>>New Script and Solution>>Multiple protocols>>Select Flex+PCoIP

Enhanced SAPUI5 recording in Tru Client:Basically this protocol is used for tru client protocol(To test desktop and mobile application).In load runner for this type of protocol we have tru client protocol.

Before that In load runner if we want to test desktop and mobile application through Tru Client protocol,for the mobile application it was not supported.

Now we have a SAPUI5 protocol in tru client protocol so that we can easily test mobile application.

SAPUI5 is a SAP user interface for HTML 5 is a collection of libraries that developers can used to build desktop and mobile application that run in a browser.With SAP's SAPUI5 Java Script toolkit,  developers can build SAP web applications using HTML5 web development standards. 

In the Load Runner Go to File>>New Script and Solution>>Single Protocol>>Tru Client-Mobile Web or Tru Client-Native Mobile or Tru Client-Web

Same protocol is available in "Mobile" and "Popular" protocol.

Difference Between TruClient Protocols:

TruClient-MobileWeb :In this protocol we can test android application accessed by the browser.Like those android application accessed by the browser.

TruClient-Native Mobile:In this protocol we can test android application accessed by the browser and mobile.

The new TruClient – Native Mobile protocol provides a novel way to record and replay native mobile applications on both Android and iOS devices. The protocol enables the developer or Develops engineer to record user interactions on the mobile application and create a TruClient script. This script can be enhanced using standard TruClient functionality including parametrization, transactions and JavaScript coding.

This protocol is meant for end-user performance testing. Together with the existing mobile protocols, it completes the LoadRunner mobile performance testing suite.

 

Load Runner 12.5

First I will talk about Load Runner.

Basically Load runner is a very powerful tool to do performance testing.Load Runner is a record and play tool.
It have 3 main components.
VuGen(Virtual User Generator)
Controller
Analysis

VuGen: VuGen is  mainly used to create scripts for any application module.In VuGen we can customize our scripts based on our requirement.

Mainly in VuGen we will focus on the below:

To handle Session-id(Server Generated Values)and cookies.
To Verify Web pages.
Check for application stability(Test with different users ).
According to the requirement add conditions,loops and API's calls.

To handle Session-id and cookies in VuGen we have a procedure called "Co-Relation".

Now I will discuss how to apply co-relation
In Load Runner when we will record script so in that script some dynamic value will generate from the server side to handle these type of value we have to use Co-relation in load runner.

Basically we have to record same  scripts two times to know that which value is changing every time.
then using the Wdiff(Window difference in two scripts) can easily identified which value is changing.
For now we have to use co-relation function:
Web_reg_save_param(dynamic value,LB,RB,ORD,LAST);

dynamic value:name of the value which value is changing every time.
LB:Left boundary of the value .
RB:Right boundary of the value
ORD:ORD value is depend on the dynamic value (How many time value is coming).

For Ex.name=outboundFlight value=230;378;11/20/2003 checked >
In my script this value is changing every time.

web_reg_save_param("outFlightVal",

"LB=outboundFlight value=", "RB= checked >",ORD=1", LAST);

ORD=1 means value is repeating only once in the script .

To Verify web pages
After recording the script I want to check my script will it is going to the right page or not.
For that we have 2 type of validation.

• Text Check
• Image Check

Text Check:To check the text present in webpage or not.
Web_reg_find("Text=Welcome to the Web Tours site", "Search=Body", LAST);
In this example I wanted to search "Welcome to the Web Tours site"text.by using this function we will easily find the text on the web page.
Image Check:To check the image present in webpage or not.
(web_image_check("web_image_check","src=ic_error.gif","report=success",LAST);
In this example I wanted to search a image called "ic_error.gif" so by giving this name we will able to search easily.
But Some time SRC will be not there in this case use ALT attribute to search.

(web_image_check("web_image_check","alt=image present","report=success",LAST);

Check for application stability(Test with different users )
To check the application stability given more data(user)on the application.To see this in load runner we have a one features called "Parameterization".
Basically parameterization is used for to see the system stability and functionality of the application.

Analysis:
After execution automatically analysis will generated reports and graphs according to execution.Load Runner analysis have different types of graphs and reports.
Mainly we will focus on the basics graphs like:
Hits per second-How much per second time the server is hitting the application.
Average Transaction Response time-What is the time taken by every transaction to complete the request from server side.
Transaction per second-How much time taken by each transaction.
Total transaction per second-How much time taken by total transaction.If a script having 6 module like Login,Enter details,do some operation,make a payment,see the order,logout.
how much time taken by all operation.
Total error per second-How much error is coming in every second of each transaction.

What is Performance Testing?

Performance Testing

Performance  is the key factor for any website,online shopping sites and any tickets booking sites. Mainly,In performance we will check the functionality of the application under Load.

I will take a simple example of IRCTC system.I wanted to book a Tatkal ticket from Bangalore to Mumbai,I have started booking procedure(Entered all entries) .When I reached on the payment page that time its showed me "Server Not Found" or "Server is not able to find DNS".

But for other user payment page is able to visible.that means the performance is not good.

Performance Testing Procedure

Performance Testing Life cycle

Performance testing is a Non-Functional testing,here we check System or application  behavior

Stability of the application.Basically performance testing is a subset of performance engineering is a computer science practice which strives to build performance standards into the implementation,design and architecture of the system.

A Simple Example Of Performance Testing Procedure

Lets,Consider I have a site of "Online Shopping"and I want to do performance testing of this site.

Step I : Identify the scenarios of this site on what basis we will do performance testing,this is called "Project Assessment".

According to my example Project Assessment will be:

• How many users want to login simultaneously.
• What is the Bottleneck(Limitation) of the application at the time of login.
• Is the system is able to handle the load?
• Like this,According to the modules we have to identify all the scenario related to the application.

Step II :How we will start our performance testing?what is the basic milestones to start the performance testing?this is called "Planning The Test".
According to my example Planning the test.
Initially if i am taking 50 VU how much time user will think to do the next operation(Think Time).

Think Time : Think time is the wait time taken by the users.In the real time if we are logging on some site,in the meanwhile i got some other work so that is the wait time  by the user.

What is the "Response time Bottleneck".
For ex. if i am taking 10 ms response time for 50 VU,have started execution of the script execution but now the response time is 19 ms that means performance is not good for the site.

Like this for all the Scenarios or Modules just think on what basis we will start our performance test plan?

Step III :Now the test plan is ready we have to start the plan execution using any tool,Techniques or any real time execution.this is called "Implementation of the test".

According to example test plan is ready so i will start the execution using tool,techniques.

Step IV : Test execution is completed so start the analysis on the basis of bottlenecks.this is called "Analysis Of the Results".

I have completed execution of the application now i will analysis of the result basis on the bottlenecks and limitation.

• Basis on the Response Time 
• Basis on the Server Load
• Basis on the Think Time
• Basis on the Hits Per Second
• Stability of the application

Step V : The final step is after analysis the results if is not matching the requirement and limitation and the customer is not satisfied with the results then "Refine(Re-Identified) the test ".

If the result is not matched with the requirement then we will start the testing procedure from the beginning.until we will get our original result according to the requirement.