Automate web app profiling
Woland
Posts: 5
Hi, i'm really impressed with your product but there is one thing that it seem to miss - the automated load script for profiling web applications or a hook to existing processes.
Right now when profiling starts i have to manually click different links in the web browser and then close it to get details. The problem is when i optimized the code it's kinda hard for me to see how the code actually improved as in order to do that i have to do exactly the same (clicks) as i did during initial test, which is sometimes pretty hard thing to do.
Is there anyway to integrate it with for instance Microsoft ACT web stress tool?
Right now when profiling starts i have to manually click different links in the web browser and then close it to get details. The problem is when i optimized the code it's kinda hard for me to see how the code actually improved as in order to do that i have to do exactly the same (clicks) as i did during initial test, which is sometimes pretty hard thing to do.
Is there anyway to integrate it with for instance Microsoft ACT web stress tool?
This discussion has been closed.
Comments
Absolutely! If you choose to profile a web application, then it doesn't matter if the incoming requests are generated by ANTS Profiler's web browser instance or a third-party load testing tool. It would be possible to start an ASP .NET profiling session, then use ACT or ANTS Load to make requests to the web application.
I will try that again.
If the viewstate for the page is not correct, none of the methods on the page will be run because an HTTP/500 error will happen.
Are there any 500 errors in the W3SVC logs when this test was run? I'm not 100% on ACT, so I don't know if it recognizes error pages properly or if it just says 'yup--I sent a request and got a response' even if the response was an error page.
I take that back -- ACT does report errors. I've just had a look at it.
Well, I can't see any reason why it wouldn't trigger results in ANTS Profiler. I'll have a look at this today/tomorrow and get back to you. There must be some sort of gotcha in ACT that is making this (not) happen.
I've done a few tests with ACT and got it to work perfectly. Here's what I did: