Browse Prior Art Database

Software-Controlled Unit Testing for IBM System/360

IP.com Disclosure Number: IPCOM000073901D
Original Publication Date: 1971-Feb-01
Included in the Prior Art Database: 2005-Feb-23
Document File: 2 page(s) / 13K

Publishing Venue

IBM

Related People

Greene, RA: AUTHOR

Abstract

This concept defines a method of performing software-controlled unit testing. A unit (a separately assembled section of machine instructions) can be isolated from the remainder of the system (interfacing units of code) and given a controlled execution. This is advantageous for the development of new system because it allows testing of units as they are developed, rather than after a group of interfacing units are developed. It is attractive for testing units in existing systems for purposes of isolating malfunctioning units.

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

Page 1 of 2

Software-Controlled Unit Testing for IBM System/360

This concept defines a method of performing software-controlled unit testing. A unit (a separately assembled section of machine instructions) can be isolated from the remainder of the system (interfacing units of code) and given a controlled execution. This is advantageous for the development of new system because it allows testing of units as they are developed, rather than after a group of interfacing units are developed. It is attractive for testing units in existing systems for purposes of isolating malfunctioning units.

This concept provides controlled unit testing by:

1) Isolating the unit from the remainder of the system.

2) Simulating an interface with the unit.

3) Controlling data in the interface.

4) Mapping the interface to verify the unit's manipulation

of data in the interface.

5) Controlling entries to and exits from the unit.

This concept can be implemented in such a manner that writing a test case to test the unit can be performed at a macro-language level, with the exception of test case code which simulates the function of the normal interfacing units that are not present during the isolated test.

The following are requirements of the macros which would satisfy the ability to write test cases to perform this concept of unit testing under an existing IBM System/360 Operating System: 1. Macro 1 generation (executable code):

a) Initialization routine -- cause control on SVC

(supervisor call) and program check interrupts to be

given

to the test monitor (this causes control on all exits

from the unit being tested to be given to the test

monitor

b) Test monitor -- gets control on SVC and program check

interrupts and links to the appropriate test case exit

handling routine for the interrupt code as defined in

Macro 5.

c) Mapping subroutine -- executed upon request by a Macro 3

to display interface contents on a printer.

2. Macro 2 generation (executable code):

a) Set up interface as defined in a Macro 4.

b) Set trap on exi...