When the behavior of the system under test (SUT) is affected by the values returned by another component whose services it uses, we call those values indirect inputs of the SUT. Indirect inputs may be actual return values of functions, updated (out) parameters of procedures or subroutines, and any errors or exceptions raised by the depended-on component (DOC). Testing of the SUT behavior with indirect inputs requires the appropriate control point on the "back side" of the SUT. We often use a Test Stub to inject the indirect inputs into the SUT.
Copyright © 2003-2008 Gerard Meszaros all rights reserved