This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: RFC: Mauve and java.awt.Robot?
- From: Thomas Fitzsimmons <fitzsim at redhat dot com>
- To: Norman Hendrich <hendrich at informatik dot uni-hamburg dot de>
- Cc: java at gcc dot gnu dot org
- Date: Mon, 09 May 2005 13:44:17 -0400
- Subject: Re: RFC: Mauve and java.awt.Robot?
- References: <200505090819.j498JNjh010444@rzdspc1.informatik.uni-hamburg.de>
On Mon, 2005-05-09 at 10:19 +0200, Norman Hendrich wrote:
> Hello everybody,
>
> a simple and a not so simple RFC-type question about java.awt.Robot:
>
>
> Mark> One of the reasons some of the non-gui stuff is in a much better shape
> Mark> is because we have lots of small easy tests that we can run in Mauve.
> Mark> For GNU Classpath releases we make sure that a new release doesn't fail
> Mark> any of the tests that passed in the previous release. We don't have much
> Mark> gui tests in mauve.
>
> Mark> Thomas made java.awt.Robot working and there
> Mark> are some examples on how to use this for automatic testing of the gui
> Mark> components in Mauve.
>
> (1) I just downloaded mauve-nightly.zip, but I cannot find any use of Robot
> in there... neither can grep. Where shall I look?
Check out mauve CVS HEAD from sources.redhat.com:/cvs/mauve. See
gnu/testlet/java/awt/Robot/* and gnu/testlet/java/awt/Frame/*.
> Also, is there a
> snapshot of the Wonka tests, or do I have to do a full CVS checkout?
>
>
> (2) Is there some kind of 'GNU policy' regarding the use of java.awt.Robot
> for automated GUI tests?
>
> java.awt.Robot turns out a pretty dangerous animal, and I am not sure
> that we would want to unleash Robot on unsuspecting users that simply
> type 'make check'.
>
The mauve harness (in mauve CVS HEAD) can be made to run these tests on
an Xvfb server which prevents the Robot from being unleashed on the
developer's desktop.
Tom