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: QA testing From:Kris Olberg <kjolberg -at- IX -dot- NETCOM -dot- COM> Date:Mon, 12 Jan 1998 11:22:17 -0600
-----Original Message-----
From: Gina Hertel <Ghertel -at- ALPHA88 -dot- COM>
To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU <TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU>
Date: Monday, January 12, 1998 10:37 AM
>The Technical Writer will be responsible for interviewing SMEs (subject
>matter experts) and conducting QA testing for the product...
Are you really going to do the QA? QA is a discipline that CAN be performed
by technical writers if they have the required skills. However, few do.
Do you know the methodologies of QA testing? Do you know the difference
between unit, integration, system, and user acceptance testing? Can you
write test plans for each type? Do you have the technical skills to verify
movement of data through the system? (You cannot use the client to test the
client. You will probably have to create or manually perform database
queries, view sniffer logs, etc. to verify the data reported by the client
is accurate.)
I'd highly suggest discussing this with your development area to clarify
your role.
Regards...Kris
------------------------------
kolberg -at- actamed -dot- com
kris -at- olberg -dot- com
