Performance Testing – Workload Model

In this modern era, we are living in a space where almost everything is found over World Wide Web. Only perquisite you need is to have proper internet connection at home and it feels like you have the whole world in your hands 😛 .If you search for any information over the web, you end up with countless providers who are just few clicks away from you. This growing competition also demands better customer services to get the competitive edge. Main purpose of web applications is to facilitate the users in getting their desired information in a quick and efficient manner.

Thus a web applications performance is the most important parameter to attract and retain maximum users. So now we know that “performance” is the key to any web application, how do we measure an applications performance? how to plan a proper and efficient approach? The answer is “performance testing” with a well planned “Workload Model  is designed  to validate whether they are meeting users expectations or not and also to reduce the identified performance bottlenecks.

What is Workload Model?

Distribution of load across all the identified scenarios of AUT(Application Under Test) is called the Workload. A workload model is designed to identify key test scenarios and load distribution across these scenarios. Performance test results can never be reliable unless its workload model is designed accurately. Identification of key test scenarios and load distribution across these scenarios is one of the major parts of a performance test plan which lies under the workload modeling. In performance workload modeling phase, a complete understanding of AUT is developed for multiple purposes such as to identify its test objectives, to figure out all its users’ types and their activities, to identify application key business scenarios along with their navigation paths and eventually to analyze and evaluate the load distribution across all identified scenarios and their navigation paths.

Continue reading Performance Testing – Workload Model


Introduction to Performance Testing

As you can witness the rapid growth in IT industry, the software application development has become pinnacle of our daily usage. Every year thousands of software’s are being developed and are creating a buzz in the industry. Not all software’s can reach user expectations, they may lack many aspects such interface, look n feel, user friendly and “Performance“. Well performance is surely is an important and crucial aspect which should not be ignored . Performance testing is necessary before marketing any software product. It ensures customer satisfaction & protects investor’s investment against product failure. Costs of performance testing are usually more than made up for with improved customer satisfaction, loyalty and retention.. Lets get familiar with performance testing  and what is the impact of performance testing on a software.

What is Performance Testing ?

Performance Testing is a discipline concerned with detecting and reporting the current behavior of the software system. Performance testing is a technical investigation done to determine or validate the responsiveness, speed, scalability, and/or stability characteristics of the product under test.

Why Performance Testing ?

Performance testing is done to tune an application without any performance glitches such as speed, stability and scalability. Most importantly, performance testing uncovers what needs to be improved before the product goes to live. Without rigorous performance testing, software is likely to suffer from issues such as: running slow while several users use it simultaneously, inconsistencies across different operating systems and poor usability. Performance testing will determine whether or not a software meets industry set standards such as responsive, speed, scalability and stability requirements under expected workloads. Software with improper performance testing will fail to meet the standards which results in a bad reputation and has a direct impact on the sales of the application. So it is recommended that a software should under go rigorous and planned performance testing to avoid performance bottlenecks.

Continue reading Introduction to Performance Testing