public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Thomas Fitzsimmons <fitzsim@redhat.com>
To: Michael Koch <konqueror@gmx.de>
Cc: mauve-discuss@sources.redhat.com
Subject: Re: Patch: GUI testing framework
Date: Tue, 04 Jan 2005 16:39:00 -0000	[thread overview]
Message-ID: <1104856780.6374.135.camel@tortoise.toronto.redhat.com> (raw)
In-Reply-To: <200501041002.30797.konqueror@gmx.de>

On Tue, 2005-01-04 at 10:02 +0100, Michael Koch wrote:
> Am Dienstag, 4. Januar 2005 00:36 schrieb Thomas Fitzsimmons:
> > Hi,
> >
> > This patch adds support to batch_run for running GUI tests, either
> > within an Xvfb server (default) or directly on the tester's
> > desktop.  It also introduces the GUI tag; all tests that require
> > DISPLAY to be set should be tagged as GUI tests.
> >
> > I tested this with the java.awt.Robot tests I posted last week. 
> > The tests run properly both within Xvfb and on my desktop.
> 
> Nice. Classpath has it now too, so we can generally test it too 
> directly.
> 
> > I would like to rely on the metacity window manager, since it
> > handles inset sizing correctly.
> 
> Depending on a specific window manager is stupid. It just makes the 
> hurdles for users of mauve higher. If we have problems with a 
> specific window manager and its his fault and not ours we should 
> report bugs.
> 

OK.  Can we default to metacity?  I'm thinking of:

if test "x$WM" = "x" ; then
    WM=metacity
fi

Then you could set WM on the command line.

Tom


  reply	other threads:[~2005-01-04 16:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-03 23:37 Thomas Fitzsimmons
2005-01-04  8:31 ` Thomas Zander
2005-01-04 18:08   ` Thomas Fitzsimmons
2005-01-04 21:16     ` Thomas Fitzsimmons
2005-01-04  9:01 ` Michael Koch
2005-01-04 16:39   ` Thomas Fitzsimmons [this message]
2005-01-04 17:35     ` Michael Koch
2005-01-04 18:28       ` Thomas Fitzsimmons
2005-01-04 19:28     ` Tom Tromey
2005-01-04 21:08     ` Michael Koch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1104856780.6374.135.camel@tortoise.toronto.redhat.com \
    --to=fitzsim@redhat.com \
    --cc=konqueror@gmx.de \
    --cc=mauve-discuss@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).