This is the mail archive of the
mailing list for the Mauve project.
Re: Tweaking default java.awt.Robot settings
- From: Thomas Fitzsimmons <fitzsim at redhat dot com>
- To: Steve McKayâ <smckay at google dot com>
- Cc: mauve-discuss at sources dot redhat dot com
- Date: Tue, 25 Sep 2007 14:10:39 -0400
- Subject: Re: Tweaking default java.awt.Robot settings
- References: <email@example.com>
Steve McKayâ wrote:
I've noticed that at least some of the tests using java.awt.Robot are
non-deterministic due to lags is the underlying window system. The
java.awt.Component.keyPressTest, for example, fails some of the time
(on linux, windows, linux+wine, ...). It looks like enabling
autoWaitForIdle (waits for the awt EventQueue to be empty before
adding new events to the queue), and setting autoDelay (pauses for an
arbitrary period of time) to some magic number of millis well above
zero (I use 100) significantly reduces failures. Would anyone object
to configuring the Robot with settings like this by default?
No objections here, that sounds like a good idea. When you say "significantly
reduces failures", does that mean some non-deterministic failures persist with
the new auto* settings?