public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
* Existing Mauve tests
@ 2002-09-18 21:47 Daryl Lee
  2002-09-19  5:10 ` Brian Jones
  0 siblings, 1 reply; 2+ messages in thread
From: Daryl Lee @ 2002-09-18 21:47 UTC (permalink / raw)
  To: Mauve Discuss

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Existing Mauve tests
  2002-09-18 21:47 Existing Mauve tests Daryl Lee
@ 2002-09-19  5:10 ` Brian Jones
  0 siblings, 0 replies; 2+ messages in thread
From: Brian Jones @ 2002-09-19  5:10 UTC (permalink / raw)
  To: Daryl Lee; +Cc: Mauve Discuss

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>

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2002-09-19 12:10 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-09-18 21:47 Existing Mauve tests Daryl Lee
2002-09-19  5:10 ` Brian Jones

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).