public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Roman Kennke <roman@kennke.org>
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: Tue, 20 Jun 2006 19:22:00 -0000	[thread overview]
Message-ID: <1150831363.11657.6.camel@localhost.localdomain> (raw)
In-Reply-To: <44982D85.9080200@object-refinery.com>


Hi David,

that*s awesome! When things are cleaned up we certainly should add this
to some daily test script, or maybe hook up into Mauve (dunno how that
could be done wrt to licensing issues though).

I come to think that the refactoring part should be quite easy using
Eclipse, it's usually only a matter of a few clicks.

/Roman

> 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
> 

  reply	other threads:[~2006-06-20 19:22 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 [this message]
2006-07-24 15:42 ` David Gilbert
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=1150831363.11657.6.camel@localhost.localdomain \
    --to=roman@kennke.org \
    --cc=classpath@gnu.org \
    --cc=david.gilbert@object-refinery.com \
    --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).