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:Names of Documents-Testing From:kimber_miller -at- acs-inc -dot- com To:<TECHWR-L -at- LISTS -dot- RAYCOMM -dot- COM> Date:Mon, 08 Nov 1999 14:00:52 -0600
Hello!
Bit of a miscommunication tizzy going 'round here, so I want to ask the
techwhirler population in general about their associated names of kinds of
documents:
In my mind and experience, a "test plan" explains the project team's plan to
perform testing. The general strategy, platforms, number of tests, testers,
needed documentation, reporting structure, etc., whatever...
The "test procedure" I write is the step-action instruction that the testers use
to carry out the performance testing (or other testing, as appropriate).
The "test report" is the stuff they write at the bottom of each test procedure,
and the "testing summary" is the compilation of all of their test reports.
The group I'm consulting with now is writing "post-y2k" tests and I'm about to
call a meeting just to clarify what the heck each of them is talking about when
they use the terms I've defined, above.
Would like your input for these terms, please:
* Test Plan
* Test Procedure
* Test Report
* Test Summary
Thanks for your time with this!
--Kimber
Kimber Hebert Miller
Affiliated Computer Services
Dallas, Texas
214.887.7408
kimber_miller -at- acs-inc -dot- com
