Tool Mentor: Setting Up the Test Environment in Rational TestFactory

Purpose

This tool mentor describes how to perform the steps to set up the Rational TestFactory environment so that you can Implement generated Test Scripts for the application-under-test (AUT).

This section provides links to additional information related to this tool mentor.

• Set Up Tools
• Implement Test
• Structure the Test Implementation
• Define Testability Elements
• Support Development

Overview

Before you can use Rational TestFactory to automatically generate Test Scripts, you must set up the Test Environment Configuration. TestFactory generates Test Scripts based on an the "application map"-a hierarchical list of "UI objects" that represent the windows and controls in the user interface of the application-under-test (AUT).

This tool mentor is applicable when running Windows 98/2000/NT 4.0.

To set up the test environment in Rational TestFactory:

1. Define the project to Rational TestFactory and instrument the AUT
2. Map the application-under-test
3. Review and refine the application map

1.   Define the project to Rational TestFactory and instrument the AUT

The first time you open a project in Rational TestFactory, you need to supply information about the project and the application-under-test (AUT). The main functional areas of TestFactory remain unavailable until you specify the project information.

To measure code-based test coverage of an executed Test Script, the AUT must contain instrumentation points-counters that tally the parts of the code that a Test Script executes. Rational TestFactory uses information in the instrumented files to calculate code-based coverage data for both the Test Scripts that TestFactory generates and the Robot Test Scripts that you can play back from TestFactory.

  Refer to the following topics in Rational TestFactory Help:

• Starting TestFactory
• Specifying information for a new project
• Instrumenting the application-under-test

2.   Map the application-under-test

A well-developed application map is the foundation for generating Test Scripts in Rational TestFactory. The "Application Mapper"-the process that creates the application map-thoroughly explores the user interface of the application-under-test (AUT). Each window and control is examined and compared to known classes and subclasses, which are stored in the "user interface (UI) library." Based on the outcome of the comparison, the mapping process creates a UI object, which is an instance of the matched class, and places it in the application map.

Every defined class in the UI library has a specific set of "UI object properties" associated with it. When it creates a UI object, the Application Mapper assigns the object the set of properties associated with its class. These properties both identify the control in the AUT that the object represents, and inform Rational TestFactory how to exercise the control during mapping and testing.

If the AUT contains a logon dialog box that requires special input such as a user ID or a password, you must provide specific logon information to the Application Mapper.

When mapping is complete, the information in the Mapping Summary report reflects the windows and controls in the AUT that Rational TestFactory has mapped.

   Refer to the following topics in Rational TestFactory Help:

• Map the AUT using the Application Mapper Wizard
• Map the AUT using the Map It! shortcut
• Mapping an AUT that has a logon dialog box

3.   Review and refine the application map

The first version of the application map may not be an accurate reflection of all the controls in the AUT. The application map may be incomplete or mapped UI objects may need reclassifying.

A well-defined application map is critical to generating quality Test Scripts. Rational TestFactory can test only the controls in the AUT that are represented by UI objects in the application map. By reviewing and refining the application map before you start testing, you can increase the scope and quality of the generated Test Scripts.

You can review the application map by comparing the windows and controls that you see in the AUT with the UI objects in the application map. If you notice unmapped controls in the AUT, and if you want to test these controls, you need to determine and resolve the cause for each unmapped control.

   Refer to the following topics in Rational TestFactory Help:

• Review the application map
• Defining undetected controls
• Resolving generic objects
• Using interaction objects to improve the application map

Rational Unified Process