This is the mail archive of the
mauve-discuss@sources.redhat.com
mailing list for the Mauve project.
tests impossible to pass with class library written using onlyspec?
- From: Noa Resare <noa at resare dot com>
- To: mauve-discuss at sources dot redhat dot com
- Date: Mon, 20 Sep 2004 18:03:06 +0200
- Subject: tests impossible to pass with class library written using onlyspec?
I looking around in some java.io mauve failures i found some failing
test code in gnu/testlet/java/io/OutputStreamWriter/jdk11.java reading
// Note that for java.io the canonical name as returned by
// getEncoding() must be the "historical" name. ISO8859_1.
harness.check(osw2.getEncoding(), "ISO8859_1",
"OutputStreamWriter(writer, encoding)");
osw2.close ();
osw2 = new OutputStreamWriter(baos2, "latin1");
harness.check(osw2.getEncoding(), "ISO8859_1",
"OutputStreamWriter(writer, encoding) // alias");
osw2.close ();
Ah, simple I thought. It must be a list in the java class library
specification that tells what the historical names are. Now i know there
is no such list. That leads me to a more general question: is it ok for
mauve to test functionality that there is no way to implement using only
the class library spec (or looking at the code of the of the tests
preformed and just returning what is asked for)?
cheers/noa
--
And the lions ate the christians and the christians burned the witches,
and even I am out of explanations -- Ola Salo
gpg fingerprint: F3C4 AC90 B885 FE15 344B 4D05 220B 7662 A190 6F09