Basic Flow of a Performance Test, as I've done them, for those interested:
1) Use The Grinder's TCPProxy to record a series of user stories, making sure to put in comments as you record
2) Trim down the scripts to only issue the necessary commands, delete the sleep times
3) Put in some text handling and error checking into the scripts to make things like searches into variable-based scripts, and custom site error responses (such as login redirects) into Grinder errors
We have run several different load tests for the Acushnet Golf company, primarily to evaluate the performance of their customized order management software. We were able to simulate a load of hundreds of users via Grinder, along with custom tools we developed such as Grinder Webtest.
We did a series of load tests in order to simulate the performance effects of hundreds of users on a complex Adobe Flex stock ticker application. Scenarios were recorded using Grinder, capturing HTTP requests that we later customized to inject unique session identifiers for each user during playback.
Load Testing is the use of multiple "virtual users" to observe how a software application responds under load. Load Testing is most commonly used for applications to verify that the emulation of peak period business processes can handle a specific number of users.
Automation Excellence's engineers have a broad base of experience load testing many types of applications on a variety of delivery platforms:
This custom module for the Grinder load testing framework allows execution of Visual Studio "webtest" files. It supports parameterization, capturing of variables in HTTP responses, and response validation using regular expressions. Test scripts may be logically grouped into test sets, allowing them to share variables and captured values. Test sets can be run sequentially, randomly, in a specific thread, or according to a percentage-based weighting.