background image
<< Setting Up the TestCodeChanges Add-In | Using the TestCodeChanges Add-In >>
<< Setting Up the TestCodeChanges Add-In | Using the TestCodeChanges Add-In >>

Preparing to Test Code Changes

Preparing to Test Code Changes
8-3
2. To continue with the setup, click Next.
3. To complete the setup, click Finish.
After you set it up, the TestCodeChanges add-in is loaded in your Visual Studio
development environment and automatically tracks changes made to the source code
files of the open project.
Preparing to Test Code Changes
The requirements for testing changes that you have made to the AUT source files
are as follows:
The AUT must be instrumented.
You must first recompile the executable file for the open project.
If you are working in Visual Basic, you must save the changed source files after
you recompile the executable file.
If you plan to run Robot scripts to test code changes, you must first run the
scripts from TestFactory so that TestFactory can calculate code coverage values
for them.
The add-in automatically displays all of the scripts that exercise the changed files and
that have code coverage values. You can select some or all of these scripts to include
in a regression suite that you can then run to test changed files. You can add scripts
that do not exercise changed files to the regression suite. For example, you may want
to include a support script that brings the system to a state necessary for testing.