Hi Nick, > Unfortunately the system is still in development and not yet publicly > available. > I am using R1704 that includes Htmlunit 2.1.
you should replace HtmlUnit-2.1 with a recent snapshot of HtmlUnit-2.2 from http://build.canoo.com/htmlunit/artifacts/. Perhaps is your problem already solved. > Can give you all the resulting response codes from the dojo modules and > any .js > but not sure if this will be enough for you to understand what might be > happening. would be too difficult if you haven identified where the problem is > It might be better if you can give me some tips on modifying the source > or any config > Options that would allow me to determine cause here. the basic strategy consist to determine where HtmlUnit's JS interpretation starts to differ from the one of the simulated browser. We have some tools in planning for this purpose but nothing currently available. This means that the basic technique is for instance to add some alert('foo') in the js code to see if this reached by your normal browser as well as by HtmlUnit. Btw, perhaps did you say it already, I don't remember but do you have these problems with WebTest simulating IE (the default) or Firefox? >>From a few thousand feet it appears that 'duplicate' function is being > invoked on a class > for which this method is not defined. Either that or a .js file has not > been loaded maybe??? or the method has not been added to the object (or it's prototype) at the right time > I am not sure that we are doing anything untoward in the use of the dojo > framework but my > previous request 'dialog not loading' indicates we are having a few > problems in this area. > > I have a javascript developer now looking at webtest and he has > indicated that a lot of the > web testing type products usually have problems with nested iframes. I > am not sure if that is > the case here but I stand to be corrected. I really don't understand what your colleague means. > I understand your time is valuable but any small push in the right > direction would be fantastic. > > (What I am thinking is some sort of detailed stack trace!) a stack trace wouldn't help, because the problem probably occurred a long time before ;-( Cheers, Marc. -- Blog: http://mguillem.wordpress.com _______________________________________________ WebTest mailing list [email protected] http://lists.canoo.com/mailman/listinfo/webtest
