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:QA Testing From:"Parks, Beverly" <ParksB -at- EMH1 -dot- HQISEC -dot- ARMY -dot- MIL> Date:Mon, 12 Jan 1998 09:16:54 -0700
Gina Hertel [SMTP:Ghertel -at- ALPHA88 -dot- COM] asks:
>>
What exactly is Q & A testing?
What goes into it?
Whose responsibility is it?
What is it for?
What types of questions are asked?
<<
Q&A stands for Quality and Assurance. The answers to your
questions depend on the type of product you want to perform QA testing
on. (Just don't anyone QA that sentence!)
Q&A, or QA, testing usually subjects a product to whatever tests
are necessary to ensure the product meets whatever operational,
construction, and safety requirements and specifications have been set
for it.
QA tests are usually performed by a person or division with that
specific responsibility. The developers of the product should not
perform the QA tests because they are "too close" to it and could easily
overlook something important because of their familiarity with the
product.
QA testing is usually done under strict protocol. Test plans are
written and followed to ensure consistent methods and to provide an
audit trail so that if a failure of some sort is discovered, the tester
knows precisely what steps were performed that lead up to the failure.