General template for Test Plan

minceillusionInternet and Web Development

Jul 30, 2012 (4 years and 4 months ago)

299 views

















Test Plan

<Integration name>
.
<
Service

name>

(Ex. RSD002.Kontakt)


Version:

1.0

Date 200
8
-
0
6
-
20




Project:

Baseline

Version: 1.0

Document:

minceillusion_4d22a125
-
6dd9
-
4370
-
948f
-
8ab375d5acd4.doc

Date:

2006
-
02
-
24


2

(
8
)

Table of Contents


1

INTRODUCTION

................................
................................
................................
................................
........

3

1.1

P
URPOSE

................................
................................
................................
................................
..................

3

1.2

A
UDIENCE

................................
................................
................................
................................
...............

3

1.3

V
ERSION HISTORY

................................
................................
................................
................................
...

3

1
.4

R
EFERENCE DOCUMENTS

................................
................................
................................
.........................

3

1.5

A
BBREVIATIONS

................................
................................
................................
................................
......

3

2

ROLES

................................
................................
................................
................................
...........................

4

3

INTEGRA
TION SPECIFIC INFORM
ATION

................................
................................
..........................

5

3.1

S
COPE

................................
................................
................................
................................
......................

5

3.2

R
EQUIREMENTS FOR
T
EST

................................
................................
................................
.......................

6

3.3

T
EST PLAN

................................
................................
................................
................................
...............

7

4

CLOSING OF THE INTEG
RATION

................................
................................
................................
........

8

4.1

D
EFECT REPORTS

................................
................................
................................
................................
.....

8

4.2

T
EST RESULT REPORTING

................................
................................
................................
.........................

8


Project:

Baseline

Version: 1.0

Document:

minceillusion_4d22a125
-
6dd9
-
4370
-
948f
-
8ab375d5acd4.doc

Date:

2006
-
02
-
24


3

(
8
)

1

Introduction

<Template note: All

italicized,

blue
text in

brackets
is template instructions and should be deleted
when filling in the template>

<All text in brackets should be substitute
d with relevant content>

1.1

Purpose

The purpose of this test plan is to verify that message transfer and mapping
functionality is

carried out
in compliance with

agreed functionality according to
specifications.
This document is valid for one specific
I
ntegrat
ion
or Service
.

The purpose is also to communicate the intent of the testing activities.

1.2

Audience

Test
Manager
, Integration Tester, Integration Developer, Project Manager

1.3

Version history


Version

Date

Description/comments

Responsible

1.0




1.4


Reference
documents


Document name

Issued by

Baseline Testprotocol


RS䐰〲⹋潮瑡歴⹤Dc


䉡獥汩ne⁉ 瑥杲慴楯a
Spe捩f楣慴楯a


RS䐰〲⹋潮瑡歴


䉡獥汩ne⁉ 瑥杲慴楯a⁉浰汥浥n瑡瑩潮


RS䐰〲⹋潮瑡歴



1.5

Abbreviations

<List any relevant abbreviations with an explanatio
n>

<IP

Integration platform>

<PoD

Point of delivery>

Project:

Baseline

Version: 1.0

Document:

minceillusion_4d22a125
-
6dd9
-
4370
-
948f
-
8ab375d5acd4.doc

Date:

2006
-
02
-
24


4

(
8
)

2

Roles

This section presents the recommended resources for the test effort, their main
responsibilities, and their knowledge or skill set.

Worker

Name


Specific Responsibilities/Comments

Test Manager

<Firstname
Lastname
,
Company>

Provides management oversight

Responsibilities:



Provide technical direction



Acquire appropriate resources



Management reporting



Generate test plan



Report Change Requests



Analyse
and assign
error
s

found
during

the
test

phase



Ev
aluate effectiveness of test
effort

Integration
Tester

<
Firstname
Lastname
,
Company
>

Designs and e
xecutes the tests

Responsibilities:



