This is the mail archive of the
mailing list for the Mauve project.
Existing Mauve tests
- From: Daryl Lee <dol at sources dot redhat dot com>
- To: Mauve Discuss <mauve-discuss at sources dot redhat dot com>
- Date: Thu, 19 Sep 2002 00:49:34 -0400
- Subject: Existing Mauve tests
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.