Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Function Level Unit Test Environment

IP.com Disclosure Number: IPCOM000103557D
Original Publication Date: 1993-Jan-01
Included in the Prior Art Database: 2005-Mar-18
Document File: 2 page(s) / 73K

Publishing Venue

IBM

Related People

Creasman, JD: AUTHOR

Abstract

Disclosed is a process for isolating software function in order to achieve functional test coverage of the software significantly earlier in the development cycle.

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

Function Level Unit Test Environment

       Disclosed is a process for isolating software function in
order to achieve functional test coverage of the software
significantly earlier in the development cycle.

      The transition from coding to testing in the typical software
development cycle begins with unit test (UT) and is immediately
followed by a function verification test (FVT).  The traditional
objective of UT is to verify that the logic of a single module
executes according to module specifications, leaving FVT to verify
that the functions supported by a collection of these modules execute
correctly in the integrated product.  The process described in this
article outlines both the method and the means to 1) integrate a
collection of functionally related modules (referred to as the test
component); and 2) perform functional testing against the integrated
code during the time normally allotted to UT [1,2].

      The test component is defined by a file which lists the object
files containing the test component members (i.e., code sections).  A
program processes this list to produce an executable load library
from the set of object files.  Testing is performed by dynamically
loading and then executing functional paths through this body of code
as though it were the complete product.  Unresolved references within
the load library are automatically supplemented by scaffolding after
the component is loaded for execution.

      Testing is performed by...