9.1.4  Time planning and time exposure

The time planning should be based on realistic and validated estimates. If the 

estimates for the migration of the application and database are inaccurate, the 

entire project plan will slip, and the testing is part of the overall project plan. 

It is always best to tie all test dates directly to their related migration activity 

dates. This prevents the test team from being perceived as the cause of a delay. 

For example, if system testing is to begin after delivery of the final build, then 

system testing begins the day after delivery. If the delivery is late, system testing 

starts from the day of delivery, not on a specific date. This is called dependent or 

relative dating.

Figure 9 1 shows the test phases during a typical migration project. The 

definition of the test plans happen in a very early moment. The test cases, and all 

its following tasks, must be done for all test phases.

Create Test Plan

Create Test Cases

Prepare Test Items

Prepare Infrastructure

Test Run in

Test Run in

MySQL Environment

DB2 UDB Environment

Compare Test Results

Figure 9 1   Test phases during a migration project

The time exposure of tests depends on the availability of an existing test plan, 

and already prepared test items. The efforts depend also on the degree of 

changes during the application and database migration. 

 Chapter 9. Testing and tuning 

269