Thanks! We expect to start looking into SWT in 2008, depending on when
the 1.0 Swing version is released :)

Best regards,
-Alex

--- In java-gui-testing@yahoogroups.com, "Carfield Yim" <carfield@...>
wrote:
>
> Look cool, how about SWT support??
>
> On Dec 28, 2007 10:22 PM, Alex Ruiz <alruiz15@...> wrote:
> >
> >
> >
> >
> >
> >
> > --- In java-gui-testing@yahoogroups.com, "Alastair Montgomery"
> >
> > <a.montgomery@> wrote:
> > >
> > > Thanks I'll have a look at Abbot and Xstudio.
> > >
> >
> > Hi Alastair,
> >
> > Another good alternative for Swing GUI testing is FEST (
> > http://fest.easytesting.org/swing/ ). Its main features are:
> >
> > 1. Compact API that is easy to read and write (uses fluent interfaces
> > to create a DSL-oriented API)
> > 2. Supports both JUnit and TestNG
> > 3. Embeds screenshots of failed GUI tests in both JUnit and TestNG
> > HTML reports
> >
> > Also, please take a look at the latest SNAPSHOT release (version
> > 0.8-SNAPSHOT) at
> >
> >
http://fest.googlecode.com/svn/trunk/fest/m2/repository/fest/fest-swing/0.8-SNAP\
SHOT/
> >
> > The changelog for this release can be found at
> > http://fest.easytesting.org/swing/changes-report.html
> >
> > We are in the process of updating the project's documentation before
> > having a full 0.8 release (next week.) This release adds new features
> > and is focused on making test troubleshooting easier. For example,
> > when a GUI component is not found, the ComponentLookupException
thrown
> > shows a list of available components in the hierarchy. Such list uses
> > indentation to better understand such hierarchy.
> >
> > I hope that helps.
> >
> > Best regards,
> > -Alex.
> >
> >
> >
> >
>