From: Mark Wielaard <mark@klomp.org>
To: Edwin Steiner <edwin.steiner@gmx.net>
Cc: mauve-discuss@sources.redhat.com
Subject: Re: inconsistent test names
Date: Thu, 24 Nov 2005 21:50:00 -0000 [thread overview]
Message-ID: <1132869012.5568.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20051118190804.GA10989@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 978 bytes --]
Hi Edwin,
On Fri, 2005-11-18 at 20:08 +0100, Edwin Steiner wrote:
> 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
Very nice overview!
> 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.
> [...]
> 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.
That does make sense to me. Probably the best approach would be to have
an explicit harness.checkPoint("<descriptive string>") after each named
check followed by unnamed ones. But I would be happy with any patch that
solves this issue.
Cheers,
Mark
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-11-24 21:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 19:08 Edwin Steiner
2005-11-24 21:50 ` Mark Wielaard [this message]
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=1132869012.5568.6.camel@localhost.localdomain \
--to=mark@klomp.org \
--cc=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).