Browse Prior Art Database

Software Testing Tool

IP.com Disclosure Number: IPCOM000050236D
Original Publication Date: 1982-Sep-01
Included in the Prior Art Database: 2005-Feb-10
Document File: 1 page(s) / 12K

Publishing Venue

IBM

Related People

Czyszczewski, JS: AUTHOR

Abstract

This article describes a software testing tool which may be used to test the software aspect of apparatus having a controller, such as a printer controller system. A simple hardware instruction mapper is used which under processor control can readily determine whether a particular branch has been taken. With this capability, a simple technique is provided for determining the extent of branch coverage which is a stronger criteria than instruction coverage in testing software since instruction coverage is implied by branch coverage.

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

Page 1 of 1

Software Testing Tool

This article describes a software testing tool which may be used to test the software aspect of apparatus having a controller, such as a printer controller system. A simple hardware instruction mapper is used which under processor control can readily determine whether a particular branch has been taken. With this capability, a simple technique is provided for determining the extent of branch coverage which is a stronger criteria than instruction coverage in testing software since instruction coverage is implied by branch coverage.

Software defects are a serious problem in processor controlled printers because correction of software problems in the field is not practical. Prior to shipment, problems are conventionally checked out by providing test cases which exercise the printer. A problem with this approach is that it is difficult to determine when all of the software has been tested or what remains to be tested. Two measurement techniques are typically used. One indicates the percentage of instructions tested, and the other indicates the percentage of branches executed. Based upon the assumption that branch coverage is a stronger criteria than instruction coverage since instruction coverage is implied by branch coverage, software techniques have been used to measure branch coverage. However, such software tools have the disadvantages of being language dependent and of increasing the size and execution time of the program being tested.

Hard...