From: Tom Tromey <tromey@redhat.com>
To: Edwin Steiner <edwin.steiner@gmx.net>
Cc: mauve-discuss@sources.redhat.com
Subject: Re: inconsistent test names
Date: Fri, 25 Nov 2005 19:28:00 -0000 [thread overview]
Message-ID: <17287.25388.605383.259537@localhost.localdomain> (raw)
In-Reply-To: <20051118190804.GA10989@localhost.localdomain>
>>>>> "Edwin" == Edwin Steiner <edwin.steiner@gmx.net> writes:
Edwin> One problem I've run accross is that some mauve tests use
Edwin> inconsistent names to report PASSes and FAILs. The most troublesome
Edwin> cases are those, where a *named* check/fail is followed by an
Edwin> *unnamed* one. For example:
Yeah, this is a problem. It is kind of a pain to write this
correctly.
I wonder if we should just give up on the current scheme and do what
was suggested years ago, namely just name the test case after the
.class, and do a single big pass/fail for the entire file as a whole.
Then we would be guaranteed that the test names would be stable (as
stable as the file names).
We could still track down failures by passing a special flag that
would make Mauve dump a stack trace on a failing check(). If compiled
with debugging this would give the line number -- which would be even
more convenient than what we do now.
Thoughts?
Tom
prev parent reply other threads:[~2005-11-25 19:28 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
2005-11-25 19:28 ` Tom Tromey [this message]
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=17287.25388.605383.259537@localhost.localdomain \
--to=tromey@redhat.com \
--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).