PRJD-TMPL-006 Test Plan Template

7/29/2019 PRJD-TMPL-006 Test Plan Template

http://slidepdf.com/reader/full/prjd-tmpl-006-test-plan-template 1/14

TEMPLATE

Test Plan

TEMPLATE

Owner: Applications Testing & Deployment Job Family

How to use this template:

• When using this template, delete the pages marked with “Delete This Page”, they contain thedocument control of the templates and instructions only.

• Complete information required on the cover sheet of the document.

• Construct the appropriate filename for the document (refer to the Manage DocumentConfiguration Procedure) and then save the file.

• Update the Change History table on the front sheet.

• Within the “File > Properties” enter in the document version number (e.g. “1”) into the Keywordsfield and then update the Comments field to designate the document as either “Draft” or “Approved”.

• Ensure that the fields updated via the “File > Properties” are refreshed within the footer (this canbe done by right clicking the field and selecting Update Field or by viewing the document in PrintPreview).

• Ensure the centre section of the footer contains the correct Information Security classification(e.g. “INTERNAL” - see the Information Security Policy for options).

• Consider using the “Track Changes” functionality before sending the document for a review.

• After the document has been reviewed and approved, ensure the master copy is checked in tothe appropriate document management system.

134328634.doc INTERNAL V07.02 Released of 14



TEMPLATE

Change History

Version Issued Details of Change CR No. Author

V01.00 01-Oct-2007 Initial version CR0000 Dominik Kaminski

Anand Chockaiah

V02.00 14-Dec-2007 New RACI table added CR0021 Dominik Kaminski

V03.00 18-Feb-2008 -Updated to reflect correct Job Family owner of Template

-New footer format added to supportConfiguration Management Standards

-General style, format and cosmetic changes

CR0532

CR0565

CR0566

Kay McCormick,Dominik Kaminski

V04.00 31-Mar-2008 -Addition of Test Milestones section

-Amendment of document formatting

CR0278

CR0529

Justin Denning

V05.00 30-Jun-2008 -Addition of sections and supporting text toaccommodate Business Change needs

-Deliverables Review Criteria added

CR0201

CR0845

Jeremy Higginson

Julian Lobley

V06.00 14-Jul-2008 - Section 8.3 Testing Milestones, includedreference to Unit / Link Testing by adding tomilestones table.

- Updated Template cover pages and footersin line with Configuration ManagementStandards

- Change History moved to the front pages

CR1055 Kay McCormick

V07.00 01-Dec-2008 - Section 6.4 KPIs removed (moved to Test Approach Template)

-Section 4.1, reference to OpCo Test Manager

removed

CR0922

CR1447

Justin Denning

V07.01 30-Mar-2009 - Reference changed from MPC Procedure to‘Manage Document Configuration Procedure’

- Added guidance to the cover page

CR1648 Dominik Kaminski

V07.02 21-Sep-2009 - Generic review criteria amendment CR1272 Dominik Kaminski

134328634.doc INTERNAL V07.02 Released of 14



Test Plan

<Project ID> - <Project Name> - <Test Phase>

Change History

Version Issued Details of Change CR No. Author

V1 <dd-mmm-yyyy>

134328634.doc INTERNAL V1 Draft of 14



Table of Contents

1 Introduction and Project Outline ...................................................................................5

1.1 Document Purpose ................................................................................................................51.2 Project Background ................................................................................................................5

2 Scope 62.1 In Scope ................................................................................................................................62.2 Out of Scope ..........................................................................................................................62.3 Risk Based Matrix ..................................................................................................................6

3 Test Deliverables ............................................................................................................ 7

4 Resources ........................................................................................................................8

4.1 Roles and Responsibilities .....................................................................................................84.2 Test Team Structure ..............................................................................................................84.3 Staffing and Training Needs ...................................................................................................8

5 Environment Preparation ...............................................................................................9

5.1 Environmental Needs .............................................................................................................95.2 Test Data Requirements ........................................................................................................9

6 Test Attributes ...............................................................................................................10

6.1 Test Tools ............................................................................................................................106.2 Test Preparation ..................................................................................................................106.3 Test Execution .....................................................................................................................106.4 Test Automation ...................................................................................................................106.5 Entry Criteria ........................................................................................................................106.6 Exit Criteria .........................................................................................................................10

7 Data / Code Conversion ..............................................................................................11

8 Additional Information ..................................................................................................12

8.1 Risks, Issues and Dependencies .........................................................................................128.2 Assumptions ........................................................................................................................128.3 Testing Milestones ...............................................................................................................12




1 Introduction and Project Outline

1.1 Document Purpose<This section should outline the purpose of this document and the standards, both legislative and company

