This is the mail archive of the
mauve-discuss@sources.redhat.com
mailing list for the Mauve project.
Re: Existing Mauve tests
- From: Brian Jones <cbj at gnu dot org>
- To: Daryl Lee <dol at sources dot redhat dot com>
- Cc: Mauve Discuss <mauve-discuss at sources dot redhat dot com>
- Date: 19 Sep 2002 08:03:48 -0400
- Subject: Re: Existing Mauve tests
- References: <20020919004934.A19792@tigger>
Daryl Lee <dol@sources.redhat.com> writes:
> I have begun writing "acceptance" tests in Mauve as part of the GNU
> Classpath project. There are existing test suites that do SEEM to
> have been written as part of a class library development activity,
> perhaps by the library class developer himself. That is, there are
> lots of 'harness.debug' calls, and few 'harness.check' calls that
> directly map to class methods.
>
> My question is: Is there a 'social protocol' for a tester to decide
> whether to replace (i.e, 'cvs rm') a test that is superseded by a
> newer, presumably more complete class test? The answer to this
> question will guide how I proceed. -- Daryl Lee Marietta, GA
>
Newer tests would not invalidate old tests unless the old tests were
wrong in some way. If the test really covers the old test cases as
well as new ones then you could remove the old test cases... to keep
the set of test cases neat and clean.
Brian
--
Brian Jones <cbj@gnu.org>