Browse Prior Art Database

Internal Test System

IP.com Disclosure Number: IPCOM000112004D
Original Publication Date: 1994-Apr-01
Included in the Prior Art Database: 2005-Mar-26
Document File: 2 page(s) / 45K

Publishing Venue

IBM

Related People

Fincher, NW: AUTHOR [+3]

Abstract

MVS/ESA* DFP Storage Management Test and Support has implemented several test applications for testing the MVS/ESA DFP product. Collectively, these applications are referred to as the Internal Test System or ITS.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 69% of the total text.

Internal Test System

      MVS/ESA* DFP Storage Management Test and Support has
implemented several test applications for testing the MVS/ESA DFP
product.  Collectively, these applications are referred to as the
Internal Test System or ITS.

      Current implementations of ITS test both internal and external
interface is one documented in customer documentation for use by
customers; examples include READ and WRITE programming statements.
Internal interfaces are not available to customers and are normally
documented in System Structure or Component Structure Documents;
examples include a CALL of a module or an explicit SVC.  An internal
interface may be to a product, a component, or a program module.

      An ITS implementation builds parameter lists and data
structures required by a function and then invokes the function.
Parameter and data structure values are specified by input scripts,
processed by an ITS parser, converted to the proper data format, and
placed in the proper storage locations.  When all of the inputs for a
function are processed, the function is invoked and results verified.
Problem determination is simplified by isolating failures to a
specific function call while providing snapshots of input/output
parameters.

      Most ITS applications do little or no validity checking of the
input values and, in general, invalid or inconsistent values are
allowed.  This is often useful for forcing error paths in the
function being tested.  How...