wide that we are looking to comply to.>The purpose of this document is to define the test plan for the <test phase> of <project name>. Thisdocument will detail the scope, schedule, resource plan, environment details and artefacts relevant to theparticular phase of testing. Unless stated otherwise, each section defined in the document will align to theTesting Standards.

<Include the list of documents referred (PID / Test Approach / BSD / Requirements Definition [L3] etc) in the‘Document Particulars’ section, including the version number and location of the document.>

The following are the list of documents that have been referred during the preparation of this document.

Document Version Location

<Insert text> <Provide hyperlink to the location of the document>

<insert additional text>

1.2 Project Background<A project summary usually taken from the PID. Expand on this as necessary.>

<Insert text>




2 Scope

<Define the scope of the test phase – with the details of applications, business functionalities being tested. If there are any specific functionality / application which might be believed to be under the scope of testing but is not needs to be explicitly mentioned in the scope as not covered.>

<Insert text>

2.1 In Scope<This section should discuss about the applications in scope of testing. Based on the test phase, theapplication details can change. For system test, different components under an application should be listed.For Integrated System test, different applications that form a part of the solution should be listed. For User acceptance testing, different business process / departments that use the solution should be listed. >

The following are the list of test items under the scope of testing.

• <list item 01>

• <list item 02>

<insert additional text>

2.2 Out of Scope<This section should discuss about the application / functionality that is not in scope of testing. For each of the application / functionality out of scope of testing, mention appropriate reason for exclusion. >

<Insert text>

2.3 Risk Based Matrix<Include discussion on Risk based testing and risk matrix – highlighting areas of critical businessfunctionalities and technical complexities. Indicate the comparative risk associated with each of thecomponent / functionality / application listed in the section ‘In Scope’. This will serve as an input to the test analyst to define the test cases with the right level of detail and coverage.>

<Insert text>




3 Test Deliverables

<Provide a plan of list of deliverables that will be produced as part of testing and the physical location of thedeliverables.

Note: The following list should reflect in the Deliverables Plan (available in PID) and the PID should be

updated for any change in the deliverables plan. The tabular column specified below reflects a snapshot of information during the Solution Definition stage of CPLC.>

Deliverable

Physical Location

Planned Date

Author

Reviewers

Approvers

<The deliverables include test specification, test closure report and any other related documents. If sign-off is not required for any of the deliverable (ex: Test schedule), specify that sign-off will not be required and specify appropriate reason for the same.>




4 Resources

4.1 Roles and Responsibilities<Specify the roles involved and for responsibilities in this section. The generic responsibilities for different

roles will be listed in the Testing Standards document. So, specify the roles involved and reference theTesting Standards document for responsibilities and list only the significant variances in the responsibilities.>

The section discusses the different roles and responsibilities involved.

Role Name Responsibilities

IT Project Management <Reference Testing Standards and specify theresponsibilities that are not part of standard responsibilities.>

<Insert Text>

Business ChangeManager

Test Manager

Test Lead

Test Analyst(s)

Add other roles

<Classify the testing efforts based on functionality / application / business areas (as required) and identify single point of contact / backup for communication purposes. The information can be presented in the tableabove by specifying responsibility as ‘Main / Backup’ point of contact within the area. This helps in smoother functioning of the projects. If resources are will be from multiple locations, specify the coordinationresponsibilities as well.>

<insert text>

4.2 Test Team Structure<Provide details of the Test Team structure, in the form of a table or an organisation chart.>

<insert text>

4.3 Staffing and Training Needs<Specify the staffing requirements for the test phase and indicate any significant ramp-up / ramp-down of resources. Also, if the resources will be from different locations (onsite/offshore) / business departments,indicate the number of resources required from each department / location. Where applicable, consider the

lead time that will be required to move resources onsite, recruit contractors or 3rd party offshore testers. Thiswill contribute towards the project planning activities. State explicitly any assumptions made during the planning of resources in Section 8.>

Department /

Location

Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec

<List the training needs for the testing team. Training needs include product training / application training / testing training / test tool training. The training needs will also be reflected in the PID.>

<insert text>




5 Environment Preparation

5.1 Environmental Needs<Specify the environmental requirements in discussion with the environments manager in this section. The

environmental requirements should include the applications under scope of testing, interfaces acrossapplications etc.>

<Insert text>

5.2 Test Data Requirements<Specify the test data requirements for the applications involved. In case only sample set of data will beavailable in the environment, list out the specific data requirements.>

<Insert text>




6 Test Attributes

6.1 Test Tools<Specify the test tools used within the test phase. In case of any deviation in the usage of the standard

testing tools defined in the Testing Standards, the details of the deviation and the rationale behind thedeviation should be discussed>.

The section discusses the different tools used within the phase of testing.

• <Quality Centre – for Test Management>

