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: Advice on software testing? From:"Dana Worley (MVP/JB)" <dana -at- campbellsci -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Fri, 12 Aug 2011 13:14:31 -0600
Dan Goldstein wrote:
/Not sure what "position" can a tester have on a bug, other than, "The
bug exists, and here are the ramifications." /
I would surmise that you've never tested software, or worked with anyone
who is passionate about testing software!
As Peter said, as a tester I may turn in a bug that the engineer or the
"bug vetter" deems is not an issue. If I care about the quality of work
I am doing, and the quality of the product that will eventually be
shipped out, then I may very well take issue with my bug being rejected.
As with most things in life, you have use good judgement on when to
stand your ground and when to walk away.
FWIW, when we get close to a release, I sit down with every one of my
testers and ask them whether or not they feel a product is ready to
ship, or how close the product feels to being stable. These folks are
working with the software day in and day out, and have a pretty good
idea whether or not we should be comfortable shipping. In one of the
classes I took, the instructor said that in one company she worked with,
the testers would draw on the board each day how they were "feeling"
about the stability of the software -- smiley face, sad face, angry
face, etc. :-) We haven't done that, but I do rely on their input along
with risk analysis, market demands, and commitments when making a
decision on when to ship.
Dana W.
--
*************************************
Campbell Scientific, Inc.
Marketing Software Product Manager
*************************************
Microsoft Help MVP 2002-2011
*************************************
Jester's Baubles Fused Glass Designs http://www.jestersbaubles.com http://jestersbaubles.blogspot.com
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com