DOCX

Test Plan

By Clyde Thomas,2014-03-22 11:02
10 views 0
Test Plan

<CLIENT NAME>

    <PROJECT NAME>

    <DOCUMENT NAME>

    <Client Name>

    <Project Name>

    Test Plan

    Author: <details>

    Tracker #: <details>

    Version: <details>

    Date: <date>

Proprietary Statement:

    ? 2011

    All rights reserved.

REVISION HISTORY

    <client name> <project name> - <project job number> <document name> - Page 1 of 6

<CLIENT NAME>

    <PROJECT NAME>

    <DOCUMENT NAME>

Date of this revision:

    Date of next revision:

    Previous revision Summary of Changes Revision

    date Changes marked date

APPROVALS

    This document requires the following approvals.

    Name Signature Title Date of Issue Version

DISTRIBUTION

    Identify all parties who are on the documents distributed list.

    Name Title Date of Issue Version

    <client name> <project name> - <project job number> <document name> - Page 2 of 6

<CLIENT NAME>

    <PROJECT NAME>

    <DOCUMENT NAME>

1 Table of Contents

    2 Test Plan ........................................................................................ 4 2.1 Overview ................................................................................................. 4 2.2 Research Scope ........................................................................................ 4

    2.2.1 Feature / Change / Addition scope ........................................................ 4

    2.2.2 Research Goals ................................................................................... 4 2.3 Methodology............................................................................................. 4

    2.3.1 Users ................................................................................................ 4

    2.3.2 Materials ............................................................................................ 4

    2.3.3 Setting .............................................................................................. 5 2.4 User Task List ........................................................................................... 5

    2.4.1 Tasks for Existing Users. ...................................................................... 5

    2.4.2 Tasks for New Users. ........................................................................... 5 2.5 Test scripts .............................................................................................. 5 2.6 Release plan / document ............................................................................ 5 3 Approvals ....................................................................................... 6

    <client name> <project name> - <project job number> <document name> - Page 3 of 6

<CLIENT NAME>

    <PROJECT NAME>

    <DOCUMENT NAME>

2 TEST PLAN

    2.1 OVERVIEW

    States the purpose of the document, for example; This document sets out the test plan that will be used to determine the level of acceptance and understanding of the “xxxx”

    feature/ change / addition to be introduced on the site.

    2.2 RESEARCH SCOPE

    This section should clearly state the focus and goals of the testing to be undertaken. It should also clearly state what is and is not in scope for a particular test since many of the features on the site are affected by many others.

    2.2.1 FEATURE / CHANGE / ADDITION SCOPE

    ; Sets out a list of the main questions or goals of the test

    ; Lists the type of things that are to be questioned and tested in the test.

    2.2.2 RESEARCH GOALS

    Sets out the research goals for the test and the understanding which already existed, pre-test, about what the users and business wanted form the particular feature/ change / addition etc on the site.

    Also a clear list of the goals the research hopes to accomplish. For example:

    This test is being carried out to gain an understanding of how current and prospective users will react to, learn and use the proposed xxxx feature. Specifically the test hopes to uncover.

The following areas will be explored:

    ; The test will determine ...

    ; The test will gauge the level …

    ; Findings will give insight into …

    2.3 METHODOLOGY

    This section outlines the methodology for the testing.

    2.3.1 USERS

     Users, who, how many, age, computer experience, fetish interests, education,

    professional back ground etc.

    2.3.2 MATERIALS

    <client name> <project name> - <project job number> <document name> - Page 4 of 6

<CLIENT NAME>

    <PROJECT NAME>

    <DOCUMENT NAME>

    This should say what is being used to conduct the test. This includes specifics about whether this is done on the site vs. prototype vs. wire frames etc. Any equipment needed to capture output of the test, video, audio, assistant to take notes etc.

    2.3.3 SETTING

    This section explains what setting of the tests. This is particularly important in the testing is to take place off site, for example in users homes.

2.4 USER TASK LIST

    This section outlines the tasks the users will be asked to perform and generally states why each task was chosen.

    This section should also state any tasks or sections / features of the site that are not being tested in the session described in this document.

    2.4.1 TASKS FOR EXISTING USERS.

    ; This is the list of tasks that Existing users will perform during the test.

    ; There may not always be a clear break between new and existing users but

    that is the most common split.

    2.4.2 TASKS FOR NEW USERS.

    ; This section lists the tasks to be performed by new users.

    ; There will not always be a clear break between user groups but this is an

    example of one of the most common separations.

    2.5 TEST SCRIPTS

    2.6 RELEASE PLAN / DOCUMENT

    <client name> <project name> - <project job number> <document name> - Page 5 of 6

<CLIENT NAME>

    <PROJECT NAME>

    <DOCUMENT NAME>

3 APPROVALS

INTERNAL APPROVALS

    CSM / Project Owner : Date: Regional Group Director : Date: Project Sponsor Manager: _ __ Date: Client Team Member : _ __ Date:

CLIENT APPROVALS

Work cannot begin until authorization has been received from PM and Sponsors:

    Authorization Sys Team Authorization <Sponsoring Organisation>

By: By:

    __________________________________ __________________________________

Name: <NAME> Name: <NAME>

Title: <Title> Title: <Title>

Address: <Address> Address: <Address>

    FAX: <(XXX) XXX-XXXX> FAX: <(XXX) XXX-XXXX>

Date: Date:

    ________________________________ ________________________________

    <client name> <project name> - <project job number> <document name> - Page 6 of 6

Report this document

For any questions or suggestions please email
cust-service@docsford.com