Template for a test plan

Marc Groenewegen (marcg@dinkum.nl)

May 5 2003

Document Information
Organisation Hogeschool voor de Kunsten Utrecht (HKU)
Project name Signature
Version 0.1
Status draft
Location mediate/signature/doc/db_testplan.xml
Audience Gerard van Wolferen, Hans Timmermans
Abstract:
The abstract gives a short description of the contents of this document. This document describes the tests to be performed on the Signature database in order to approve or disprove that the system performs as stated in the corresponding requirements document.

Table Of Contents

1 Introduction

2 Functional test

3 Integration test

1 Introduction

This test plan consists of two parts, one part describing the functional test and one part describing the integration test. The functional test is restricted to the (sub)system itself. This is also known as a design test. It serves to prove that the (sub)system operates according to the requirements specification. For various interfaces, stubs In the integration test, the (sub)system is validated in its intended context.

2 Functional test

The functional test is restricted to the (sub)system itself. This is also known as a design test. It serves to prove that the (sub)system operates according to the requirements specification. For various interfaces, stubs and test sequences may be used to validate its behaviour.

2.1 Database writes

2.1.1 Prerequisites

Connect the Signature database to a pattern generating stream

2.1.2 The test

Feed the default test stream containing 250 different patterns into the database. Analyse the database and verify the correct storage of all patterns.

2.2 Database reads

2.2.1 Prerequisites

Connect the Signature database to a pattern eating stream. Put 250 patterns from the default test stream into the database.

2.2.2 The test

Perform a pattern read dump on the database and feed the output into a temporary stream. Analyse the stream and verify the correct retrieval of all patterns by comparing the stream with the default test stream.

3 Integration test

In the integration test, the (sub)system is validated in its intended context.

3.1 Database writes

3.1.1 Prerequisites

Connect the Signature database to the Signature analysis system.

3.1.2 The test

Feed a reproducible data stream containing a number of patterns to the input of the Signature analysis system. Analyse the database and verify the correct storage of all patterns.