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:Writing vs. Testing From:Fred Sampson <wfreds -at- CRUZIO -dot- COM> Date:Fri, 21 May 1999 09:54:37 -0700
Greetings--
Although I have years of writing and editing experience, I'm new to tech
writing, and still feeling my way into the profession.
At my first official technical writing job, I was to write online help for
accounting software written in FoxPro 2.6. However, for four of my seven
weeks on the job, I was asked to alpha-test the latest module. Originally,
support techs were supposed to do the tests, but weren't as "up to speed"
as I was. I received little direction--one test script, one set of sample
data, and was told to keep doing it over and over, and report the bugs.
When I mentioned that I found this monotonous testing mind-numbing, I was
shown the door.
So, my question is: Can a technical writer (especially a newbie) reasonably
expect to perform alpha-testing assignments? I understand the need to learn
the new software by using it, which can include testing, but is this the
major part of the tech writer's job?
I'll appreciate any comments you folks might have on this.
