Browse Prior Art Database

User Interface to Test Cases for Testing a Virtual Resource Manager

IP.com Disclosure Number: IPCOM000038652D
Original Publication Date: 1987-Feb-01
Included in the Prior Art Database: 2005-Jan-31
Document File: 2 page(s) / 14K

Publishing Venue

IBM

Related People

Jones, JE: AUTHOR [+3]

Abstract

A method is described to provide a user interface to coded test cases written to test Virtual Resource Manager (VRM) function interfaces. In accordance with the new method, a set of user-interface routines is made available to testers, so that they can better control the execution of their test cases coded in PL.8 code. The test case should follow a common format shown in Fig. 1. The external procedure and variable declarations provide the user interface: TLINIT - Initializes all variables and displays the tool menu for the user. TLBREAK - After each step in the test case, execution control variables are checked. Execution continues according to these variables. (Image Omitted) TLTERM - Allows the user to terminate the test case, or dump the error logs.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 2

User Interface to Test Cases for Testing a Virtual Resource Manager

A method is described to provide a user interface to coded test cases written to test Virtual Resource Manager (VRM) function interfaces. In accordance with the new method, a set of user-interface routines is made available to testers, so that they can better control the execution of their test cases coded in PL.8 code. The test case should follow a common format shown in Fig. 1. The external procedure and variable declarations provide the user interface: TLINIT - Initializes all variables and displays the tool menu for the user. TLBREAK - After each step in the test case, execution control variables are checked. Execution continues according to these variables.

(Image Omitted)

TLTERM - Allows the user to terminate the test case, or dump the error logs. TEST_ID - Used by the tool to display the current test case for user information. TEST_STEP - Execution of the test case is controlled by the value of TEST_STEP. The user may run the test case automatically, in which case TEST_STEP begins with a value of one, and is incremented at the call to TLBREAK by the value specified in the call. The test case will run until all steps have been run. VMABEND - This routine permits the user to log error information found during testing. An option exists in the tool menu which allows the user to specify whether he wants to stop each time an error occurs, or to continue running. An option is available to dump the error log when desired. In order to use the tool, the tester includes these external variables in his test case program, and then binds with the appropriate files. When running with the VRM Development Test Tool, the menu, shown in Fig. 2, is used to provide the user interface: The numbered options are used for controlling test case execution. When the AUTOMATIC switch is on, the test case executes sequentially. When the AUTOMATIC switch is off, the test case executes test steps which follow a step list which the user can specify using the 'L' option. When the STOP_ON_ERROR switch is on, control returns to the user every time an error is found. The user at this point may call the VRM debugger, terminate the test case, dump the error log, or continue execution of the test case. When the STOP_ON_ERROR switch is off, execution is not interrupted. Errors are logged whether the switch is on or off. When the STOP_ON_STEPS switch is on, the use...