Browse Prior Art Database

DART, An Automated Diagnostic Analysis Routine Tester

IP.com Disclosure Number: IPCOM000107698D
Original Publication Date: 1992-Mar-01
Included in the Prior Art Database: 2005-Mar-22
Document File: 4 page(s) / 154K

Publishing Venue

IBM

Related People

Wendling, PA: AUTHOR

Abstract

Disclosed is an REXX88 PC program that submits a large number of test cases to the PCC Simulator and verifies the results against a set of expected values. The program was originally developed in the power area for verification and regression testing of the 9021 and 9022 analysis routines. The tester maximizes use of the PCC Simulator by injecting bugs previously manually applied by technicians. It also relieves the operator from the task of results verification, a time consuming process. The program design is flexible enough for use on other areas of the CEC. Application of the program in the CP area of the CEC is currently being pursued.

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

DART, An Automated Diagnostic Analysis Routine Tester

       Disclosed is an REXX88 PC program that submits a large
number of test cases to the PCC Simulator and verifies the results
against a set of expected values.  The program was originally
developed in the power area for verification and regression testing
of the 9021 and 9022 analysis routines. The tester maximizes use of
the PCC Simulator by injecting bugs previously manually applied by
technicians.  It also relieves the operator from the task of results
verification, a time consuming process.  The program design is
flexible enough for use on other areas of the CEC.  Application of
the program in the CP area of the CEC is currently being pursued.

      The DART package is a collection of REXX88 programs used to
sequence th PCC simulator through the various stages of Bring Up,
Error Injection, AQE Collection, Results Comparison and System
Recovery in case of VM Net loss.  The functions run on the PC and
communicate with the PCVMSERG, the operator's console, via HOSTMYTE.
Benefits of the DART tester

      Because of changing hardware requirements and feedback from
field data, the AR package is continually being updated and improved.
The DART tester is used to verify existing functions that have not
been corrupted during an AR update and that the required functions
are operating correctly. This results in a significant reduction in
problem escapes to the test floor and, ultimately, the field.

      Since the overall product quality has been improved, a reduced
release schedule is possible.  That is, less releases are required to
achieve the desired product quality level.

      A feature of the DART tester is its ability to re-apply bugs.
This can be equated to several months of testing on the machine
floor.  By DART testing the stuck fault conditions, several shifts of
EVT work can be eliminated or scheduled for other tests.
-    PMS Reduction
-    Reduced Release Schedules
-    Improved Product Quality
-    Regression Test Release
-    Shortened EVT Period
-    AR Functional Verification.
Test Case Delivery System

      The Bugs scenarios can be applied in different modes: PMODE,
apply the bug and power on the system; IMODE, power on the system and
then apply the bug; CMODE, power on the system, apply the bug, power
off the system.
-    Power on Mode Testing (PMODE)
-    Interrupt Mode Testing (IMODE)
-    Cyclic Monitor Testing (CMODE)
-    Power Off Testing (OMODE).
DART Configuration

      The DART package consists of 22 REXX BAT files, totaling 119K
bytes of code.  FRU information is contained in 4 files consisting of
250K of data.  (These numbers do not contain test case information.)
DART Driver Flow

      The main DART program flow is shown below, identifying the
steps of a typical run.  Not shown in this flow is the recovery code
when the VM net drops, the exception handler code, and the retry
proces...