From: David Gilbert <david.gilbert@object-refinery.com>
To: Bryce McKinlay <mckinlay@redhat.com>
Cc: Anthony Balkissoon <abalkiss@redhat.com>,
classpath@gnu.org, mauve-discuss@sources.redhat.com
Subject: Re: Mauve wishlist
Date: Wed, 22 Mar 2006 11:12:00 -0000 [thread overview]
Message-ID: <44213403.3020307@object-refinery.com> (raw)
In-Reply-To: <4420874C.2090800@redhat.com>
Bryce McKinlay wrote:
>
> It is not reasonable to expect test case developers ensure that all
> tests "run linearly". Exceptions can potentially be thrown at any
> time, so to ensure linearity, every check() call would need wrapped
> with a try/catch.
>
If there is a linear sequence of checks in a test() method, and an
(unexpected) exception causes the test() method to exit early (after,
say, 3 checks out of 10), I don't consider that to be non-linear. If we
are comparing run A to run B, and 10 checks complete in run A, but only
3 checks complete in run B, we can safely assume that checks 4 to 10
were not completed in run B, and report that.
The majority of test() methods in Mauve are written that way, so I don't
think it is an unreasonable requirement, especially if it means we can
develop better comparison/regression reporting on top of the existing
TestHarness.
Regards,
Dave
prev parent reply other threads:[~2006-03-22 11:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 16:27 Thomas Fitzsimmons
2006-03-17 21:06 ` David Daney
2006-03-18 8:15 ` Michael Koch
2006-03-17 22:34 ` Audrius Meskauskas
2006-03-20 10:53 ` Arnaud Vandyck
2006-03-20 16:51 ` Anthony Balkissoon
2006-03-21 16:58 ` David Gilbert
2006-03-21 22:24 ` Tom Tromey
2006-03-21 23:08 ` Bryce McKinlay
2006-03-22 11:12 ` David Gilbert [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=44213403.3020307@object-refinery.com \
--to=david.gilbert@object-refinery.com \
--cc=abalkiss@redhat.com \
--cc=classpath@gnu.org \
--cc=mauve-discuss@sources.redhat.com \
--cc=mckinlay@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).