Skip to main content

Performance Testing


                                
As I have shared before about testing experience here. Today I am pen downing my experience regarding performance testing.
Here I am not going explain about advantage or anything about automation over manual. I start with basic knowledge of performance which I have grabbed till now in my words. Please feel to free to express about any point.

Performance testing: A type of testing which has different outlook for an application. I believe that performance testing is not performed for finding bugs or defects in application.

Performance testing is a type of testing which determine performance of application in terms of its component for particular condition or time or stage.
There are various industry based benchmarks which need to be follow by each of application.

Performance testing helps us to established benchmark of our application basis on industry standard.

When I am saying benchmark, it does not represent customer exact requirements. Customer requirement always lead us to functionality of application but benchmark is something when we say this application with so and so functionality can behave in stable manner in which kind of environment.
When we say minimum requirements for an application means we are providing a benchmark for our application with which it will behave stable and reliable.
So now I can define performance testing as a type of testing to establish various benchmarks to become certain that how components are behaving under specific situation and same time we can also determine that resources usage in terms minimum , maximum or avg , network usage and other factors which can impact our application performance. Such as , memory used by various process called by application, network connection, network bandwidth used any application, amount of time for fetching the data over networks from various tier of application like database server, index server, content server .

There are various types of performance which help us to determine performance of an application. These types are defined on basis of approach of performance testing:

1.       Load testing: Load testing is very important perspective in performance testing. If I say that for achieving primary goal of performance always require.  Load testing is a type of performance testing which is performed to determine exact load your application can sustain successfully and explore various non-functional defects of application like memory leak, network outage and also at same time load testing can determine upper limit of resources used by application.  So in other words, Load testing is performance testing technique to determine behavior of application under various loads and mainly focused on response time of application. Also known as capacity testing.

2.     Stress Testing: It is also very important aspect of performance testing. Stress testing is performance testing technique to determine breaking point of application in terms of load. It is extension of load testing. After load testing we perform stress testing to find out the breaking point of our application. Stress testing mainly focused on throughput ( amount of data exchanged between client and server)


3.     Longevity testing/Endurance test: A similar type of load testing. It is a load testing executed for more longer duration (more than 8 hrs I suggest) to determine memory utilization

4.     Volume testing: Volume testing is a type of performance testing to behavior when under peak load time user performs complex functionality of application. E.g. performing other tasks on irctc in talkal timings J

5.      Spike Testing: Spike testing is performance testing technique to determine how application will behave under significant change in load at time like low load to high then  low in sudden manner.it help us to determine that our application can handle load in spike manner and how it will response.


6.     Availability Testing: Availability testing is another type of testing which help us to determine down time possibilities of our application. By performing this performance testing we can determine that 24x7 our application will be available under what conditions

7.     Scalability Testing: Scalability Testing is a performance testing technique which helps us to forecast scalability of our application for future in case of what if users increase. this testing help use to determine that what kind of and how many additional resources can help us to scale up our application

PS: I will explain major performance testing types and their difference in next post J

è How to determine which application can become under performance testing:

Any application which has at least two tiers architecture can be tested using performance.
So why do we need at least two tier application. If you consider observations in performance testing, you will find what we record actually when we plan performance testing.
Basically, Performance tool always record request (sent by user/client) and response received from server. Other inputs from user also get recorded and some time in specific settings mouse/keyboard activities but not always. So, to perform performance testing, we ideally required an application which has at least two tier communications.

è How to determine which tool can use for performance testing:

Now, we have an application then second step is to choose performance testing tool.
There are various tools are available in market which help us to perform performance testing.

è For choosing the suitable tool, we need to understand our application communication process with client and other tier of application. Knowing the way communication will let us know about protocol used in application at various level.

è Other import factor will be , on which technologies application has developed

è On which platform our application is compatible and same time required platform for tool too

è Above  factors will tell us compatibility of performance tool with our application

è Now other factors which we should consider for choosing the tool will , our performance testing goals like for how many users (possible highest number), size of project (cost wise of course because each tool has their costing along with it)


