Docstoc

Project Master Test Plan

Document Sample
Project Master Test Plan Powered By Docstoc
					Projects Office
Tari Kaupapa




                     Project Name
                  Master Test Plan
                                                                                                     Project Name
                                                                                            Master Test Plan - Draft



Table of Contents
  1    INTRODUCTION .....................................................................................3
       1.1 Purpose ...........................................................................................3
       1.2 Audience .........................................................................................3
       1.3 Associated documents .....................................................................3
  2    VERSION CONTROL ..............................................................................3
  3    OVERVIEW.............................................................................................4
       3.1 Project Objectives ............................................................................4
       3.2 System Description ..........................................................................4
       3.3 Plan Objectives ................................................................................4
       3.4 Outstanding Issues, Assumptions, Risk and Contingencies................4
  4    BUSINESS REQUIREMENTS TO BE TESTED........................................4
  5    PREREQUISITES ...................................................................................5
       5.1 Test Data .........................................................................................5
       5.2 Hardware .........................................................................................5
       5.3 Software ..........................................................................................5
       5.4 Location...........................................................................................5
       5.5 Staffing and Training ........................................................................5
  6    TEST SCOPE .........................................................................................6
       6.1 Requirements to be Tested ..............................................................6
       6.2 Features not to be Tested.................................................................6
       6.3 Security testing ................................................................................6
       6.4 Process testing ................................................................................6
       6.5 Data conversion testing ....................................................................7
       6.6 Extended scenario testing ................................................................7
       6.7 Transition.........................................................................................7
  7    PROPOSED SCHEDULE ........................................................................8
  8    RESOURCES .........................................................................................8
  9    SUSPENSION CRITERIA........................................................................8
  10   BUSINESS OWNER SIGNOFF................................................................8




  Version: a                                    Page ii
  Date: 7 February 2005
                                                                        Project Name
                                                               Master Test Plan - Draft

1 Introduction
1.1 Purpose
        This document describes the testing procedures/overview for quality testing
         for the newly created <insert description>.

1.2 Audience
  Project Manager, Business Analysts, Business Owners, ITS

1.3 Associated documents
  This document should be read in conjunction with the following documents:

        <insert description> requirements documents

2 Version Control
  File Name: Document3

  Date           Status Version      Updated by        Reason for Update
  3/11/04        Draft    a




                                          -3-
                                                                         Project Name
                                                                Master Test Plan - Draft

3 Overview
3.1 Project Objectives
  Establishing a fully integrated student advisement tool set Massey wide.

3.2 System Description
  SPM is an application in the SMS (MAS) system. IT has to major components.

       The Maintenance Interface where academic regulations can be
        maintained.
       The Assessment Interface where students can be assessed against
        selected academic regulations in order to establish progress to
        completion, eligibility to graduate and other nifty functions.
       Interacting with the various processes within the administration of the
        University that are dependent upon the outcomes of assessment and
        advice given to students.

3.3 Plan Objectives
  The objectives of this plan are to;

       Define responsibilities
       Identify the method to be used
       To identify how <insert description> will be tested against the user
        requirements specified in the <enter name> specification to ensure fitness
        for purpose.

       Identify the environment in which testing will occur.

3.4 Outstanding   Issues,                   Assumptions,             Risk         and
    Contingencies


4 Business Requirements to be tested
       <insert description> from the Business Requirements.




                                          -4-
                                                               Project Name
                                                      Master Test Plan - Draft



5 Prerequisites
5.1 Test Data
     The following data must be available prior to this test design being
     implemented:

        

5.2 Hardware


5.3 Software


5.4 Location


5.5 Staffing and Training




                                   -5-
                                                                          Project Name
                                                                 Master Test Plan - Draft

6 Test Scope
6.1 Requirements to be Tested
6.1.1 Requirement 1
   The combination of features to be tested is as follows.

Feature                               Purpose




6.1.2 Requirement 2


Feature                               Purpose




6.2 Features not to be Tested
   The following features are not included:

       

6.3 Security testing
   Check that user characteristics as set up match security.

      Test that user groups are able to access all they are entitled to, and only what
       they are entitled to.
      Physical Test: Log-on and verify security settings.
      Testing has list of users and their security level. Testing to see that users
       belong to correct group and that the group has the correct security.

6.4 Process testing
   All business processes involving the system can be carried out smoothly.

   Testing has:

Process           Assoc        All doc        Process   Result /        Status
name              forms        OK             OK        comment




                                           -6-
                                                                    Project Name
                                                           Master Test Plan - Draft




6.5 Data conversion testing
   All data has been converted correctly from old to new where appropriate



6.6 Extended scenario testing
   Typical scenarios are handled correctly by the system

   Testing includes:



Area       Scenario          Expected         Result/ comment          Status
                             result



6.7 Transition
   Maybe parallel running or cut-over to production and watch. How will this be
   tested?




                                        -7-
                                                                      Project Name
                                                             Master Test Plan - Draft




7 Proposed Schedule
  List of proposed tests and dates

8 Resources
  Who is required for the testing and when.

9 Suspension Criteria
  What conditions will halt testing.




10 Business Owner Signoff


  I have reviewed this document, agree with its content and approve the test plan.




  Signed:    __________________________                  Date: _____/_____/____

             <insert name>, Business Owner




                                        -8-

				
DOCUMENT INFO
Shared By:
Stats:
views:346
posted:1/28/2008
language:English
pages:8
ocak ocak
About