From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4350 invoked by alias); 20 Jun 2006 19:22:35 -0000 Received: (qmail 4340 invoked by uid 22791); 20 Jun 2006 19:22:32 -0000 X-Spam-Check-By: sourceware.org Received: from kennke.org (HELO box7954.elkhouse.de) (213.9.79.54) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 20 Jun 2006 19:22:30 +0000 Received: from q6557.q.strato-dslnet.de ([89.53.101.87] helo=[192.168.2.5]) by box7954.elkhouse.de with esmtpsa (TLS-1.0:RSA_ARCFOUR_MD5:16) (Exim 4.50) id 1FsmoL-0001vL-Fs; Tue, 20 Jun 2006 22:26:57 +0200 Subject: Re: Intel's AWT/Swing test suite From: Roman Kennke To: David Gilbert Cc: GNU Classpath , mauve-discuss@sourceware.org In-Reply-To: <44982D85.9080200@object-refinery.com> References: <44982D85.9080200@object-refinery.com> Content-Type: text/plain Date: Tue, 20 Jun 2006 19:22:00 -0000 Message-Id: <1150831363.11657.6.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 Content-Transfer-Encoding: 7bit Mailing-List: contact mauve-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: mauve-discuss-owner@sourceware.org X-SW-Source: 2006-q2/txt/msg00013.txt.bz2 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 >