TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Names of Documents-Testing From:"Anthony Markatos" <tonymar -at- hotmail -dot- com> To:kimber_miller -at- acs-inc -dot- com, techwr-l -at- lists -dot- raycomm -dot- com Date:Tue, 09 Nov 1999 10:03:41 PST
Kimber Miller asks for definition of Test Procedure (along with other
Tony Markatos responds:
BLACK BOX TEST PROCEDURES
Software requirement spec defines essential tasks. (Keyword is essential; we
can not test everything - only the essential). From essential tasks, black
box (i.e., systems level) test cases are determined. From black box test
cases, (systems level) test procedures are written.
WHITE BOX TEST PROCEDURES
Software requirements spec is used to create systems design. Systems design
determines essential aspects of the design that need to be tested. (Key
word is 'essential'; we can not test everything - only the essential). From
these essential design aspects, white box (i.e, design specific) test cases
are created. From these white box test cases, white box test procedures are