<< Code Coverage and UI Coverage | Preparing for Automated Testing >>

Testing Software with TestFactory

Introduction

1-6

How you use TestFactory depends on whether you are the sole engineer on a project
or a member of a QA team, as well as the testing practices you have in place. How
you use TestFactory also depends on where you are in the testing cycle. For instance,
in the early phases of the product development cycle, you can use TestFactory to
automatically find defects in the AUT. As the AUT matures and stabilizes, you can
use TestFactory to build regression suites. The tasks that you might perform in a
typical TestFactory project are as follows:

With each new build, you instrument the AUT, update the application map, run
scripts (regression Test Suites) from the previous build, track and resolve defects,
create and run new scripts, and reorganize test material.

Task

Manual Chapter

Instrument the AUT so that TestFactory can
calculate code coverage for scripts.

Chapter 3: Instrumenting the
Application-Under-Test

Use the Application Mapper to map the AUT.

Chapter 4: Developing and Working
with the Application Map

Run several Pilots in functional areas of the AUT to
generate best scripts and defect scripts that test those
areas.

Chapter 5: Automatically Generating
Scripts
Chapter 7: Using the AutoPilot

Examine failures uncovered by the defect scripts.

Chapter 5: Automatically Generating
Scripts

Examine the outlined steps and detailed code
coverage results for best scripts.

Chapter 5: Automatically Generating
Scripts

Create a Test Suite that contains pointers to all of
the best scripts and defect scripts and run the Test
Suite against future builds of the AUT.

Chapter 6: Developing and Running a
Test Suite

Create customized TestFactory scripts to augment
the coverage your Test Suites provide.

Chapter 5: Automatically Generating
Scripts

Use the TestCodeChanges add-in for Visual Studio
to access and run scripts that test changes to the
source code of the AUT.

Chapter 9: Testing Code Changes in
Visual Studio

Run Pilots to test the AUT for defects related to
memory access.

Chapter 5: Automatically Generating
Scripts