Integration Testing

Integration testing determines if a program works properly with other programs. A program can pass unit testing — and then fail when executed in conjunction with other programs that were not part of the unit test. For example, if several programs update the same file, a change to one program may have unexpected effects on the others.

Follow these steps:

Create a test stream logging all affected programs — that is, the program that changed and all programs run in conjunction with it. Or, use a previously logged test stream that tests this application.
The logged test stream can be created by one of the following methods:
- Capturing a series of transactions in your production region
- Combining several unit test streams. Use the Append or Insert utilities if you want the test streams to run sequentially, or the Merge utility if you want the test streams to run concurrently.
Change the screen in the application.
After the changed program passes unit testing, run the logged test stream. CA Verify for VTAM compares the output produced by all the programs before the change with the output produced after the change.
CA Verify for VTAM automatically flags all differences. You expect one difference — the difference in the single field, which you changed. Otherwise, all the original and current screens should be the same.
If you find any unexpected differences, make corrections and rerun the logged test stream until you are sure the modified program and all programs connected to it are functioning as anticipated.