W3C home > Mailing lists > Public > www-qa-wg@w3.org > July 2004

Re: [SpecGL Draft] E. Good Practice: Write Test Assertions

From: Lynne Rosenthal <lynne.rosenthal@nist.gov>
Date: Fri, 16 Jul 2004 07:33:35 -0400
Message-Id: <5.1.0.14.2.20040716073227.012a3b78@mailserver.nist.gov>
To: Andrew Thackrah <andrew@opengroup.org>, www-qa-wg@w3.org

Good point.  We will need to clarify this.  The assertion would be written 
during or after the specification, but before publication of the 
specification.  The idea is to include the assertion with the specification.

-lynne

At 04:43 AM 7/16/2004, Andrew Thackrah wrote:


>Hi,
>I have one comment/question, below:
>
>On Thursday 15 July 2004 23:56, Lynne Rosenthal wrote:
> >
> > Nicely done. Just a few grammar/spelling changes....and 1 comment at the
>end.
> >
> > At 06:17 PM 7/15/2004 -0400, Karl Dubost wrote:
> >
> > >Good Practice:
> > >         Write Test Assertions
>[snip]
> >
> > >Techniques:
> > >         1. Do not input the feature inside a specification before to 
> have
> > > associated test assertions.
> >
> > Do not put the feature in the specification without having its
> > corresponding test assertion(s).
>
>Are you suggesting that assertions are written before the specification?
>If so I don't this ever happens (?) I thought assertions were derived from
>specs.
>
>-Andrew
Received on Friday, 16 July 2004 07:33:51 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.30 : Thursday, 9 June 2005 12:13:16 GMT