Appropriate Approach For Testing

Determining the appropriate approach for testing applications is very important. As it has been mentioned above, there are three different ways to go about performance testing of web-based systems, some of them more difficult than others. Usually the approach of performance testing we will use depends on client requirements or what type of results client wants. In this case, the client wants to measure and test a web-based system to estimate how many users the system can handle simultaneously, when the response time is acceptable. The goal is to simulate real-world usage to find out whether the web-based system can maintain the requested number of users with acceptable response times. As load testing is used to measure how much capacity web system can handle, as maintaining adequate response time. A load test of the entire baseline of software is one of the more involved tests and will require a lot of different scripts to be run at the same time (Kumar, 2001). The load generators will be sending and receiving requests at very high rates. They will also be reporting on the most important performance measurement in Web systems, end user response times. On the other hand, stress testing, however, seeks to determine the behaviour of the system once it reaches load limits, when the server can no longer cope with the load. Load and capacity testing are relatively similar as far as execution is concerned, and hence they are frequently mixed up. It is important to stress, that contrary to a stress test, a load test does not push the system beyond its breaking point.  Because load testing is comprehensive, I think it is most appropriate technique to precisely measure and test performance of a web-based system before going online.

September 28, 2007 | Filed Under Testing/Quality Assurance 

Comments

Got something to say?

You must be logged in to post a comment.

<