This is the mail archive of the
mailing list for the Mauve project.
RE: New runner
- From: "Jeroen Frijters" <jeroen at sumatra dot nl>
- To: "Thomas Zander" <TZander at factotummedia dot nl>,<mauve-discuss at sources dot redhat dot com>
- Date: Wed, 9 Feb 2005 10:25:03 +0100
- Subject: 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
> (read: removal of the cast):
> 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.
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
> 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 :-)
This is more tricky to handle, but hopefully we can figure out a way to
get this test in as well.