From: "Todd Jonker" <[EMAIL PROTECTED]> > Is there a good reason that JellyAssertionFailedError is not an Error but an > Exception? Besides the misleading name, its quite different from plain > JUnit, where AssertionFailedError is actually an Error so you don't have to > handle it explicitly.
Whoops. JellyAssertionFailedError was always meant to extend AssertionFailedError. The idea being that it really was a JUnit assertion failure exception, but just that it was adorned with the JellyUnit context (file, line, column, tag name etc). I've patched the code in CVS to make this the case now. > Background: I'm trying to write a scripting system for acceptance tests of > GUI apps. This involves several custom Jelly tags to do various GUI > assertions an manipulations. I'll post some other questions/problems on > other threads. Sounds interesting. James ------- http://radio.weblogs.com/0112098/ __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
