1 – Test from the end user’s perspective

The first objective of a successful load test is not to lose focus of the most important metric of the test; The End user’s experience with the application.

Remember that an application server, a network, database, etc. might perform well under heavy load, but your tests are not conclusive if they don’t replicate real world transactions executed the same way the end users will.

2- Set test objectives

Define the test objective for response time and stability. Identify what is acceptable and what is not.

3- Identify test scenarios

Scenarios are sets of actions the end user performs when interacting with the application.

The test should include the scenarios for which you have set performance goals or have significant performance impact. These scenarios should replicate business activities performed by the end user.

Example:

End user Searching for an airline flight, Reserving a seat, then Buying the ticket.

4- Set the load distribution

In the real world, not all the users who searched for a flight will select one and purchase it. So the load distribution will be something like :

At any given time, you may have 70% of end users searching for a flight, 20% reserving a seat, and 10% making a purchase.

From this we can derive the number of virtual users executing each scenario. For 1000 virtual users:

700 will be searching flights of different origins and destinations

200 will perform the reservation process

100 will purchase a ticket

5-  Create test casesThe test cases are the steps to be performed with the application and the expected result for each step. ? They are based on the scenarios and user profiles. Each test case/step will be marked as PASSED or FAILED after the test run. 6- Choose a load tool

The right choice is the tool that will help through each of the identified steps so far.  Depending on the budget and intended use of the tool you might want purchase, lease or use a SaaS type tool. 

Make sure to try before you buy.

 7- Prepare the load environment

Identify the hardware and install the load test software.  Ensure you have the right number of servers and sufficient bandwidth to generate the load.

8-Start with small number of users then increase incrementally

This allows adjusting the wait time to synchronize the execution of the scenarios and will help you find the break points easily.

9- Run the test

Perform multiple runs with different numbers of users to analyze the way the application behaves under different loads.

10- Analyze the results.

Make sure the objectives have been achieved.

Compare the results of each run and determine how the application is behaving under different loads.

 

Bookmark with:

Deli.cio.us    Digg    reddit    Facebook    StumbleUpon    Newsvine

I'm excited to officially bring you the NRG Global blog. It seems that technology keeps evolving at an astonishing pace, particularly when it comes to enterprise applications and IT requirements. We're launching our blog to keep you up to date on the latest happenings – in terms of our products, our company, and the world of app testing in general.

You'll find out about new product announcements, company events, our take on industry news, and even some sneak peaks behind the scenes here at NRG. Our goal is to create a comprehensive digital resource to help you make the most of your NRG Global products with quick tips, product updates, application notes, and more.

Most importantly, we’re looking forward to hearing from you. After all, the best product development always factors in real customer needs and wants. And we want to build an active community of NRG users, who share their insight and experiences. We hope you read, contribute, and keep checking back. Stay tuned for more.

Bookmark with:

Deli.cio.us    Digg    reddit    Facebook    StumbleUpon    Newsvine