Don't get cheated! If you really need a test tool, then do not use the ridiculous implementation, rather take a look at this message , where Daniel Turini points to a lot of better free tools.
This article will stay here though, untill a better implementation is posted, don't expect me to assemble it though :-)
This is a stress tester developed for testing a webshop, it will work its way through a list of URLs, and send a request. Optionally it will test the response for a string value. The app was developed for speed, in development hours as well as performance, so it lacks a lot in user friendliness, but, hey, who wants to befriend users anyway.
Here is how to set up the list, it is important to avoid empty lines:
# The name of the server
# Number of repetitions of the whole sequence
# The following should be a list of pairs of an URL and
# a string to find in the response.
# An URL
# Something to find in the response
# An URL 2
# Something to find in the response 2
When running it will put some log info into this file: C:\\webtestlog.txt, so you better have a C drive. As I said, this is a very primitive tool, so besides some readable log text, there is also some binary values thrown in, so don't get scared if you see sometnig weird in the start of the file.
Here is what the, readable part, of the log looks like:
Num Requests = 242
Ms. Pr. Request = 21141
Num error requests = 0
Num error responses = 0
First there is the number of requests performed, next is the average millisecs used per request. The next value is the number of requests that failed, and after that follows the number of responses that didn't contain the wanted response string.
The sourcecode in plain C is added, so any changes to the app is possible, if you do it yourself.