Marc, Yes, that is precisely the problem: we often have links to sites that have third party code. Since we have no access to the source, when we get a Javascript error the test fails, but there's really nothing we can do about it since we don't own it.
I see the stuff about haltonerror and haltonfailure in the config but I see nothing about telling WebTest to register no failure at all in the case of a Javascript error. Where or how do I set that? Ken Thank You! On 5/9/08, Marc Guillemot <[EMAIL PROTECTED]> wrote: > > Hi Ken, > > > ... > > > I have recently had some words here with engineers about that other, > > chemical element testing framework. They want it because then they > > don't have to fix the JS errors in the code. But I picked WebTest > > partly *because* it detects those errors. So far my choice has > > prevailed. > > > in fact WebTest allows you both options: fail on JS errors or ignore them. > The default setting is to fail on JS errors because we consider that > they denote a problem in the application that should be fixed ASAP (and > that is cheaper to fix early). Nevertheless you sometimes need to ignore > JS errors when you don't have easy access to the sources (third party > library or testing done - too - late). > > > > If there are any other experts out there floating around who would like > > to work in SF, maybe a private inbox would be good .. especially if they > > also know some JUnit. > > > SF is quite far away ;-) Remote? > > Cheers, > Marc. > > -- > Blog: http://mguillem.wordpress.com > > > _______________________________________________ > WebTest mailing list > [email protected] > http://lists.canoo.com/mailman/listinfo/webtest >