Generate test
cases and test data



Execute tests



Log results

and store test files



Document change requests

Integration
De
veloper

<
Firstname
Lastname
,
Company
>

Implements and unit tests the classes
,
adapters, message flows, transformations

and packages

Responsibilities:



Acquire test files



Create

the classes and packages
implemented in the model


Project:

Baseline

Version: 1.0

Document:

minceillusion_4d22a125
-
6dd9
-
4370
-
948f
-
8ab375d5acd4.doc

Date:

2006
-
02
-
24


5

(
8
)

3

Integration specific informat
ion

3.1

Scope


Reference to
specifications

Baseline Integration Specification


RSD002.Kontakt

Baseline Integration Implementation


RSD002.Kontakt

Integration Units that
should be tested


MQ Series


WBIMB
/WMB


ICS


Adapter …….


WDI


TPI


WPG


WAS


WPS


WSF


Other: …………

Types of test that should

be exec
uted


U
nit

Test
Contracts


U
nit

Test
Services


Integration Test End to End


Message size Test


Performance Test


Acceptance Test


System Regression Test


<Other>

Risk factor/description

<Where is the highest risk of failure? Where is the most advanced logic
applied? Where are the bottlenecks?>


Project:

Baseline

Version: 1.0

Document:

minceillusion_4d22a125
-
6dd9
-
4370
-
948f
-
8ab375d5acd4.doc

Date:

2006
-
02
-
24


6

(
8
)

3.2

Requirements for Test

The listing below identifies those item
s (functional requirements,
test tools
) that have
been identified as targets for testing. This list represents what will be
used during the
test
s
.

<Enter a high level list of the major requirements for test
>

Item

Usage

<IBM Websphere MQ Explorer>

<
Mana
ge files on MQ
>

<Queue Browser / RFH Util or equal>

<
Manage files on MQ
>

<Testline>

<
Execute Unit tests on the
WMB

platform
>

<IBM Websphere
Message Broker Toolkit
>

<
Execute Unit tests on the
WMB

platform
>

<IBM Websphere ICS


System Manager>

<
Execute U
nit tests on the ICS
platform
>

<File/text editor>

<
Update or view conte
nt

of test
files
>

<Terminal Services Client>

<
To access the test environment
>


System access

Describe t
he systems used during testing, how to access the systems and which IP
-
addresse
s to use.

Project:

Baseline

Version: 1.0

Document:

minceillusion_4d22a125
-
6dd9
-
4370
-
948f
-
8ab375d5acd4.doc

Date:

2006
-
02
-
24


7

(
8
)

3.3

Test plan

Project milestones

Milestone Task

Role

Start Date

End Date

Test files / documents

Customer

representative



Unit tests

Integration Developer




Integration tests

Integration tester



Distribution of
Integration
package

Integration

Developer



QA Environment updated

Support
technician



Acceptance
tests

Customer

representative




Schedule

For smaller
integration
s the Project milestones
are

enough
to

manage the Test planning.
F
or larger and longer projects / integrations
,

a schedu
led plan must be created.

The test plan schedule could be migrated into the main project plan or
a separate
schedule for the tests phase could be maintained.

Project:

Baseline

Version: 1.0

Document:

minceillusion_4d22a125
-
6dd9
-
4370
-
948f
-
8ab375d5acd4.doc

Date:

2006
-
02
-
24


8

(
8
)

4

Closing of the integration

4.1

Defect reports

All known errors and not tested cases should be displa
yed and annotated here.

Known errors

Test
case id

Change
request
Id

Description/comments

Date

Responsible












Not tested cases

Test
case id

Not tested because

Date

Responsible










4.2

Test result reporting

The result of the quality verific
ations made in the Test Protocol should be reported here.

Test type

Status

Date

Approved by

<
Unit test Contract A
>




<
Unit test Service 1
>




<
Integration test
>




<
Performance test
>




<
Acceptance test
>