Above mentioned factors can lead us to choose suitable tool for performance testing.

Hope this post will be given a basic idea about the performance testing.  I will try to share more on concept basis and tool specific pointers too.


                             



Happy Exploring!!!


image source: google

Comments

Post a Comment

Popular posts from this blog

Pacing Calculation in Load runner

                                        Today i will share my understanding on “Pacing”. Usually people take pacing as think time only. I will try to explain both terms first Think time and Pacing, both are a kind of “wait” or “delay” in terms of time but still both differ from each other. Think time: Think Time is the time or delay which user can take between two actions For example, User opens a URL by pressing “Enter” and login page appears but to enter user name or password user is taking some time like copying from other place or remembering it or something like that. This wait or delay we can term as think time in load runner. Think time can be inserted by user in script or captured by tool itself Whereas, Pacing is the delay between two iterations of test. We can give pacing time by using “Runtime Settings” of load runner tool. We can calculate Pacing/Think...

MI Listener in LoadRunner

In a regular LoadRunner load test scenario (not over a firewall), The Controller has direct access to the LoadRunner agents running on remote machines. This enables the Controller to connect directly to those machines. When running Vusers or monitoring applications over a firewall, this direct connection is blocked by the firewall. The connection cannot be established by the Controller, because it does not have permissions to open the firewall. LoadRunner solves this problem by using a communication configuration based on HTTPS or secured TCP/IP. This configuration uses the standard SSL port on the firewall (port 443). The MI Listener is a component that serves as router between the Controller and the LoadRunner agent. When the LoadRunner agent connects to the MI Listener, the MI Listener keeps a listing of the connection to the agent using a symbolic name that the agent passed to it. When the Controller connects to the MI Listener, it communicates to the MI Li...

Configuring Vuser, Controller and Load Agent using MI Listener

          Configuring Vuser, Controller and Load Agent using MI Listener To Configure Vuser, Controller and Load Agent using MI Listener , make sure MI listener is running Running Vusers over a firewall : To set up your system to run Vusers over a firewall Ø   On each load generator machine that will be running over a firewall, configure the LoadRunner agent to communicate with the MI Listener. Ø   Configure the Controller machine to recognize the load generator and MI Listener machines. Configuring LoadRunner Agents over the Firewall Ø   Stop the LoadRunner agent by right-clicking its icon in the system tray and selecting Close. Ø   Run Agent Configuration from Start > Programs > LoadRunner > Advanced Settings, or run \launch_service\bin\AgentConfig.exe. Ø   Select the Enable Firewall Agent check box, and then click Settings. Ø   The Agent Configuration dialog box opens. Ø ...

Mobile Web(Http/HTML) Protocol IN Loadrunner

Today i will share my learning on performance testing performed on mobile application. We can use Load runner tool for mobile based applications. HP LoadRunner 11.50 has two new protocols for helping to record mobile applications: ·          Mobile Application – HTTP/HTML : recording scripts at the transport level for both browser-based mobile applications and native mobile applications, that communicate with their servers over HTTP ·          Mobile TruClient: recording scripts for browser-based mobile applications through the browser-based user interface.  This protocol is based on Ajax TruClient, using a browser modified to emulate the mobile browser. These protocols are independent of mobile operating systems, so will work on different versions of iOS, Android, Windows Mobile, WebOs (Palm), Blackberry, etc. Let’s see the picture behind the scene: We can run the p...

Performance Testing of Documentum

Before starting details of how to do performance testing on Documentum I will try share a basic of Documentum so you can get an idea why we need a different approach while doing performance testing on it. What is Documentum? Documentum is content management software that provides management of document content and attributes. Documentum product is a three-tier, client-server system built on top of a relational database. Documentum components comprise the following: ·          Content Server - Manage access to the metadata stored in the relational database and the  Content files, usually stored in the file system ·          Webtop/Wdk Server - J2EE-based web application framework Behavior behind the scene: An applet is invoked at the client side when a file within the docbase is accessed and while files are imported into a docbase. Applet/UCF client being client side Java applic...

