background image
<< Restoring the Default Property Values | Creating a Test Suite >>
<< Restoring the Default Property Values | Creating a Test Suite >>

Ch. 6 Developing and Running a Test Suite

C H A P T E R 6
Developing and Running a Test Suite
This chapter describes Test Suites and how to use them to run scripts on your local
machine. This chapter includes the following topics:
Overview of Test Suite functionality
Creating a Test Suite
Running a Test Suite
Viewing the results of a Test Suite run
Overview of Test Suite Functionality
You can insert a Test Suite object
in the application map to organize and track scripts
and to run them in batches. Test Suites are useful for organizing and running groups
of best scripts, defect scripts, and scripts created against a specific build of the AUT.
In addition to Pilot-generated scripts, a Test Suite can include other Test Suites,
customized TestFactory scripts, and Robot scripts. Because a Test Suite contains
pointers to the scripts that you insert in it, you can include a specific script or
Test Suite in several different Test Suites.
If you run a Test Suite on your local machine, TestFactory runs the scripts in the
order that you specify. The sequence in which you arrange them depends mostly on
which script run results you want to see first. However, a particular script run
sequence can affect the AUT in unexpected ways. You can use Test Suites to explore
such possibilities.
The Test Suite Coverage tab provides an aggregate code coverage value for all of the
scripts that it contains. You can use the results to determine how much code was
exercised during a Test Suite run.
The Test Suite is a convenient tool for organizing groups of scripts for regression
testing. You can drop Pilots into several functional areas of the application map, run
them to obtain best scripts and defect scripts, and then place the scripts in
Test Suites.