<< Progress Bars | Rational Test Enablers to the AUT >>

Ch. 3 Instrumenting the AUT

3-1

þ þ þ

C H A P T E R 3

Instrumenting the Application-Under-Test

This chapter addresses the first task you perform in TestFactory--instrumenting the
AUT so that you can obtain code coverage information for your scripts when you
start testing. This chapter describes what is required to instrument the AUT, how to
instrument the AUT, and how to use the stand-alone instrumentor to instrument
the source files of a Visual Basic application before build time. This chapter includes
the following topics:

About instrumentation

Adding the Rational Test Enablers to the AUT before instrumenting

Requirements for instrumenting the AUT

Instrumenting C++, Visual Basic, and Java object code

Instrumenting Visual Basic source code

About Instrumentation

If you want to obtain code coverage values for the scripts that you generate in testing,
then you first need to instrument the AUT. TestFactory uses information in the
instrumented files to calculate code coverage values for the best scripts that your
Pilots generate, as well as for the Robot scripts that you run from TestFactory.

TestFactory calculates a code coverage value and a UI coverage value for a best
script. The code coverage value represents the percentage of all AUT source code
that the script exercises. The UI coverage value represents the percentage of unique
UI objects that the script touches. Without instrumentation, TestFactory can use
only UI coverage as a metric to generate a best script. Because instrumentation
significantly improves testing results, we highly recommend that you instrument the
AUT before you map it.