Testing CICS programs without CA Verify for CICS is difficult because your test region differs significantly from your production environment. For example, it's very hard to replicate the:
With CA Verify for CICS, it's easy to simulate production conditions. That means you can perform all types of testing — unit, integration, concurrency, regression, stress, and migration — so you know your application will perform as expected. The rest of this chapter will explain in detail how to use CA Verify for CICS to perform these types of testing.
To test applications effectively, you need well-constructed tests. CA Verify for CICS greatly simplifies the task of creating these tests. All you have to do is log test streams. Optionally, you can edit these test streams to meet your testing needs. For example, you can combine test streams, alter the input data to test a variety of conditions, or delete a sequence of screens. As you save test streams, you'll create a library of tests that will always be available to test application and system changes.
To further streamline the testing of application or system changes, CA Verify for CICS provides a powerful Rules function to use with your library of test streams. Rulesets let you identify the expected changes to the existing test stream due to application or system changes. By running the test stream in the new application with a specified ruleset, you can eliminate the need to stop at the expected changes, greatly streamlining your testing.
|
Copyright © 2012 CA.
All rights reserved.
|
|