Run Vugen script using command prompt

We can also run or replay our Vugen script using Dos Command Prompt (CMD) " LoadRunner install dir" \bin\mmdrv.exe -usr "path to .usr file" Note: LoadRunner install dir: Path of directory where Loadrunner has installed Hope this will help you guys. Happy Exploring!!!!

CITRIX Error in Load runner: Failed to get window size, wrong format.

Citrix based Applications are now days very popular. We can perform load testing on Citrix based application using load runner tool also. Quick tips for Citrix applications: 1. You can use "HTTP" and "Citirix" protocol together in load runner. 2. Try to keep windows in full screen mode. Some time while replaying the recorded script can give some error too. one of the error i have encountered was: Error: Failed to get window size, wrong format. Unable to detect client version. Warning: Extension CitrixClientImpl.dll reports error -1 on call to function ExtPerThreadInitialize Error: Vuser failed to initialize extension CitrixClientImpl.dll Resolve the issue: 1. Save the script after recording. 2. Go to Script directory and look for "default.cfg” file 3. Open the file into edit mode 4. Add below mentioned code in file and save it [CITRIX] DesktopColors=32 Colors=True Color (24 bit) Enctyption=128 Bit Window=1024 x 768 ...

Heap Dump : how to generate heap dump

Heap dump is important when it’s come to performance testing. Let’s start with what is heap in an application. Heap: Heap is dynamically collective amount of data /memory in partially binary sorted tree structure. But we need to loop up on heap in term of memory. Heap is part of memory where memory for objects assigned dynamically. Heap dump : Heap Dump is snapshot of memory at certain point which contains below mentioned information: -information of java objects -information of java classes or we can define as A heap dump is a textual or binary representation of the Java heap which is usually written to a file.   Heap dump is always helpful to analyze memory leak or high usage of memory of java application. There are various tools which help us to generate the heap dump. We can also generate heap dump without using tools. What we require is JVM (Java Virtual Machine)on system. There are various vendors for JVM but let’s concentrate on Sun JVM. ...

Software being installed: Cucumber Eclipse Feature 0.0.23.201811220126 Missing requirement: Cucumber Editor 0.0.23.201811220126

Error:    cucumber.eclipse.feature.feature.group 0.0.23.201811220126 While installing cucumber plugin for eclipse, sometimes we faced below mentioned error Error : Cannot complete the install because one or more required items could not be found.   Software being installed: Cucumber Eclipse Feature 0.0.23.201811220126 (cucumber.eclipse.feature.feature.group 0.0.23.201811220126)   Missing requirement: Cucumber Editor 0.0.23.201811220126 (cucumber.eclipse.editor 0.0.23.201811220126) requires 'osgi.bundle; org.eclipse.pde.ui 3.5.0' but it could not be found   Cannot satisfy dependency:     From: Cucumber Eclipse Feature 0.0.23.201811220126 (cucumber.eclipse.feature.feature.group 0.0.23.201811220126)     To: org.eclipse.equinox.p2.iu; cucumber.eclipse.editor [0.0.23.201811220126,0.0.23.201811220126 ] Solution: Clear your eclipse cache with below steps: Open Eclipse and navigate to the ...

Record scripts on mobile applications in LoadRunner

Record scripts on mobile applications in LoadRunner : As LoadRunner 11 in Patch 3, Mobile App (HTTP/HTML) protocol added which can help us to record scripts of mobile apps. There are three recording options in the recording Wizard: 1.Record and Analyze Traffic - Use mobile sniffer agent to capture traffic and then analyze. This allows Vugen to connect to the mobile agent on the server or localhost and carry out the business process for recording. 2. Analyze Traffic - Analyze traffic using existing capture file to generate script. This allows Vugen to scan a pre-captured network traffic (WinPcap) file and generate the code based on the traffic. 3. Record Emulator - Record script using a mobile device emulator. This allows Vugen to record an emulator installed on the Vugen machine. With this option, you need to verify that you are able to bring up the emulator and navigate to a URL outside of Vugen to make sure the emulator settings are correct.