From: Thomas Zander <TZander@factotummedia.nl>
To: mauve-discuss@sources.redhat.com
Subject: Re: New runner
Date: Mon, 07 Feb 2005 19:41:00 -0000 [thread overview]
Message-ID: <20050207194026.GA1959@factotummedia.nl> (raw)
In-Reply-To: <D92197D0A6547B44A1567814F851FA68069456@LEMBU.sumatrasoftware.com>
[-- Attachment #1: Type: text/plain, Size: 2012 bytes --]
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
gnu/testlet/java/net/Socket/jdk14.java
The following test tests things like being able to open a file we ship in
mauve (in the same package) and other stuff thats really really basic.
(like File.seperator) Quite useless to test in an environment that is
shipped in a jar :-)
gnu/testlet/java/io/File/jdk11.java
What do you think? Should these last 5 tests be modified in any way? Or
should we keep the dependency on config (and SimpleTestHarness) for them
even though they have a different set of problems?
Whatever we decide, I'll stop shipping those in my jar.
--
Thomas Zander
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-02-07 19:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-07 8:55 Jeroen Frijters
2005-02-07 19:41 ` Thomas Zander [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-09 9:48 Jeroen Frijters
2005-02-09 9:25 Jeroen Frijters
2005-02-09 9:36 ` Thomas Zander
2005-02-06 20:27 Thomas Zander
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=20050207194026.GA1959@factotummedia.nl \
--to=tzander@factotummedia.nl \
--cc=mauve-discuss@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).