Thomas Zander | 6 Feb 21:26 2005
Picon

New runner

Hi,

I promised to continue work on a much much easier way for people to use 
mauve.  Many of the people I know are not able to run the tests due to the 
dependency on the autotools.
In short I plan to
a) provide a jar which anyone can run using their own preferred VM
b) provide simpler feedback in the form of html or even XML so everyone can 
put his or her results online.

I'd like to present an intermediate version for feedback and perhaps for 
inclusion in the mauve CVS (although I'm personally quite please with 
darcs :)

Please download and try on all your VMs;
http://members.home.nl/zander/alltests.jar

The resulting html of my installed vm is visible on:
http://members.home.nl/zander/results/

The sources of the runner are also provided on:
http://members.home.nl/zander/newRunner.tar.gz

I'm still going to work on an XML format, like discussed in an earlier post 
so better aggregate results can be posted by VM groups online for 
comparison.  Its not progressing as fast as I'd like; but I'm getting 
there :-)  Anyway, this is just a "I did not forget about this just yet" 
message.

I'd love to hear feedback on what is wrong/incomplete or great.
(Continue reading)

Jeroen Frijters | 7 Feb 09:54 2005
Picon

RE: New runner

Thomas Zander wrote:
> Please download and try on all your VMs;
> http://members.home.nl/zander/alltests.jar

On my (Windows) system a bunch of tests fail because the
gnu.testlet.config settings don't make sense. Also, some of the socket
tests fail because they do a downcast from TestHarness to
SimpleTestHarness.

Thanks,
Jeroen

Robert Schuster | 7 Feb 11:42 2005
Picon
Picon

ChangeLog entry

Hello Audrius,
please do not forget to write a ChangeLog entry for each patch you apply.

For these two patches I have done this for you:

2005-02-05 Audrius Meskauskas <audriusa@...>

    * gnu/testlet/javax/swing/text/html/HTML/HTML_Test.java,

 gnu/testlet/javax/swing/text/html/parser/AttributeList/AttributeList_test.java 

    gnu/testlet/javax/swing/text/html/parser/DTD/DTD_test.java,
    gnu/testlet/javax/swing/text/html/parser/Element/Element_Test.java,
    gnu/testlet/javax/swing/text/html/parser/Entity/Entity_Test.java,

 gnu/testlet/javax/swing/text/html/parser/TagElement/TagElement_Test.java:
    Changed JDK tag to 1.2.

2005-02-05 Audrius Meskauskas <audriusa@...>

    * 
gnu/testlet/javax/swing/text/html/parser/AttributeList/AttributeList_test.java 
,
    gnu/testlet/javax/swing/text/html/parser/DTD/DTD_test.java,
    gnu/testlet/javax/swing/text/html/parser/Element/Element_Test.java,
    gnu/testlet/javax/swing/text/html/parser/Entity/Entity_Test.java,

 gnu/testlet/javax/swing/text/html/parser/TagElement/TagElement_Test.java:
    New tests.

(Continue reading)

Thomas Zander | 7 Feb 20:40 2005
Picon

Re: New runner

On Mon, Feb 07, 2005 at 09:54:54AM +0100, Jeroen Frijters wrote:
> Thomas Zander wrote:
> > Please download and try on all your VMs;
> > http://members.home.nl/zander/alltests.jar
> 
> On my (Windows) system a bunch of tests fail because the
> gnu.testlet.config settings don't make sense. Also, some of the socket
> tests fail because they do a downcast from TestHarness to
> SimpleTestHarness.

Hi, Jeroen. Thanks for your reply.
I've just looked into this; when I delete the config and the
SimpleTestHarness I get compile errors in (only) 9 tests.
The following are easy to fix and run correctly with some modifications
(read: removal of the cast):
    gnu/testlet/java/io/FileDescriptor/jdk11.java
    gnu/testlet/java/io/FileReader/jdk11.java
    gnu/testlet/java/io/FileWriter/jdk11.java
    gnu/testlet/java/io/RandomAccessFile/jdk11.java

These are a bit more difficult; but I believe them to be broken by design
or not usable for a 'java -jar' kind of test anyway.
I'll be more specific:
These 4 tests each test some socket stuff based completely on the
assumtion that there is someone (an smtp host) listening on a
pre-configured host/port.  This is quite an assumtion that is not very
usable in the proposed (portable) test-jar.
    gnu/testlet/java/net/Socket/SocketTest.java
    gnu/testlet/java/net/Socket/jdk12.java
    gnu/testlet/java/net/Socket/jdk13.java
(Continue reading)

Jeroen Frijters | 9 Feb 10:25 2005
Picon

RE: New runner

