Overview

CA Verify for CICS is used to identify changes in a test stream of pre-recorded 3270 activities. This test stream can be used over and over again against a new software release for both regression and volume testing. However, instead of using the RUN Mismatch panel to pinpoint these changes during runtime, you can use the Rules function to identify known changes before running a test stream and specify, in advance, how CA Verify for CICS is to handle each change.

To identify changes within a test stream, you must first tell CA Verify for CICS how to recognize the screens that need changes. This is done by creating rules that define what the changes are. This collection of rules is called a ruleset.

There are three types of rulesets: test stream, system, and application. How a rule is applied when the test stream is run depends on the type of ruleset that the rule belongs to.

In a test stream ruleset, rules are applied to all screens in the test stream.
In a system ruleset, rules are applied to all screens in all test streams in the system.
In an application ruleset, rules are applied to all test streams in the application.

You can find more detailed information on the different types of rulesets in the section Creating a Ruleset later in this chapter.

All of the rulesets in the CA Verify for CICS data set are listed on the Ruleset Selection Menu. From this menu, you can use the Ruleset Browse feature to examine the summary information about the rules within a ruleset. This information lists all of a ruleset's rules, and summarizes the actions each rule performs.