Load testing question

Currently we don't have any ability to drill down to the step level. Also the load happens for all steps unconditionally. What's going on is that if you specify 100 virtual users, Test Studio will start 100 separate threads, each representing one user and let each one run through the user profile (i.e. the HTTP traffic for that user scenario) as quickly as possible with appropriate pauses for the think times included in the user profile.

We don't do anything like detect the load during step 6 of the test. Since all the virtual users are running asynchronously each user can be at any random step at any point in time, but you will always have 100 active virtual users trying to interact with your application under test... up until the time runs out for the test.

I hope that helps clear up how our load testing works.

Currently to determine what HTTP errors occurred requires you enable logging and study the log file. There was a minor bug in our 2012 R1 release (version 2012.1.411) where we didn't log all of the HTTP errors. That has been fixed in our latest internal build, 2012.1.426.

I'm not sure I understand your question "or high load happened how can i know in which step". The load presented by Test Studio is going to be constant, or ramped based upon the settings you specify. You have total control on the load presented to your application under test.

Maybe you mean trying to determine during which steps your application was slowing down or speeding up? This is very high on our TODO list. Many of our customers are asking for more details per step. Unfortunately we don't have that information available or easily accessible. In the meantime I suggest you try using our Performance Testing feature to try and get this information (though I admit it will be for only one user).

If you feel like doing your own data mining, we have published the load database SQL schema for anyone to access and generate their own reports. We will be adding to this documentation with more details on what the fields represent and how to use it. We're just not quite there yet.