background image
<< Deleting UI Object Components | Application Mapper >>
<< Deleting UI Object Components | Application Mapper >>

Mapping Secondary Applications

Mapping Secondary Applications
Mapping Secondary Applications
An AUT can consist of a main application and one or more secondary applications
that the main application loads and executes. A secondary application can be one that
is developed as part of the application, or it can be a third-party application. If the
AUT calls secondary executable files, you can map these in addition to the main
executable file.
If you specified a secondary Visual Basic application to instrument before mapping,
TestFactory automatically lists its executable file on the Application Mapper tab.
This gives the Application Mapper access to all of the controls in the secondary
executable file.
To prevent the Application Mapper from mapping an instrumented secondary
application to full depth during subsequent mapping sessions:
1. Click Tools > Options, and then click the Application Mapper tab.
2. To exclude a listed executable file from mapping, do one of the following:
In the List of executable files to map box, clear the check box to the left
of the listed executable file.
Click the file path, and then click Remove.
3. Click OK.
After you next map the AUT, the Mapping Summary report displays the secondary
executable files that were excluded from full-depth mapping.
If you did not instrument a secondary application (Visual Basic only), the Application
Mapper maps just the main application and the first level of controls in the secondary
application. If you plan to fully map and test a secondary application written in Visual
Basic, we recommend that you instrument it before mapping. For information about
instrumenting a secondary Visual Basic application, see Instrumenting Visual Basic
Source Code
on page 3-7.