Stress testing with simulated browser behaviour

Question

I tried JMeter and it's great but fails in what I need.

Basically I'm testing an ASP script that returns frameset to the client. When frameset renders it calls a couple of other asp scripts which render in separate frames. When I test this with JMeter I only get results for the output of the main script that renders first. JMeter is not behaving as browser would and is not trying to render the html that it receives, and therefore not requesting separate asp scripts and doesn't render them.

The application I'm trying to test is "Aquaforest Tiff server". And I need to know how much time it needs to load tiffserver, along with tiff images from the storage under large number of concurrent connections. Is there a way to actually simulate browser behavior and to render the script that is returned as a response and measure response times all together from start to end???

PS. If I was not clear enough, please tell me... I'll try to elaborate more if you don't understand what I'm talking about here...

Answer 1

I found the 'Retrieve All Embeded Resources from HTML Files' option under HTTP Request and it does download resources that are more deeply nested...

But I don't think this solves my problem, because I have some resources that are downloaded with use of javascript. And I don't see them downloaded in the Results Tree. Am I right?

Answer 2

Visual Studio Test Edition should do the trick for you. A Visual Studio web test recording will record that the page requested the sub pages as dependant http requests.

However, you can still simulate the load correctly, you just have to instruct JMeter to do the http requests for the dependant requests. To record the complete array of http requests made, try using fiddler2 to record. Fiddler2 also works to record visual studio web tests.

Answer 3

Try Selenium or Google WebDriver. You can write unit tests to remote control Firefox and IE. We're doing that for integration tests and it works fine. Occasionally, i pimp one of the integration tests to run multi-threaded in loops for benchmarking.