hmm, I don't think that this is the right answer. <enableJavaScript../> allows you to enable/disable JavaScript, just as you can do it in your "normal" browser.
If you want to ignore JavaScript errors, ie to continue processing just like what a "normal" browser does, you can do following: <config...> <option name="ThrowExceptionOnScriptError" value="false"/> </config> On one side, I'd like to add a "first level" config option for this but on the other side, scripts should help to find *all* kinds of errors, including JavaScript errors and errors due HtmlUnit should be reported to be fixed. On the other side, I understand cases like Daniel's one where the JS error is caused by some external JS code (for instance add code). Perhaps the solution would be to have the possibility to ignore JS errors on foreign code but not the one of JS code that really belongs to the application. What do you think? Cheers, Marc. -- Web: http://www.efficient-webtesting.com Blog: http://mguillem.wordpress.com Ron C Carman wrote: > Daniel Gibby wrote: >> Is there a way to change settings on how strict WebTest or maybe it is > HtmlUnit handles javascript errors? > > The only solution I know of is to turn off Javascript checking entirely > via the enableJavaScript task: > > <enableJavaScript description="Disable javascript to avoid bugs" > enable="false"/> > > The semantics of this task are pretty awful, btw. This could've been > implemented more simply as: > > <disableJavaScript description="Disable javascript to avoid > bugs"/> > > _______________________________________________ > WebTest mailing list > WebTest@lists.canoo.com > http://lists.canoo.com/mailman/listinfo/webtest > _______________________________________________ WebTest mailing list WebTest@lists.canoo.com http://lists.canoo.com/mailman/listinfo/webtest
