Browse Prior Art Database

Test Sequence Supervisory Routine

IP.com Disclosure Number: IPCOM000045442D
Original Publication Date: 1983-Mar-01
Included in the Prior Art Database: 2005-Feb-07
Document File: 3 page(s) / 57K

Publishing Venue

IBM

Related People

Cox, CM: AUTHOR [+2]

Abstract

The program routine of Fig. 1 supervises the sequence of tests performed by an operator working with an interactive terminal to test a device attached to the system. The program in combination with the test sequence table in Fig. 2 provides for test sequence integrity and versatility. The integrity is due to the supervisory program guiding the operator through the desired test sequences. The versatility is due to the programmable nature of the test sequence table and the ability of the program to exercise different options in the table. In addition depending upon test results during the test sequence, the path through the test sequence will vary.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 3

Test Sequence Supervisory Routine

The program routine of Fig. 1 supervises the sequence of tests performed by an operator working with an interactive terminal to test a device attached to the system. The program in combination with the test sequence table in Fig. 2 provides for test sequence integrity and versatility. The integrity is due to the supervisory program guiding the operator through the desired test sequences. The versatility is due to the programmable nature of the test sequence table and the ability of the program to exercise different options in the table. In addition depending upon test results during the test sequence, the path through the test sequence will vary.

In the test sequence table of Fig. 2, each entry in the table has a test number (TEST #), a condition code (CC), an indication of an analysis routine (ANA #), if any, and a pointer to the next test entry. The test number indicates the test being performed. The condition code indicates the results of the test performed. The analysis identifies the type of analysis routine, if any, available to that test routine. Analysis may be used to select varied functions to be performed conditionally based upon testing results. For example, it can invoke changing test fixturing, attaching automated test equipment, recording of test results, or displaying of repair action to be taken as well as actual analysis of test data. The test entry pointer points the way to the next test entry after the test and analysis have been performed.

Referring to Fig. 1, some examples of how the supervisory routine uses the test sequence table will now be described. At the start of the test sequence routine, operation 10 loads and executes test 1 and waits for the condition code resulting from test 1. When the condition code is returned from test 1, decision 12 checks for an entry in the test sequence table of Fig. 2 for a test 1 having that condition code. If there is no match or the condition code is 00, the supervisory routine proceeds to operation 14. In operation 14, if there is a data analysis to be run, the supervisory routine allows the analysis and waits for the condition code as a result of the analysis.

If the search operation monitored by decision 12 finds a test with the same condition code that resulted from the test operation during operation 10, then the supervisory routine points to that entry in the test sequence table and performs the analysis specified by the new table entry. For...