background image
<< Instrument a secondary application | Stand-Alone Instrumentor >>
<< Instrument a secondary application | Stand-Alone Instrumentor >>

The Coverage Dictionary

Instrumenting the Application-Under-Test
3-10
The Coverage Dictionary
As TestFactory instruments code, it creates a coverage dictionary that it uses to
calculate code coverage for scripts. If every member of your testing team shares the
same build of the AUT, and saves test data to the same project, then each has access
to the coverage dictionary after the AUT is instrumented.
If team members share the same build of the AUT, but have independent projects
and save test data to separate repositories, then they can move the coverage dictionary
between repositories to share it. A developer can instrument AUT source files and
export the coverage dictionary for use by testers who only have access to AUT
executable files. A tester can then import the coverage dictionary and use it to obtain
code coverage data on scripts (as long as the scripts run against the executable file
made from the same instrumented AUT). To move a coverage dictionary between
projects, you must export it from one project and import it to another project.
Exporting and Importing the Coverage Dictionary
To export the coverage dictionary after you instrument source files:
1. Click Tools > Import/Export Dictionary.
2. Under Action, click Export.
3. In the Export coverage dictionary to box, enter the path for the exported
dictionary file, including the .vcd file name extension.
4. Click OK.
Importing the Coverage Dictionary
To import the coverage dictionary:
1. Click Tools > Import/Export Dictionary.
2. In the Import coverage dictionary from box, enter the path of the file
to import, including the .vcd file name extension.
NOTE: The coverage dictionary is visible only after you instrument source files
or preinstrument the Visual Basic AUT using the stand-alone instrumentor.