Re: Test, Test, Test Plans

[Angela Wiens <AWiens -at- PANGAEA -dot- CA>]

Marc,
Here are topics and sub-topics I used in a Master Test Plan.

Introduction
   Purpose
   Background
   In Scope
   Out of Scope
Test Requirements
   Inputs
   Test Technique and Tools
   Tracking and Metrics
   Traceability
Test Types
   Business Function
   User Interface
   Configuration
   Installation
   Performance
   Stress
   Volume
   Migration
   Conversion
   Regression
Test Strategy
   System Test (for your case)
      Description
      Objectives
      Test Points
      Test Types
      Data Volume
      Entry Conditions
      Exit Conditions
   UAT
      (same as System Test)
Responsibilities
   (broken down by Role and Test Stage)
Deliverables
   Detailed Test Plans (the testing scripts)
   Requirements Validation Matrix
   Test Logs
   Defect Tracking Reports (we handled trouble tickets via Perfect Tracker
and had a separate procedures document for that)
Resources
   (checklists and templates)

I hope this help. If you have any question, please send me an e-mail (see
address below).

Angela Wiens
Pangaea Systems Inc.
2200 Canada Trust Tower
10104 - 103 Avenue
Edmonton, AB  T5J OH8
(403) 426-3510
awiens -at- pangaea -dot- ca

Visit our website at: http://www.pangaea.ca


-----Original Message-----
From: Marc Lederman [mailto:marclederman -at- HOTMAIL -dot- COM]
Sent: January 12, 1999 7:55 AM
To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Subject: Test, Test, Test Plans


Good morning one and all,

I am writing to ask for some assistance on test plan development.  I am
working on a set of test plans for a client that will include a system
test plan and a user acceptance test plan (UAT).  The system is a
web-based tool developed in Javascript with a SQL database backend.  To
date, the requirements statement is not available and neither is the
system (it's still in development, promised a week ago).

So far I've developed a template and inserted an overall plan to
proceed, written some definitions, provided general acceptance criteria,
etc., etc.  Hopefully the requirements will appear, but until then, has
anyone a good idea on what needs to go into a system test plan and a
user acceptance test plan?  What about objectives and conditions,
procedures, and the ever popular trouble ticketing process?

Your help is greatly appreciated.

Thanks,

Marc


______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com


 From ??? -at- ??? Sun Jan 00 00:00:00 0000=


 From ??? -at- ??? Sun Jan 00 00:00:00 0000=