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:System Testing and TWs From:Anthony Markatos <tonymar -at- HOTMAIL -dot- COM> Date:Thu, 5 Feb 1998 12:02:53 PST
Question to all Technical Writers:
Do software TWs often get involved in system level testing. More
specifically, do they create outputs such as test plans, system level
test cases, and test scripts (i.e., test procedures).
I have read that the end user manual is often the major input into the
system level testing process. It would seem logical that the TW (the
developer of the end user manual) would be a major resource in this
I have significant experience (as a TW) developing system level test
outputs. The results have been vary favorable. However, I have not
heard of any other TW being involved in a formal test planning process.
I am developing a self marketing plan and am wondering what the
marketability is for a Technical Writer with such skills.