what you do is exactly what would be done by <config easyajax="10".../>. The problem currently is that it works currently for XHR and setTimeout but not when setInterval is used. In this case, you end waiting the maximal delay all the time. I know how I want to improve it but never found enough free time for it ;-(
Cheers, Marc. -- Blog: http://mguillem.wordpress.com Shawn Bradley wrote: > Hi, > > > > My application has many javascript/Ajax functions that I am endeavoring > to test with Webtest. Since most of these don’t execute immediately, I > have been littering my tests with statements such as > > > > step.context.currentResponse.enclosingWindow.threadManager.joinAll(10000); > > > > to ensure that testing proceeds AFTER the javascript has completed. > However, I find I must specify a large enough value to guarantee that > the javascript has completed, otherwise I get false failures. So, I > specify a value like 10000 – but the problem is that all of these really > add up, since it appears that execution is halted for 10000, regardless > of how long the javascript actually executes. Am I going about this the > wrong way? Is there a better way to guarantee that javascript code is > fully executed before the next webtest step is executed? > > > > Thanks, > > > > Shawn Bradley > > President, Sunergeo Systems, Inc. > > www.sunergeosystems.com > > > > > _______________________________________________ WebTest mailing list [email protected] http://lists.canoo.com/mailman/listinfo/webtest
