Template test plan system and acceptance tests



|Template test plan system and acceptance tests |

>

signs).

There is also text between single hooks (). This text contains example elaboration and also needs to be removed or replaced by the definitive text. All other standard text may be adjusted as need fits.

The sub-chapters (chapters en paragraphs) are obligatorily. That means; when a certain aspect is not paid attention to, you have explain this decision.

A template risk assessment is available. If needed this template can be transferred to this release advice.>>

Version information

|Version |Date |Remarks |Author |

| | | | |

| | | | |

Distribution list

|Name |Company/Function |

| | |

| | |

Approval Client

>

|Client: |Signature |

|Name | | |

|Division | | |

|Department | | |

|Function | | |

|Location | | |

|Telephone | | |

|E-Mail address | |Date: |

Management summary

|Project objective |

| |

|Test objective and assignment |

| |

|Short description of the test approach |

| |

|Results to be realized |

|Result |Document |Delivery date |

|< example: well executed and finished system test> |ST Test report | |

|Qualitative objectives |

| |

|Go/no-go decisions |

|< Example: After each test level the test manager makes sure that a test report is drawn up. This report will, after reviewing with |

|the project manager, be presented to the key stakeholders, who decide if it is possible to move to the next test level. |

|At the end of the total test project an end testing report will be drawn up, containing a risk based assessment of the test object. |

|Based on this end report the key stakeholders make the final decision to go to production or not. > |

| |

Table of contents

> II

Version information III

Distribution list IV

Approval Client V

Management summary VI

Table of contents VII

1 Introduction 1

1.1 Goal of the test plan 1

1.2 Assignment 1

1.2.1 Client 1

1.2.2 Supplier 1

1.2.3 Assignment 1

1.2.4 Scope 1

1.2.5 Preconditions and assumptions 1

1.2.6 Acceptants and acceptance criteria 2

2 Documentation 3

2.1 Basis for the test plan 3

2.2 Test basis 3

3 Test strategy 4

3.1 Test strategy 4

4 Approach 6

4.1 Test design table 6

4.2 Description test approach 7

4.2.1 Intake test object 7

4.2.2 7

4.3 Phasing 8

4.4 Entry and exit criteria 8

4.4.1 > 8

4.4.2 > 9

4.4.3 > 9

5 Infrastructure 11

5.1 Test environments 11

5.1.1 System tests 11

5.1.2 Acceptance tests 11

5.2 Office setup 11

6 Management 12

6.1 Test management 12

6.2 Defect procedure 12

7 Estimation & Planning 13

7.1 Estimation 13

7.2 Planning 13

Appendix 1 – Product risK analyseS 15

Introduction

1 Goal of the test plan

>

The goal of this Test Plan (TP) for is to inform all who are involved in the test process about the approach, the activities and the deliverables concerning for . This test plan describes a concrete and detailed elaboration of what has been described in the master test plan [reference] for the .

2 Assignment

1 Client

>

2 Supplier

>

3 Assignment

>

4 Scope

Give a short description of the application and the main changes in the new version (if applicable) as well as the limitations of the system and acceptance tests.

Within scope:

>

Out of scope:

>

5 Preconditions and assumptions

The list below is an example. The test coordinator has to find out for each part which preconditions and assumptions are relevant. For each precondition there has to be agreement with the project manager of the commissioning organization about the expectancy of the project.

The following demands apply to the test process:

>

To make the test process successful the following things need to be arranged:

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

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download