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.
Not sure what "position" can a tester have on a bug, other than, "The
bug exists, and here are the ramifications."
The tester's report should be read by those deciding whether or not the
product can be shipped. But the tester (and the report) can remain
neutral on the decision itself.
From: Dana Worley (MVP/JB)
Sent: Wednesday, August 10, 2011 11:49 AM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Re: Advice on software testing?
... Defend your position on a bug, but also know when to back off
(especially when you get near release). Don't be offended if your bugs
are "next versioned". Think about risk -- how likely is a customer to
run into this issue? What are the ramifications? Is there a work around?
Is it catastrophic? At some point, the software needs to be locked down
(or it will never ship) and all bugs except those that are absolutely
show stoppers will need to be moved to a future release. Understand this
and don't take it personally.
This message contains confidential information intended only for the use of the addressee(s). If you are not the addressee, or the person responsible for delivering it to the addressee, you are hereby notified that reading, disseminating, distributing, copying, electronic storing or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this message by mistake, please notify us, by replying to the sender, and delete the original message immediately thereafter. Thank you.
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
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-