public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Noa Resare <noa@resare.com>
To: mauve-discuss@sources.redhat.com
Subject: tests impossible to pass with class library written using only spec?
Date: Mon, 20 Sep 2004 16:03:00 -0000	[thread overview]
Message-ID: <1095696186.25818.33.camel@c-351f72d5.01-60-6c6b701.cust.bredbandsbolaget.se> (raw)

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

             reply	other threads:[~2004-09-20 16:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-20 16:03 Noa Resare [this message]
2004-09-20 19:22 ` Mark Wielaard

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=1095696186.25818.33.camel@c-351f72d5.01-60-6c6b701.cust.bredbandsbolaget.se \
    --to=noa@resare.com \
    --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).