Test plan

Revision A - 22 MARCH 1996

	Name	Position	E-mail address
Author(s):	Jim Håkansson	Test Manager	pt93jha@pt.hk-r.se
Responsible:	Jim Håkansson	Test Manager	pt93jha@pt.hk-r.se
To:	SAIDA	Project	saida@pt.hk-r.se
Cc:

1 Introduction

The Test plan does not describe when different tests are going to be performed, only which tests. The time and date of the tests are described in the Team development plans [SIW][SAGA].

Because we are using evolutionary delivery we must have a system test before each delivery. Before different units are integrated they must be tested separately, this is the unit test. When different units are integrated they must be tested together, this is the integration test.

The outline of a test session is described in the test procedure [QMG].

2 Test categories

A test can be one of the following types:

Unit test
Testing the functionality in the tested unit against the design and the requirements specification.
Integration test
A test to make sure that different units (which has already passed the unit test) work together as planned.
System test
Test an independent part against the system requirements specification. A part can be a collection of integrated units or separate units.

For more information see [QMG 96].

3 Schedule

3.1 Activities

The following activities are needed to perform the test procedure in a proper way.

These activities last during the project:

Study of the test procedure.
Produce the Test plan.
System test specification.
Planning for test sessions.

3.2 Time resource

The solution team has estimated the time needed for the test procedure. The test time is 30-40% of the implementation time.

For more details see the estimation part in the Team development plans. [SIW][SAGA].

3.2.1 Estimations of test management

3.2.1.1 Study of the test procedure

	pages	h/page	h
Test procedure	10	0.5	5
Test plan	2	0.5	1
Test session	2	0.5	1
Test protocol/report	2	0.5	1
Total of needed time			8

3.2.1.2 Produce the Test plan

Average size of a test plan : 5 pages

Constant: 6 h/pages

Needed time: 30 h

3.2.1.3 Planning for test sessions

Number of tests:
9 unit tests
5 integration tetsts
7 system tests

Total: 21 tests, see [3.3], "Tests"

Constant: 2 h/tests

Needed total: 42 h

3.3 Tests

The time and date of the tests are already planned in the Team development plans. [SIW][SAGA]

3.3.1 Unit test

There are going to be at least nine unit tests, see the Team development plans [SIW][SAGA].

One unit test for each of these:

WWW interface
Navigator
Logger
E-Mail
Alarm

Two unit tests for each of these:

Data server
Development environment

The teams makes a unit test specification for these parts.

3.3.2 System test

A system test is done before each evolutionary delivery step, and the test starts at least four work days before the day of delivery. There will be five system tests.

One system test specification shall be made by the teams together.

3.3.3 Integration test

All units are related to the data server and need to be tested against it.

There are going to be seven integration tests, see the Team development plans [SIW][SAGA].

One integration test for each of these:

WWW interface
Navigator
Logger
E-Mail
Alarm

Two integration tests for each of these:

Development environment

4 Test results

After a test session the following shall be delivered to the Team Manager:

Test Specification
Test Report
Test Session protocol
Test Input Data and Output Data

Test tools shall also be included.

5 Environmental needs

We shall have a dedicated computer (Windows NT) to perform all the tests on and also used to perform the delivery on. The computer shall not contain more or less software/hardware than what the installation manual says.

Each test session has its own specification of needed environments.

6 Responsibilities

The SAGA team is responsible for producing the test specifications for the...

... data server
... logger
... E-Mail
... alarm

The SIW team is responsible for producing the test specifications for the...

... WWW interface
... navigator
... development environment

7 Risks and contingencies

The time to write the test session specification can be too high compared to the time spent on testing.

8 Appendix A

8.1 Literature

[SAIDA] SAIDA project, "Project development plan" - University of Karlskrona/Ronneby, 1996.

[SIW] SIW team, "Team development plan" - University of Karlskrona/Ronneby, 1996.

[SAGA] SAGA team, "Team development plan" - University of Karlskrona/Ronneby, 1996.

[QMG] QMG project, "Test procedure" - University of Karlskrona/Ronneby, 1996.

Test plan
1 - Introduction
2 - Test categories
3 - Schedule
3.1 - Activities
3.2 - Time resource
3.2.1 - Estimations of test management
3.2.1.1 - Study of the test procedure
3.2.1.2 - Produce the Test plan
3.2.1.3 - Planning for test sessions
3.3 - Tests
3.3.1 - Unit test
3.3.2 - System test
3.3.3 - Integration test
4 - Test results
5 - Environmental needs
6 - Responsibilities
7 - Risks and contingencies
8 - Appendix A
8.1 - Literature