-
Archives
- April 2019
- January 2019
- June 2018
- January 2018
- July 2017
- April 2017
- December 2016
- August 2016
- February 2016
- September 2015
- April 2015
- February 2015
- September 2014
- February 2014
- January 2014
- December 2013
- November 2013
- July 2013
- June 2013
- March 2013
- February 2013
- January 2013
- October 2012
- March 2012
- February 2012
- January 2012
- December 2011
- November 2011
- September 2011
- July 2011
- May 2011
- April 2011
- March 2011
- February 2011
- September 2010
-
Meta
Monthly Archives: November 2013
How to analyze a load test report? Part 2: Test design problems.
When you start load testing a web site (especially if this is the first load test in your life) you may see a lot of errors in the report. Possibly you will even have to stop the test before it completes, because at some point in time it becomes clear that something goes wrong. If the problem is not so obvious, it is still recommended to check the report for the errors related to each virtual user profile (i.e. to each different type of virtual users) before looking at any performance data.
Usually you do not create a high load in the very first test of a web site, so if you see any errors in the report, most probably they appear because of the test design problems. In other words, the emulation of the real user activity is performed incorrectly. Your web application may produce errors and even refuse connections because it receives incorrect data from your load testing tool. Why this may happen?
Continue reading
Posted in Testing practice, WAPT usage
Tagged error type, HTTP status code, parameterization, test execution log, test report
5 Comments