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: How to document test procedures? From:Randall Raemon <rlr -at- HAL -dot- COM> Date:Sun, 8 Jan 1995 12:22:22 -0600
In message <9501062003 -dot- AA24099 -at- hal -dot- com>
Sue Heim writes:
> Oh joy!! I have been assigned to a committee whose charter is to
> write the process and procedures for testing our software (both
> upgrade and new releases). Does anyone know of any books, or other
> information, that is available that I could use as a foundation?
Some references for you:
Testing Computer Software
Kaner, Falk, and Nguyen
Van Norstrand Reinhold, 1993
In the various software testing books that I used, this is the most
comprehensive and readable. There is discussion on the full range of
things: test techniques, problem tracking systems, tools, and legal
Depending on what kind of formality your site has, then the
following IEEE standards might be useful:
Std 829: Software Test Documentation
Std 983: Software Quality Assurance Planning
Std 1008: Software Unit Testing
Std 1063: Software User Documentation
If you consider getting more than 2-4 standards, then it is more
cost effective to get the Software Standards Collection. The 1994
edition was published about mid-94.