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:Users' documentaion and QA Teams From:"Mariana Prusorova" <mprusorova -at- hotmail -dot- com> To:techwr-l -at- lists -dot- raycomm -dot- com Date:Thu, 22 Jan 2004 11:36:53 +0000
Hi, Please share some of your experiences with the QA teams, how do you
communicate with them and what is your process . Do you ceate special
testing plans - how the user documentation should be tested?
I think they should test more the usability - whether the needed
information is provided to the user and questions are answered.
By us the situation is that they test my design, alignment, grammar,
anything but the conntent, mostly the form. And fixing bugs about minor html
details waists my precious time, when I could develop more/better content.
Further more the tests are continuouing even when the new release is
already a fact; and commas, spaces etc. have to be patched on the
lifesystem.
