From: Thomas Fitzsimmons <fitzsim@redhat.com>
To: mauve-discuss@sources.redhat.com
Subject: [PATCH] Enable GUI tests by default
Date: Wed, 05 Jan 2005 00:18:00 -0000 [thread overview]
Message-ID: <1104884316.6374.168.camel@tortoise.toronto.redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]
Hi,
I just committed this patch. It enables the GUI tests by default in
both choose and choose-classes, allows setting of NATIVE on the command
line and sets WM to /bin/true if metacity is not found. I also
committed the gnu.testlet.java.awt.Robot tests.
Tom
2005-01-04 Thomas Fitzsimmons <fitzsim@redhat.com>
* batch_run: Allow NATIVE to be set on the command line. Set WM
to /bin/true if metacity is not found.
* choose: Include GUI tests by default.
* choose-classes: Likewise.
* gnu/testlet/java/awt/Robot/mouseMove.java: New test.
* gnu/testlet/java/awt/Robot/mousePress.java: Likewise.
* gnu/testlet/java/awt/Robot/constructors.java: Likewise.
* gnu/testlet/java/awt/Robot/createScreenCapture.java: Likewise.
* gnu/testlet/java/awt/Robot/getPixelColor.java: Likewise.
* gnu/testlet/java/awt/Robot/keyPress.java: Likewise.
* gnu/testlet/java/awt/Robot/keyRelease.java: Likewise.
* gnu/testlet/java/awt/Robot/mouseRelease.java: Likewise.
* gnu/testlet/java/awt/Robot/mouseWheel.java: Likewise.
[-- Attachment #2: Type: text/x-patch, Size: 2048 bytes --]
Index: batch_run
===================================================================
RCS file: /cvs/mauve/mauve/batch_run,v
retrieving revision 1.6
diff -u -r1.6 batch_run
--- batch_run 4 Jan 2005 20:53:30 -0000 1.6
+++ batch_run 5 Jan 2005 00:09:39 -0000
@@ -44,8 +44,10 @@
COMPILER_FLAGS="-g"
+if test "x$NATIVE" = "x"; then
NATIVE=
#NATIVE="true"
+fi
# Cleanup
find gnu/testlet -name "*.class" | xargs rm -f
@@ -69,6 +71,10 @@
XVFB=`which Xvfb`
if test "x$WM" = "x"; then
WM=`which metacity`
+ # check if we found metacity
+ if test "x$WM" = "x"; then
+ WM=`which true`
+ fi
fi
if test -z "$SHOW_GUI_TESTS"; then
Index: choose
===================================================================
RCS file: /cvs/mauve/mauve/choose,v
retrieving revision 1.27
diff -u -r1.27 choose
--- choose 4 Jan 2005 20:53:30 -0000 1.27
+++ choose 5 Jan 2005 00:09:39 -0000
@@ -121,7 +121,7 @@
done
# By default, use JDK1.1.
-test -z "$tags" && tags="JDK1.0 JDK1.1"
+test -z "$tags" && tags="JDK1.0 JDK1.1 GUI"
test -n "$verbose" && echo "tags = $tags"
test -n "$verbose" && echo "spectags = $spectags"
Index: choose-classes
===================================================================
RCS file: /cvs/mauve/mauve/choose-classes,v
retrieving revision 1.4
diff -u -r1.4 choose-classes
--- choose-classes 26 Dec 2004 17:02:16 -0000 1.4
+++ choose-classes 5 Jan 2005 00:09:39 -0000
@@ -70,6 +70,10 @@
file="`echo $i | tr . /`"
file_specs="$file_specs $file"
;;
+ GUI)
+ tags="$tags GUI $i"
+ test -z "$seen_dashdash" && spectags="$spectags $i"
+ ;;
JAVA2)
tags="$tags JDK1.0 JDK1.1 JDK1.2 $i"
test -z "$seen_dashdash" && spectags="$spectags $i"
@@ -118,7 +122,7 @@
done
# By default, use JDK1.1.
-test -z "$tags" && tags="JDK1.0 JDK1.1"
+test -z "$tags" && tags="JDK1.0 JDK1.1 GUI"
test -n "$verbose" && echo "tags = $tags"
test -n "$verbose" && echo "spectags = $spectags"
reply other threads:[~2005-01-05 0:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1104884316.6374.168.camel@tortoise.toronto.redhat.com \
--to=fitzsim@redhat.com \
--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).