From: Thomas Fitzsimmons <fitzsim@redhat.com>
To: David Gilbert <david.gilbert@object-refinery.com>
Cc: Lillian Angel <langel@redhat.com>,
mauve-patches <mauve-patches@sources.redhat.com>
Subject: Re: Patch: New Lightweight tests
Date: Wed, 22 Feb 2006 17:12:00 -0000 [thread overview]
Message-ID: <1140628341.1404.192.camel@tortoise.toronto.redhat.com> (raw)
In-Reply-To: <43FC373E.9010904@object-refinery.com>
On Wed, 2006-02-22 at 10:04 +0000, David Gilbert wrote:
> Hi Lillian,
>
> I wonder if these methods should really be added to TestHarness, they
> seem a little too "specialised" to me (especially the rectangle corner
> color tests), and it would be nice to keep TestHarness as simple as
> possible. Maybe you could create a utility class in
> gnu.testlet.java.awt.* that contains static methods that perform these
> checks? Then you could share that between your Frame and Container tests.
Yes, it's probably cleaner to have a utility class in
gnu.testlet.java.awt.
Tom
>
> Regards,
>
> Dave
>
> Lillian Angel wrote:
>
> >On Tue, 2006-02-21 at 18:52 -0500, Lillian Angel wrote:
> >
> >
> >>I added new tests for Lightweight Containers.
> >>
> >>
> >
> >I forgot to mention, I added some new methods to TestHarness. These
> >methods are helpful for testing locations on the screen when using
> >Lightweight/Heavyweight widgets. It made sense to add these to
> >TestHarness, since they are used in Frame and Container.
> >
> >
> >
> >>2006-02-21 Lillian Angel <langel@redhat.com>
> >>
> >> * gnu/testlet/TestHarness.java
> >> (checkColor): New method used to compare colors.
> >> (checkRectangleOuterColors): New method used to compare the
> >> colors of a rectangle's corners to the colors of the pixels
> >> surrounding the corners.
> >> (checkRectangleCornerColors): New method used to compare
> >> the colors of the pixels at the corners of a rectangle, to
> >> a given color.
> >> * gnu/testlet/java/awt/Container/LightweightContainer.java:
> >> New Test.
> >> * gnu/testlet/java/awt/Frame/size1.java
> >> (checkColor): Removed.
> >> (test): Changed to use new methods in TestHarness.
> >>
> >>
> >>
next prev parent reply other threads:[~2006-02-22 17:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 23:52 Lillian Angel
2006-02-21 23:55 ` Lillian Angel
2006-02-22 10:04 ` David Gilbert
2006-02-22 14:48 ` Lillian Angel
2006-02-22 17:12 ` Thomas Fitzsimmons [this message]
2006-02-22 8:12 ` Roman Kennke
2006-02-22 14:49 ` Lillian Angel
2006-02-22 10:28 ` David Gilbert
2006-02-22 14:51 ` Lillian Angel
2006-02-22 15:09 ` Michael Koch
2006-02-22 15:12 ` Lillian Angel
2006-02-22 15:55 ` FYI: " Lillian Angel
2006-02-22 17:25 ` Patch: " Thomas Fitzsimmons
2006-02-22 17:47 ` FYI: " Lillian Angel
2006-02-22 18:18 ` Lillian Angel
2006-02-24 2:02 ` Thomas Fitzsimmons
2006-02-24 14:49 ` Lillian Angel
2006-02-24 15:17 ` Lillian Angel
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=1140628341.1404.192.camel@tortoise.toronto.redhat.com \
--to=fitzsim@redhat.com \
--cc=david.gilbert@object-refinery.com \
--cc=langel@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).