Terminology

Several new terms are unique to NaviQuest. You will need to familiarize yourself with them before you begin to use this facility.

The following terminology and concepts are used throughout this topic:

base line test set: A special case test set, which includes all test cases for data sets not planned for SMS management. Expected values are nulls (''); the associated special subtype prefix is NEVR.
data classification: The process of determining the data types in your installation and identifying data subtypes that require specific SMS data services.
data subtype: Groupings of data sets from a data type needing identical SMS services, such as performance, backup, migration, or deletion. NaviQuest testing is managed at the subtype level.
data type: Major groupings of data. TSO, test, batch production, online production, system, and temporary are examples of data types that most installations have.
errors: Results that are different from the expected results. Errors are a subset of exceptions.
exceptions: A test case whose results differ from the saved expected results. For a regression test case, this exception is also an error; for an initial test case, this exception might or might not be an error. If the result is equal to the expected value, there is no error.
expected results: Values that you want assigned by the ACS routines for data class, storage class, management class, and storage group for a specific subtype when the ACS routines perform correctly.
initial test: First-time testing of a single data subtype performed prior to converting the data to SMS. The test may include regression tests for other data subtypes that have already been tested successfully.
phase or implementation phase: Data conversion to SMS management of one or more data subtypes with the same data type.
phase test set: Group of subtype test sets that define all data subtypes that make up a phase. Phase test sets are converted to SMS management within a single phase.
regression test: Testing of data subtypes that have already been successfully tested, along with the initial test of the current phase subtype.
results: Values that are assigned by the ACS routines for data class, storage class, management class, and storage group for a specific test case. These results might or might not be correct.
saved expected results: Results that have been saved in the test case after the successful initial test of the subtype test set. The results are used by the ACS comparison function during regression testing.
subtype prefix: A unique 1-to-4 character prefix associated with each data subtype. This prefix is used to relate the data classification data subtype to the subtype test set and to group all test cases together for a single subtype test set.
subtype test set: A group of test cases for all data sets associated with the same data subtype. All test cases within one subtype test set have the same expected results.
testbed library: A partitioned data set (PDS) that contains one member to define each test case.
test case: Parameters associated with a single data set that is tested using ISMF option 7.4.3.