9.1  Test planning

The test planning details the activities, dependencies, and effort required to 

conduct the test of the converted solution.

9.1.1  Principles of software tests

Keep in mind the principles of software tests in general:

It is not possible to test a non trivial system completely.

Tests are optimizing processes regarding completeness.

Always test against expectations.

Each test must have reachable goals.

Test cases have to contain reachable and non reachable data.

Test cases must be repeatable.

Test cases have to be archived in the configuration management system as 

well as source code and documentation.

9.1.2  Test documentation

The test documentation is a very important part of the project. The 

ANSI/IEEE 

Standard 829 1983 for Software Test Documentation

 describes its content 

exactly. We give you a high level overview here.

Scope

State the purpose of the plan, possibly identifying the level of the plan (master 

etc.). This is essentially the executive summary part of the plan. You may want to 

include any references to other plans, documents, or items that contain 

information relevant to this project and process. If preferable, you can create a 

references section to contain all reference documents.

Identify the scope of the plan in relation to the software project plan that it relates 

to. Other items may include resource and budget constraints, scope of the testing 

effort, how testing relates to other evaluation activities (analysis and reviews), 

the process to be used for change control and communication, and coordination 

of key activities.

As this is the

executive summary

, 

keep information brief and to the point.

264 

MySQL to DB2 UDB Conversion Guide