You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@commons.apache.org by Todd Jonker <tv...@pobox.com> on 2002/12/10 00:06:07 UTC
[Jelly] JellyUnit JellyAssertionFailedError not an Error
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.
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.
.T.
--
so much to see so much to do / so what's wrong with taking the backstreets
you'll never know if you don't go / you'll never shine if you don't glow
Re: [jelly] scripting system for GUI tests (was Re: [Jelly]
JellyUnit JellyAssertionFailedError not an Error)
Posted by Todd Jonker <tv...@pobox.com>.
No, there isn't any relation. I wasn't aware of Abbot; thanks for the
pointer, Paul. I'll definitely look into it. However, unless Abbot
provides some fairly sophisticated extension mechanisms, I may not be able
to use it.
The (experimental) test framework is for a custom GUI framework that is part
of the Seedling component application platform.
http://seedling.sourceforge.net/
I have (uncommitted) Jelly tags for configuring Seedling components via XML
(in addition to plain properties files).
Seedling GUI-framework module, Bonsai, has a sophisticated system for
connecting widgets with each other and with application components. I've
got some (hackish) Jelly tags extending JellySwing to support this. Then
yesterday I wrote some other tags extending JellyUnit to handle the
acceptance tests.
My main issue is that it would be desirable to write Unit tests (as well as
Acceptance tests) with the same framework, which means I need access to some
application internals beyond the Robot/Screen-scrape level. With Jelly my
test scripts can dive in to any level necessary. The only real problems are
the usual Swing threading/timing grunge.
.T.
On 12/10/02 10:53 AM, paul@activemath.org wrote:
> Is there any relation between this and the Abbot gui-scripting ?
> http://abbot.sourceforge.net/
>
> Paul
>
>
> On Mardi, décembre 10, 2002, at 10:07 , James Strachan wrote:
>
>>> 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.
--
I do not think there is any thrill that can go through the human heart like
that felt by the inventor as he sees some creation of the brain unfolding
to success... Such emotions make a man forget food, sleep, friends, love,
everything. -- Nikola Tesla, electrical engineer and inventor (1856-1943)
Re: [jelly] scripting system for GUI tests (was Re: [Jelly] JellyUnit JellyAssertionFailedError not an Error)
Posted by Paul Libbrecht <pa...@activemath.org>.
Is there any relation between this and the Abbot gui-scripting ?
http://abbot.sourceforge.net/
Paul
On Mardi, décembre 10, 2002, at 10:07 , James Strachan wrote:
>> 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.
Re: [Jelly] JellyUnit JellyAssertionFailedError not an Error
Posted by Todd Jonker <tv...@pobox.com>.
On 12/10/02 4:07 AM, james_strachan@yahoo.co.uk wrote:
> 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.
Excellent. Thank you!
.T.
Re: [Jelly] JellyUnit JellyAssertionFailedError not an Error
Posted by James Strachan <ja...@yahoo.co.uk>.
From: "Todd Jonker" <tv...@pobox.com>
> 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