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: Test Scripts/ Test Specifications From:"Cekis, Margaret" <Margaret -at- mediaocean -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 2 Jan 2002 14:36:06 -0500
John Fleming [mailto:johntwrl -at- hotmail -dot- com]asked about " Test Scripts/ Test
Specifications"
"For the first part of the project, I will be working with a set of
incomplete test specifications prepared by others, and will need to ensure
they meet client requirements.... do you have any
suggestions, tips, or warnings?"
__________________________________
John:
Get copies of all of the specs that you can. The more complete and
detailed, the better. This includes not only the general overall high-level
specs, but the nitty-gritty details specified for the user interface (what
happens when a user selects something on a screen? what happens when he
makes an entry, change, or deletion?) and for the data base (what happens in
the database when user does one of the above? and how can a tester confirm
it?) Does the software respond as specified on the UI, in the database, and
on any other form of input/output that can be monitored?
The test specs should cover all these details, and the various tests should
be grouped in such a way that a review of the results will help pinpoint
bugs or problems. For example, a test set should show the UI results,
database results, and I/O results for a given feature. Bad grouping would
link all UI tests, with no connection to the other results for the same
features; and all the database or I/O results without linking them to other
tests of the same events.
Check out all the previously written material against the specs, and make
notes to add more detailed tests to fill in the holes. Then try to organize
the material logically. Good Luck.
Sponsored by eHelp Corporation, makers of RoboHelp - the industry standard
in Help authoring. Download a trial version today or get special savings when
you buy the RoboHelp 2002 Holiday Edition. Visit http://www.ehelp.com/techwr
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