Thomas Zander wrote:
> Hi, Jeroen. Thanks for your reply.
> I've just looked into this; when I delete the config and the
> SimpleTestHarness I get compile errors in (only) 9 tests.
> The following are easy to fix and run correctly with some 
> modifications
> (read: removal of the cast):
>     gnu/testlet/java/io/FileDescriptor/jdk11.java
>     gnu/testlet/java/io/FileReader/jdk11.java
>     gnu/testlet/java/io/FileWriter/jdk11.java
>     gnu/testlet/java/io/RandomAccessFile/jdk11.java
> 
> These are a bit more difficult; but I believe them to be 
> broken by design or not usable for a 'java -jar' kind of
> test anyway.
> I'll be more specific:
> These 4 tests each test some socket stuff based completely on the
> assumtion that there is someone (an smtp host) listening on a
> pre-configured host/port.  This is quite an assumtion that is not very
> usable in the proposed (portable) test-jar.
>     gnu/testlet/java/net/Socket/SocketTest.java
>     gnu/testlet/java/net/Socket/jdk12.java
>     gnu/testlet/java/net/Socket/jdk13.java
>     gnu/testlet/java/net/Socket/jdk14.java

I don't think they're inherently unusable from a jar, I'd like to see a
gnu.testlet.config version that reads the settings from a properties
file (or whatever) instead of hardcoding them in the auto dance.

> The following test tests things like being able to open a 
(Continue reading)

Thomas Zander | 9 Feb 10:36 2005
Picon

Re: New runner

On Wed, Feb 09, 2005 at 10:25:03AM +0100, Jeroen Frijters wrote:
> Thomas Zander wrote:
> > Hi, Jeroen. Thanks for your reply.
> > I've just looked into this; when I delete the config and the
> > SimpleTestHarness I get compile errors in (only) 9 tests.
> > The following are easy to fix and run correctly with some 
> > modifications
> > (read: removal of the cast):
> >     gnu/testlet/java/io/FileDescriptor/jdk11.java
> >     gnu/testlet/java/io/FileReader/jdk11.java
> >     gnu/testlet/java/io/FileWriter/jdk11.java
> >     gnu/testlet/java/io/RandomAccessFile/jdk11.java
> > 
> > These are a bit more difficult; but I believe them to be 
> > broken by design or not usable for a 'java -jar' kind of
> > test anyway.
> > I'll be more specific:
> > These 4 tests each test some socket stuff based completely on the
> > assumtion that there is someone (an smtp host) listening on a
> > pre-configured host/port.  This is quite an assumtion that is not very
> > usable in the proposed (portable) test-jar.
> >     gnu/testlet/java/net/Socket/SocketTest.java
> >     gnu/testlet/java/net/Socket/jdk12.java
> >     gnu/testlet/java/net/Socket/jdk13.java
> >     gnu/testlet/java/net/Socket/jdk14.java
> 
> I don't think they're inherently unusable from a jar, I'd like to see a
> gnu.testlet.config version that reads the settings from a properties
> file (or whatever) instead of hardcoding them in the auto dance.

(Continue reading)

Jeroen Frijters | 9 Feb 10:48 2005
Picon

RE: New runner

Thomas Zander wrote:
> The way the config settings are shipped is not the issue here;  the
> question where a socket can connect to that is reachable from 
> the testing machine so the test does not fail because of wrong
> reasons is a bigger problem.

I thought the tests only connect to an SMTP server? Presumably most
people have access to an SMTP server. You could ask a question in the
test configuration step (where you ask about awt tests).

> When we are actually running this test we already did a 'java 
> -jar' and we found several classes in that jar.  Does that not
> imply that the tests in that class will pass?

Not necessarily. With IKVM, for example, you can pre-compile the jar
into a .NET executable and run that directly, that way no Java I/O is
involved in starting up the tests. I'm sure a similar scenario exists
for gcj.

Regards,
Jeroen

Bryce McKinlay | 16 Feb 20:10 2005
Picon

Class choosing script - Tag sensitivity

The choose-classes script seems to be very sensitive to extra whitespace 
characters around the tags. For example, the test below was not being 
run due to an extra space. Perhaps some sed/egrep can fix this? In the 
mean time, this patch fixes the one I found.

Bryce

2005-02-16  Bryce McKinlay  <mckinlay@...>

    * gnu/testlet/java/lang/Class/serialization.java: Remove stray space
    from 'Tags'.

--- gnu/testlet/java/lang/Class/serialization.java      17 Jan 2005 
17:03:24 -0000      1.2
+++ gnu/testlet/java/lang/Class/serialization.java      16 Feb 2005 
19:06:59 -0000
 <at>  <at>  -1,4 +1,4  <at>  <at> 
-// Tags: JDK1.2
+// Tags: JDK1.2

 // Copyright (C) 2005 David Gilbert <david.gilbert@...>

Bryce McKinlay | 19 Feb 04:44 2005
Picon

JLS vs JDK tags

Does it make any sense to keep JLS tags in mauve? Only a handful of test 
cases use them. I'd like to simplify the tags a little and convert 
JLS1.2 -> JDK1.2, etc.

Bryce

Tom Tromey | 19 Feb 17:57 2005
Picon

Re: JLS vs JDK tags

Bryce> Does it make any sense to keep JLS tags in mauve? Only a handful of
Bryce> test cases use them. I'd like to simplify the tags a little and
Bryce> convert JLS1.2 -> JDK1.2, etc.

I never really understood the distinction.  I say nuke 'em.

Tom


Gmane