[Sigia-l] Re: Need resource for test scripts

[Richard Hill]

[Posted for John Howe <: john at wyriwyg.com > because of formatting problems.
Dick Hill]

>Jarrett Knyal wrote:
>
>I'm looking to revaluate how we put together our test scripts.  Does 
>anyone have a resource that discusses the test script creation 
>process they consider valuable?

Jarrett,

I found this site useful: http://www.softwareqatest.com.  And here's 
a list of issues affecting scriptwriter productivity, from my own 
limited experience in that role:

Issue: functional specification incomplete, not thoroughly vetted and 
proofed (e.g. minor functionality and usability issues "to be 
decided" or unresolved, or confusing language) leads to multiple 
e-mail exchanges, meetings, script revisions.  Resolution: Ascertain 
prior proofing of func. spec., or include proofing in writer's 
assigned tasks.

Issue: Multiple, incomplete or invalid versions of data delivered 
after start leads to script revisions.  Resolution: Don't begin 
writing before final delivery of *all* data--write draft test design 
only.

Issue: Descriptive scope (detail level) of test scripts not specified 
and agreed to at start, leads to script revisions.  Resolution: 
Request explicit (written) statement, or prior example of descriptive 
scope, at start.

Issue: Uncertainty over technical and Web knowledge of testers (re: 
test design and script vocabulary) leads to script revisions. 
Resolution: Request explicit (written) user profile before beginning 
to write, or agree on change request responsibility and procedure.

Issue:  No standard/approved test script template--scriptwriters 
spend time developing different, one-off versions of template. 
Resolution: Request identification of approved script template at 
start, or include template development in writer's assigned tasks.

Issue: Multiple iterations and obsolete versions of project files and 
design comps on project site--confusion over authority files. 
Resolution: Request identification of authority files before 
beginning to write, or agree on change  notification procedure.

Hope all the above helps. 

- John


-- 
John Howe, Web writer and information architect
"What you READ is what you get"
http://www.wyRiwyg.com

------------
Richard Hill
Executive Director
American Society for Information Science and Technology
1320 Fenwick Lane, Silver Spring, MD  20910 
FAX: (301) 495-0810
Voice: (301) 495-0900
www.asis.org