public inbox for mauve-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tania Bento <tbento@redhat.com>
To: mauve-patches@sources.redhat.com
Subject: FYI: New ComponentEvent test
Date: Fri, 03 Nov 2006 15:01:00 -0000	[thread overview]
Message-ID: <1162566055.17015.167.camel@toothpaste.toronto.redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 221 bytes --]

Hey,

This adds a new test for java.awt.event.ComponentEvent.paramString().

Cheers,
Tania

2006-11-03  Tania Bento  <tbento@redhat.com>

        * gnu/testlet/java/awt/event/ComponentEvent/paramString.java:
New test.




[-- Attachment #2: patch.diff --]
[-- Type: text/x-patch, Size: 2282 bytes --]

Index: gnu/testlet/java/awt/event/ComponentEvent/paramString.java
===================================================================
RCS file: gnu/testlet/java/awt/event/ComponentEvent/paramString.java
diff -N gnu/testlet/java/awt/event/ComponentEvent/paramString.java
--- /dev/null	1 Jan 1970 00:00:00 -0000
+++ gnu/testlet/java/awt/event/ComponentEvent/paramString.java	3 Nov 2006 14:58:55 -0000
@@ -0,0 +1,55 @@
+/* paramString.java 
+   Copyright (C) 2006 RedHat
+   
+This file is part of Mauve.
+
+Mauve is free software; you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation; either version 2, or (at your option)
+any later version.
+
+Mauve is distributed in the hope that it will be useful, but
+WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with Mauve; see the file COPYING.  If not, write to the
+Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
+02110-1301 USA.
+
+*/
+
+// Tags: 1.4
+
+package gnu.testlet.java.awt.event.ComponentEvent;
+
+import java.awt.Button;
+import java.awt.event.ComponentEvent;
+
+import gnu.testlet.TestHarness;
+import gnu.testlet.Testlet;
+
+public class paramString implements Testlet
+{
+
+  public void test(TestHarness harness)
+  {
+    Button button = new Button();
+    ComponentEvent event = new ComponentEvent(button, 
+                                              ComponentEvent.COMPONENT_MOVED);
+
+    // Check that previous code produced incorrect string representation.
+    harness.check(! event.paramString().equalsIgnoreCase(
+              "COMPONENT_MOVED java.awt.Rectangle[x=0,y=0,width=0,height=0]"));
+    
+    // Check that current code produces correct string representation.
+    harness.check(event.paramString(), "COMPONENT_MOVED (0,0 0x0)");
+    
+    // Check that correct string representation is returned when
+    // an invalid event ID is given.
+    event = new ComponentEvent(button, ComponentEvent.COMPONENT_MOVED + 1024);
+    harness.check(event.paramString(), "unknown type");
+  }
+
+}

             reply	other threads:[~2006-11-03 15:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-03 15:01 Tania Bento [this message]
2006-11-03 15:04 ` David Gilbert
2006-11-03 15:10   ` Roman Kennke
2006-11-03 15:19     ` Tania Bento

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=1162566055.17015.167.camel@toothpaste.toronto.redhat.com \
    --to=tbento@redhat.com \
    --cc=mauve-patches@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).