The batch testing

Scope of batch testings

Out of scope of batch testing

Risks & dependencies

Resource requirements

Deliverables

It is assumed that for overnight batch jobs to work on the Linux operating systems, 75 out of 220
batch jobs needs amendments. These changes are still unknown until a Unix developer has looked
into existing codes. The developer needs to analyse, amend & test the code in the Linux system to
prove it be compatible

Once it has been unit & integrated tested it will be tested on the cloud during Ellis replatforming
project. It is also evident that 10 out of 75 batch jobs will need further amendments for it to work on
the new data centres

Ellis Transformation project will take a risk based approach of batch testing & will majorly prove that
10 further amended batch jobs are working

Further, a full regression testing will be performed to prove that none of the unchanged jobs are
affected due to data centre migration

Regression testing will aim to test that jobs can run & can produce extract files or databases are
updated

Regression testing does not scope for testing the contents of extract files

However where a batch is completely changed to work on new data centre, extract files will be
produced & results will be verified against equivalent Solaris files. Where required extract files will be
sent to the 3rd parties for acceptance by their system. The processed files will be pulled by esure
system for further processing.