IBM OS/390 manual Responsibilities, Recommendations, Testing Priorities

∙Simulated production (or acceptance) tests: in conjunction with batch production tests

∙Network and performance tests with actual connection to future end users

OS/390 batch application tests include:

∙

∙

Unit (or technical) tests: on a representative sample of jobs

System (or Functional) tests are scenarios of chained job executions corresponding to application flows

∙Simulated Production/Parallel (or acceptance) tests: replicate one day of VSE operations in MVS

Batch and online tests are coordinated to test the integration of batch and online applications.

The three phases of testing are building blocks. Each uses the output and successes of its predecessor to build on. Although they build on each other in a sequential manner, the boundaries between each in practice are blurred by overlapping test start dates and durations. Testing activity increases through this incremental building process from unit to system to parallel testing. The testing process is completed through a series of test switchovers which end with the final switchover/cutover. This last switchover converts your entire production system to OS/390.

32.5.4.1 Responsibilities

In a migration project it is the responsibility of the customer to do and resolve the testing of their converted applications. It is not realistic to expect that a contractor or service provider can come into the customer environment and understand the applications and application flow. It is the customer who understands how all these elements work individually and together.

32.5.4.2 Recommendations

Testing Priorities

All ²critical² applications should be targeted for testing with daily applications tested first, followed by weekly, then monthly. Testing of quarterly and other periodically scheduled programs and applications can be scheduled after the production cutover, if necessary.

Test the most critical, or hardest to fix, applications first (that is, those programs, applications most subject to failure or degraded performance) thereby allowing more time to modify or tune these applications, if necessary.

Personnel Involvement in Testing

For each test implementation task (scheduling, setup, submission, execution control, result review and validation, debug) it is critical to use the exact same personnel who will be responsible for that task under OS/390 after switchover. Testing is not only to identify and correct conversion created regressions. It is the primary method to train and prepare the staff for OS/390 operations.

Chapter 32. Conversion Process 507