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.
Oh. Given that anything you test will be some form of
"release candidate" subject to change, be sure to secure
agreement (in writing...) from the PTB that this-or-that
testing on an earlier candidate was sufficient, and that
the changes between candidates are deemed sufficient that
you don't need to repeat the entire suite of testing at
each increment of the builds.
Then sanity-check anyway.
> -----Original Message-----
> From: McLauchlan, Kevin
> Sent: Tuesday, August 09, 2011 3:00 PM
> To: Cardimon, Craig; 'techwr-l -at- lists -dot- techwr-l -dot- com'
> Cc: McLauchlan, Kevin
> Subject: RE: Advice on software testing?
> 1) Ensure that you have really extensive, really complete test cases,
> against which to test. Have agreement from the PTB that those test
> cases are the full and complete scope of your testing.
> 2) If you don't have them, make them - before you start any testing -
> and have them approved -- before you start any testing.
> 3) Have complete lists of all platforms (Windows, Unix/Linux, OSX,
> Android...) and all versions of each operating system, on which the
> product must be tested.
> 4) Have agreement in hand (and in writing...) whether virtualized
> environments are OK, or you need real loads of some OS flavors.
> 5) Be prepared to revise/completely-rewrite any of 1)-through-4)
> above... at least you'll have the starting points of agreement as a
> base scope-of-testing that you can adapt as the situation changes.
> 6) Keep ALL correspondence, and write capsule summaries of every phone
> or hallway conversation, sending them out as e-mails to interested
> parties with: "This is what I believe we agreed to .... or .... where
> the conversation rested when we spoke just now."
> In other words, pretty much what you need to remember to do
> techwriting. :-)
> You'll do fine.
> Go forth and break things!
> > -----Original Message-----
> > From: techwr-l-bounces+kevin -dot- mclauchlan=safenet-inc -dot- com -at- lists -dot- techwr-
> > l.com [mailto:techwr-l-bounces+kevin.mclauchlan=safenet-
> > inc -dot- com -at- lists -dot- techwr-l -dot- com] On Behalf Of Cardimon, Craig
> > Sent: Tuesday, August 09, 2011 2:35 PM
> > To: 'techwr-l -at- lists -dot- techwr-l -dot- com'
> > Subject: Advice on software testing?
> > My manager told me I'm going to be adding software testing to my
> > repertoire. Any suggestions for a newbie software tester?
The information contained in this electronic mail transmission
may be privileged and confidential, and therefore, protected
from disclosure. If you have received this communication in
error, please notify us immediately by replying to this
message and deleting it from your computer without copying
or disclosing it.
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-