6.2 Test Preparation<Specify the attributes of the test cases, indicating the following:

• Test specification –Test Management Tool will be used to document the test specification. Specify where within the tool the test cases will be available.

• Specify the document / requirements details that will be used as the basis to define test conditions /

cases / scripts

• Specify how the traceability matrix will be established, mapping requirements to test cases >

6.3 Test Execution<Specify the attributes of the test execution, indicating the following:

• Test cycles – identify the number of cycles to be performed in this phase of testing.

• Test location – identify the location(s) in which the testing will take place.

• Test log – Test management tool will be used to document the test execution details (like actual results, tester details etc)

• Defect management – if there are any significant variations in following the defect management procedure specified in the Testing Standards document, indicate the changes

• Defect attributes – Reference the Testing Standards document for standard defect attributes likeSeverity / Priority etc. >

6.4 Test Automation<Specify the scope for test automation. Test automation needs to be considered taking into considerationthe following aspects

• Reusability within the project – multiple cycles of testing

• Reusability in future releases

• Repeatable nature of test cases – same screens with different test data

• Execution time schedule>

6.5 Entry Criteria<This section needs to provide the entry criteria for the test phase.>

<Insert text>

6.6 Exit Criteria<This section needs to provide the exit criteria for the test phase.>

<Insert text>




7 Data / Code Conversion

<If the project contains an element of data/code conversion, include details on the test coverage for Data / Code conversion. This is a SOX Requirement. If there is no element of Data / Code Conversion make astatement to that effect >

<Insert text>




8 Additional Information

8.1 Risks, Issues and Dependencies<State all the risks identified and the mitigation steps (if any). The information can be documented in the

following tabular format. These risks, issues and dependencies should be given as input to the project Risks,issues and Dependencies (associated to the Identify Risks, Issues and Dependencies procedure). Thissection captures the snapshot of risks, issues and dependencies.>

Risk ID Risk / Issue /

Dependency

Impact Mitigation Owner

<Inserttext>

<Insert text> <Insert ext> <Insert text> <Insert text>

8.2 Assumptions<State all the assumptions made during the definition of the document.>

<Insert text>

8.3 Testing Milestones<Include details of all known Testing Milestones. Example milestone listed below are indicative only and will require tailoring to each specific project. If key dates, such as UAT Start, are unknown this should be stated,rather than no reference made.>

Milestone Date

Unit / Link Testing StartUnit Link Testing End

Test Specification Start

Test Specification End

Test Specification Sign Off

IST Start

IST End

IST Sign Off

UAT Start

UST End

UAT Sign Off




Document Particulars

Review & Sign Off As part of the review and sign off process, it is important to refer to the following criteria to ensure that thedocument is fit for purpose. There are two types of review criteria:

• Generic criteria – which can apply to any document

• Specific criteria – that assess specific areas within a particular type of document.

Generic Criteria

The Generic criteria that must be used when considering deliverables are:

1. Has each section of the document been addressed to the expected level?

2. Could this deliverable, in its current state, be used as an input into a subsequent document or subsequent activity?

e.g. If you are reviewing a Requirements Definition Document, is it of sufficient quality to be used as aninput into the Business System Design?

Specific Criteria

For this deliverable, the following specific criteria should be applied to the review:

1. Does the Test Plan reference the inputs used for its creation, including the Testing Standards currentlyin force?

2. Is the scope of testing clearly defined, including the applications and business functions deemed to bein scope of testing?

3. Are applications and functionality which are out of scope explicitly described?

4. Have risk based testing considerations been documented?

5. Have the deliverables which will be produced as part of testing been documented?

6. Have Roles and Responsibilities in relation to testing been described and have resource considerationsbeen addressed?

7. Are Environment and Data requirements adequately addressed?

8. Have a description of the Test Tools to be used and details of Test Preparation and Execution beenprovided?

9. Are the Entry and Exit criteria for the test phase described and are they appropriate?

10. Have Data/Code conversion requirements been considered?

11. Are Assumptions, Risks, Issues and Dependencies associated with the test phase addressed?

The following review table applies to each baselined version of the document.

Approvers (Accountable)

Sign Off

Authors (Responsible)

Contribution




Reviewers (Consulted)

Level of Review / Criteria

Distribution (Informed)

Reference[1] <Author>, <Title>, <Publisher>, <Year>

[2] <Title>, <URL>

Glossary and AcronymsFor Glossary and Acronyms, refer to ARK.

Derived from Template: PRJD-TMPL-006 Test Plan Template V07.02

Document Storage Location: <TBD>

134328634.doc INTERNAL V1 Draft

PRJD-TMPL-006 Test Plan Template

Documents

Transcript of PRJD-TMPL-006 Test Plan Template