This is the mail archive of the
mailing list for the Mauve project.
Re: inconsistent test names
- From: Tom Tromey <tromey at redhat dot com>
- To: Edwin Steiner <edwin dot steiner at gmx dot net>
- Cc: mauve-discuss at sources dot redhat dot com
- Date: Fri, 25 Nov 2005 12:17:00 -0700
- Subject: Re: inconsistent test names
- References: <20051118190804.GA10989@localhost.localdomain>
- Reply-to: tromey at redhat dot com
>>>>> "Edwin" == Edwin Steiner <email@example.com> 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
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.