commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin van den Bemt <mll...@mvdb.net>
Subject Re: [jelly] for testing existing GUIs?
Date Mon, 23 Dec 2002 10:24:21 GMT
Maybe a tip : check how eclipse is testing their stuff. afaik they are
all automated.

Mvgr,
Martin


On Sun, 2002-12-22 at 04:30, Thomas L Roche wrote:
> Might Jelly be useful for automating testing of SWT/JFace GUIs?
> Why I ask:
> 
> I've written a fair number of wizards for an Eclipse plugin that
> generates Struts artifacts. Unfortunately I unit-test manually, so as
> my functionality grows, so does the time required to regress :-(
> (Please no preaching about test-first development: I see the light,
> and seek only to tread the path :-)
> 
> I'd like to try using something like Abbot
> 
> http://abbot.sourceforge.net/
> 
> but it relies on java.awt.Robot, and AFAIK there is no SWT analog.
> 
> JellySWT also looks interesting, but I suspect it solves a problem
> different than mine. It seems to me that Jelly is for interface RAD
> (RID ?-), and that JellyUnit and JellyTestSuite are designed to allow
> one to easily build test-harness GUIs. By contrast, what I want to do
> is automate testing for _existing_ GUIs. This view seems confirmed by
> 
> http://nagoya.apache.org/eyebrowse/ReadMsg?listName=commons-user@jakarta.apache.org&msgNo=1348
> 
> but not clearly. So I ask:
> 
> Can Jelly do what I want? If so, please lemme know, and please point
> toward example(s) if known. (And feel free to forward.)
> 
> 
> --
> To unsubscribe, e-mail:   <mailto:commons-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:commons-user-help@jakarta.apache.org>
> 
> 



Mime
View raw message