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.
I've been asked to write a Test and Acceptance Plan doc for one of our
products. No clue! Never done this before. (I'm a lone writer, so I get
every writing opportunity that exists around here.) Can anyone who has done
this send me some sketchy guidelines about what goes in such a doc? Also, is
the language more like a functional spec ("The system does this") or a user
guide ("Do this and this").
Tony Markatos responds:
Karen, I have significant experience creating systems level test test cases
(a primary component of a test plan). I also create clear and concise test
procedures. I think I know where the person who gave you this assignment is
coming from. Goes like this: the main input to creating a test plan is
valid requirements specifications; however, since nobody has valid
requriements specs, the end user manual is often used instead.
And, if you wrote the end user manual, who better to write the test plan.
There are many software test related books that outline suggested test plan
contents. Big time guru author -- Glenford (I think that is his first name)
Meyers. Very readable!
Tony Markatos
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
