From: Edwin Steiner <edwin.steiner@gmx.net>
To: mauve-discuss@sources.redhat.com
Subject: inconsistent test names
Date: Fri, 18 Nov 2005 19:08:00 -0000 [thread overview]
Message-ID: <20051118190804.GA10989@localhost.localdomain> (raw)
Hello!
I'm one of the developers of the cacao jvm[1]. We use mauve
intensively to test cacao and it is a very good test suite.
Currently I'm developing an automated testing framework for
cacao[2]. You can see preliminary results here (large page!):
http://www.complang.tuwien.ac.at/cacaojvm//tgolem/2005-11-18T03-22/mauve.html
One problem I've run accross is that some mauve tests use
inconsistent names to report PASSes and FAILs. The most troublesome
cases are those, where a *named* check/fail is followed by an
*unnamed* one. For example:
gnu/testlet/java/net/MulticastSocket/MulticastSocketTest.java:207
there is a
harness.fail("could not create FIRST multicast socket on shared port
" + sharedMcastPort);
at this line. The next check on line 216 and unnamed. Now if the first check fails,
and the second succeeds, you get a bogus PASS line like:
PASS: gnu.testlet.java.net.MulticastSocket.MulticastSocketTest: could not
create SECOND multicast socket on shared port 1234 (number 2)
from the harness.
If you also think these cases should be fixed (by naming the checks),
I would be happy to provide patches. Makes more sense than teaching
my tgolem to work around these cases.
-Edwin
[1] http://www.cacaojvm.org/
[2] http://www.cacaojvm.org/tgolem
Most of the tgolem code is not cacao specific and I plan
to release it as a GPL project within the next months.
next reply other threads:[~2005-11-18 19:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 19:08 Edwin Steiner [this message]
2005-11-24 21:50 ` Mark Wielaard
2005-11-25 19:28 ` Tom Tromey
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=20051118190804.GA10989@localhost.localdomain \
--to=edwin.steiner@gmx.net \
--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).