After you start the application you will first see the window below.

Press the Start Recording button which will open the recording window.

In this window the application will try to autodedect your computer settings and will choose by default the default proxy port 10123 which you can change if you want to. If the program didn't detected your IP address propperly you can change it.

After you have finished configuring the IP address and the port number push the "Start Recording" button. When you push the button the internal proxy server will be started. In order to actually record your browsing actions you have to start your browser and set the proxy setting with the IP address and port configured above. If you don't know how to set the proxy settings there are a few hints for IE here, for Firefox here and for for Opera here. After you have set the proxy settings in your browser you can start browsing and the proxy will record the request that your browser makes. If you receive a message like this Could not connect to proxy server. Access denied than the proxy might not be running try pushing "Start Recording" again and reopen the page or the proxy configuration from your web browser doesn't match the recorder proxy configuration, please check them to see if they match. When you browse your first page you should see something like this in the recorder.

After you have finished recording your actions push the stop button and close the window and don't forget to put your old setting in your web browser proxy setting because when you stop the recorder the proxy will be shut down and you will not be able to see any web page.

After you have closed the recording window you'll be back here.

You can save the recorded data for later use in XML format. If you don't want to get into the code that will be used, you can run the test directly by pressing Run Tests because anyway you will see the code later or you can modify the recorded requests by pressing View/Modify Recorded Data and run the tests after. The application will open the tests runner.

Here you can view the details of each request modify them, add new requests or modify existing requests.

Here you can set the number of concurrent threads that will replay what you have recorded in the Number of Threads field. If you put there a number like 5 the application will behave like there were 5 browsers.

Pause between requests represents the number of miliseconds that the application will wait between requests(in a real enviroment there will probably be at least 1 second delay between requests or more).

In the Time Line fields you will set how long the test will run.

1. Number of Steps - the number of times the program will play all your recorded requests
2. Hour and minutes - the time in hours and minutes after which the player will stop
3. Number of seconds - the time in seconds after which the player will stop

To start running the tests you have to click Start. If you run the tests for the first time it will open a window with the C# program generated for running your tests.

If you don't want to get into details just push Compile Code & Close. This will Compile the C# code into a temporary assembly and will start running the tests.

After a first run you should see some results like this.

You can save all the results from the grid into an XML file if you click on "Save XML Log File".

You can view each request html recorded content by selecting the request and than click on "View page".

You can export all the recorded content into html files by clicking the "Export Responses to HTML Files".

(new) You can export the data through a xsl file by clicking on "Export Data".
This will search all the XSL files in the ResultReportsTemplates folder and will show them in the drop down list so that you can use them to export the data. There is a simple export format right now and as time goes we will add some more.

Well not much :).

The html content is there just to help you prepare the test script/program. So you will have to check each page and see that all your user actions that you have recorded in the prowser are happening propperly here too. There are a lot of scenarios where due to the way the web application was done load testing it will require a little tinkering with the C# code (ex the developers have put a functionality for protecting against robots)

After you have a woking test script/program you will have to decide on the Pause between requests and start load testing the web application for a specific amount of time lets lay 10 minutes with 1 thread. After those ten minutes you check the results and if everything is ok you should increase the number of threads to 5 and after that to 10 threads, 15 ... and so on until the web application that you are testing stops responding propperly. You can also check the CPU and memory consumption on the web server, if the CPU stays constant at 100%(or a lower value for real servers) during the test you should proably stop because you probably reached your web application+Web server limit.

When you find the number of threads for which the web application doesn't work propperly it means that the number of users that web application will support = Number of Threads