public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: David Gilbert <david.gilbert@object-refinery.com>
To: David Gilbert <david.gilbert@object-refinery.com>
Cc: GNU Classpath <classpath@gnu.org>, mauve-discuss@sourceware.org
Subject: Re: Intel's AWT/Swing test suite
Date: Mon, 24 Jul 2006 15:42:00 -0000	[thread overview]
Message-ID: <44C4EA69.1080609@object-refinery.com> (raw)
In-Reply-To: <44982D85.9080200@object-refinery.com>

Hi All,

I've uploaded a new jar file containing modified test cases from the 
Intel test suite (the jar contains both .java and .class files, see 
below for more details).  Compared to the jar I posted last month, this 
one contains around 900 additional tests.  Most of the new tests are for 
the javax.swing.text.* package:

http://www.object-refinery.com/classpath/htests-20060724.jar

Instructions for running the tests are the same as in my previous message.

Regards,

Dave


David Gilbert wrote:

> Hi All,
>
> Last week Intel posted their AWT/Swing test suite at the Harmony 
> project site.  I've been taking a look at it, to see what value there 
> is in it for GNU Classpath...and, in spite of a lot overlap with 
> Mauve, there are many new tests in there that are useful to us.
>
> Unfortunately they decided to write the tests in the java.awt.* and 
> javax.swing.* namespace, which makes it awkward to run the tests, both 
> against Sun's reference implementation (to verify the tests) and 
> against GNU Classpath (to find bugs in our implementation).  However, 
> it has been relatively straightforward (though tedious) to refactor 
> the tests to move the tests into their own namespace (I used 
> test.java.awt.* and test.javax.swing.*).
>
> You can find a jar file containing both the (JUnit-based) tests and 
> corresponding source code (for around 2,600 tests so far) here:
>
> http://www.object-refinery.com/classpath/htests-20060620.jar
>
> To run the tests, use the following command line:
>
> jamvm -classpath .:lib/junit.jar junit.textui.TestRunner 
> test.java.awt.PackageTestSuite
>
> ...replacing the class name with the name of any test class, or the 
> package level test suites:
>
> test.java.awt.PackageTestSuite
> test.java.awt.datatransfer.PackageTestSuite
> test.java.awt.event.PackageTestSuite
> test.java.awt.font.PackageTestSuite
> test.java.awt.image.PackageTestSuite
> test.javax.swing.PackageTestSuite
> test.javax.swing.border.PackageTestSuite
> test.javax.swing.colorchooser.PackageTestSuite
> test.javax.swing.event.PackageTestSuite
> test.javax.swing.plaf.PackageTestSuite
> test.javax.swing.table.PackageTestSuite
> test.javax.swing.tree.PackageTestSuite
> test.javax.swing.undo.PackageTestSuite
>
> There is also a test suite that will run all tests:
>
> test.AWTSwingTestSuite (runs all tests)
>
> There are still many tests that I haven't extracted from 
> javax.swing.*, javax.swing.plaf.basic.*, javax.swing.plaf.metal.* and 
> javax.swing.text.*.  I'll post a revised test jar file when I've 
> completed those.
>
> Regards,
>
> Dave

  parent reply	other threads:[~2006-07-24 15:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-20 17:14 David Gilbert
2006-06-20 19:22 ` Roman Kennke
2006-07-24 15:42 ` David Gilbert [this message]
2006-07-25  8:21   ` Roman Kennke

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=44C4EA69.1080609@object-refinery.com \
    --to=david.gilbert@object-refinery.com \
    --cc=classpath@gnu.org \
    --cc=mauve-discuss@sourceware.org \
    /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).