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 actually like being part of the testing process when I can do it my way.
One time and one time only, I participated in the official "test run" of a
software. We sat and clicked on the same series of buttons over and
over and over and over. Luckily, they only required two hour shifts. If I
would have had to do it any longer, I think I would have screamed.
I can understand why the original poster was frustrated if that is what he
was
up against.
Melonie R. Holliman
Technical Writer
CPD Marketing
Advanced Micro Devices
> -----Original Message-----
> From: Leona Dupree [SMTP:llmdupree -at- YAHOO -dot- COM]
> Sent: Friday, May 21, 1999 1:31 PM
> To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
> Subject: Usability Testing
>
> I never hand over my documentation without testing it against the
> product. I don't mind testing what I have written because I want to
> make sure it works according to what the software does. Why would any
> Technical Writer have a problem with this being a part of the writing
> process, if there are no QA personnel on board?
> ===
> Sincerely,
> Leona L. Magee-Dupree
>
>
> Have a nice day!
>
> _____________________________________________________________
> Do You Yahoo!?
> Free instant messaging and more at http://messenger.yahoo.com
>
>
> From ??? -at- ??? Sun Jan 00 00:00:00 0000=
> =
>
