Migration unit testing process

Shell Programming and Scripting
1

Hi,
We are doing migration from DB2 to Teradata.
There are couple of things involving in the project.

Please see below following order

Autosys-Jil script
Profile script
Category1
Teradata script
Data stage job script
Tera data script
Export files script..

Like that we have 10000 jobs....

We are planning to migrate all the scipts. We did lot of atomization to change all the scripts,,, like search and replace the string....

Now the challenging task is UNIT TESTING.
I suggested the client two ways:

  1. We deploy all the existing code in to one schema.....
    Another schema we will deploy the latest code....
    We will compare with the counts in the tables.
    The output counts should be matched.

Advantages:
1. Improve the quality of testing
2. Work flow is understandable.
Disadvantages:
1. Investing llot of cost on resources.
2. Client is not accepting to spend that much money on additional resource

  1. First deploy the existing code then load the data into tables. Then take the back up of the tables and deploy the new code and trigger the load.
    Compare the two tables.
    The counts should be match.

Advantages:

  1. Save the amount of resource cost.

Disadvantages:

  1. Re work process is more if the output is not correct.

Please advise me any other solution.

We have very less time to do on unit testing. Help me on advises and automise the unit testing process.

Thanks
Suri...

2

Maybe it makes sense to have ordered queries on all tables, then run the output through a filter, and finally pass it through a checksummer (md5 for instance):

<psuedocode>
For each table:
  select * from <table> order by <primary key> 
  Output query to a file. 
  Send file through a formatting filter to remove, for instance, unprintable characters and spacing. 
  Send resulting output through  openssl md5 -