RE: Instructions and team assignments for getting to Last Call

Thanks for the update for the TEST portion!

 From QA Test FAQ Question #7 ("What makes a good test?") [1],

"A good test is:
       Mappable to the specification (you must know what portion of the 
specification it tests)
       Atomic (tests a single feature rather than multiple features)
       Self-documenting (explains what it is testing and what output it 
       Focused on the technology under test rather than on ancillary 
       Correct "

Would any of these points apply/be relevant to the TEST portion mentioned 
in the excerpted message following
(as possible additional guidance for the TEST portion)?

Also, the QA Note Test Metadata [2] mentions 14 test metadata elements as 
identifier, title, purpose, description, status, specref, preconditions, 
inputs, expected results,
version, contributor, rights, grouping, and seealso.

Some of these are already included in the TEST portion, but would any of 
these additional terms be
  useful for the TEST portion mentioned in excerpted message following?

Thanks and best wishes
Tim Boland NIST


At 04:41 PM 12/30/2005 -0600, you wrote:
>Hi Tim,
>I updated the wiki page for techniques to include the information for the
>TEST portion.
>  -- ------------------------------
>Gregg C Vanderheiden Ph.D.
>Professor - Ind. Engr. & BioMed Engr.
>Director - Trace R & D Center
>University of Wisconsin-Madison
>-----Original Message-----
>From: [] On Behalf
>Of Tim Boland
>Sent: Wednesday, December 28, 2005 3:24 PM
>Subject: Re: Instructions and team assignments for getting to Last Call
>Will there be any consideration of a template for tests, in addition to the
>template mentioned in the excerpted message following?   Is a test template
>appropriate or necessary?
>I think that possibly including such a test template, or at least some
>additional specific instructions for test creators, might serve to enhance
>the consistency of test format across the various SCs, as well as simply the
>process of test description and maintenance.  Since tests are to evaluate
>the implementation of related techniques (which have a template), perhaps
>tests should also have a template?
>Just a thought..
>Thanks and happy new year!
>Tim Boland NIST
>      At 03:05 PM 12/21/2005 -0600, you wrote:
> >4.      Draft new techniques and edit existing ones as required, using
> >the Techniques template in the WIKI <>. Refer
> >to Tips for editing techniques <> for detailed
> >instructions.
> >5.      Include both pass and fail tests in the tests section of each
> >technique. ("Pass" shows correct implementation of the technique; "Fail"
> >shows incorrect implementation.)
> >6.

Received on Tuesday, 3 January 2006 13:59:20 UTC