Previous Topic: Stress TestingNext Topic: Automated Batch Testing

Testing › Migration Testing

Migration Testing

Migration testing ensures that existing applications perform as expected when you have major hardware or software changes; for example, upgrading from one release of CICS to another, adding disk packs, or even migrating from VSE to MVS.

Follow these steps:

  1. Create a test stream by logging several critical hours of activity for as many terminals as you believe are necessary to provide a realistic "slice of life." For example, you may want to log all the terminals in a particular branch or department. Or, you may want to create a controlled test by combining and/or editing many unit tests.

    Remember, once you create this test stream, you can use it again and again to test system or software upgrades.

  2. At night or on a weekend, run the logged test stream, either from a terminal or as a batch job. Specify no operator think time so the test completes as quickly as possible.
  3. If the transactions execute normally and the output is correct, you can assume that the hardware or software change won't have any unexpected impact on production.