Some migration trajectories are undertaken using external resources. These kinds of migrations are mostly iso-functional i.e. with no change in output whatsoever. The biggest complexity in such migrations it the iso-functional testing approach. Testing of the reports mostly works fine, pinpointing underlying errors on the other hand are very tough to lay hands on.
Understanding the real end to end information flow is needed to thouroughly test and above all correct errors in migrations.
Migration testing of reports depends on the complexity of the information flows e.g. is there a data warehouse or not, and the number of outputs that are to be tested. Such an assignment can take between a few days for simple migrations and a few months when complexity is huge and the number of reports plentiful. The underlying information architecture is an important determining factor in the amount of effort needed…