Re: Advice on software testing?

Subject: Re: Advice on software testing?
From: "Peter Neilson" <neilson -at- windstream -dot- net>
To: techwr-l -at- lists -dot- techwr-l -dot- com
Date: Tue, 09 Aug 2011 16:35:51 -0400

Here's a scenario that occasionally happens, and that should underlie any test plan using unusual hardware:

- Tuesday: The sole beta-test version of the custom hardware device promised for Monday is ready for you to begin testing. You've read the specs and the code, and you have a plan. You have two weeks before it gets taken away from you.

- Wednesday: You're revising the test plan to cover the new items you discovered in the hardware and the latest changes to the software.

- Thursday: You begin actual testing, entering bugs into the reporting system.

- Friday: Testing is going well. You report that you might be done well within time frame.

- Monday: You discover that over the weekend the system was shipped out. "We needed to make it billable."

- Tuesday: You try to get your boss to push through to a level of management that can make the decision on what to do.

- Wednesday: The consequences of the decision now belong to you. Whether you have to spend the next two months in Irkutsk, or test remotely over a dial-up connection, or publish a lie that reports no bugs, it's not something you want to own.

How do I know this stuff can happen? Kansas City is not quite Irkutsk, but I'd not planned to be debugging software on a machine sitting on a factory floor. On the other hand, we did discover that the SCR-controlled forklift trucks created electrical noise that crashed the custom device. Nothing in the original specs had anticipated that problem.

On Tue, 09 Aug 2011 15:11:28 -0400, Cardimon, Craig <ccardimon -at- m-s-g -dot- com> wrote:

The guy I'm going to be working with will be contacting me. He's one of the senior support dudes. I work with him when I'm wearing my tech writer hat.

-----Original Message-----
From: Bill Swallow [mailto:techcommdood -at- gmail -dot- com]
Sent: Tuesday, August 09, 2011 3:10 PM
To: Cardimon, Craig
Cc: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Re: Advice on software testing?

Do you have a testing/QA group where you work? If so and you'll be
joining, talk to them. Otherwise many good suggestions made so far.
But collaborate with development, and never test without a plan.

On Tue, Aug 9, 2011 at 2:35 PM, Cardimon, Craig <ccardimon -at- m-s-g -dot- com> wrote:
My manager told me I'm going to be adding software testing to my repertoire. Any suggestions for a newbie software tester?

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.

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Please move off-topic discussions to the Chat list, at:


Advice on software testing?: From: Cardimon, Craig
Re: Advice on software testing?: From: Bill Swallow
RE: Advice on software testing?: From: Cardimon, Craig

Previous by Author: Re: Wiki for Customer Facing documentation?
Next by Author: Re: Advice on software testing?
Previous by Thread: RE: Advice on software testing?
Next by Thread: RE: Advice on software testing?

What this post helpful? Share it with friends and colleagues:

Sponsored Ads