Using Rational TestFactory - A User's Guide: Outline

• Using Rational TestFactory
• Contents
• Preface
  • Audience
  • Other Resources
  • Contacting Rational Technical Publications
  • Contacting Rational Technical Support
• Introduction
  • About Rational TestFactory
  • Key TestFactory Concepts
    • The Application Map
    • The UI Library
    • UI Objects
    • Pilots and Automatic Script Generation
    • Script Segments
    • The Best Script
    • Defect Scripts
    • UAW Scripts
    • The UI Script
    • Code Coverage and UI Coverage
    • Test Suites
    • The AutoPilot
    • The Test Datastore
  • Testing Software with TestFactory
    • Preparing for Automated Testing
    • Before You Map the AUT
    • After You Map the AUT
    • Testing the AUT
  • Preparing to Work with the Application-Under-Test inTestFactory
    • Enabling Java and C++ Applications
      • Enabling Java Applications and Applets
      • Enabling C++ Applications
    • Selecting the IDE Extensions to Load for the AUT
    • Working with C++ Applications in TestFactory and Robot
• The TestFactory Interface
  • Starting TestFactory
    • Starting TestFactory from the Command Line
  • Using the New Project Wizard
  • Using the Project Assistant
  • The TestFactory Workspace
    • TestFactory Toolbars
      • The Standard Toolbar
      • The Insert Toolbar
      • The Tools Toolbar
      • The Report Toolbar
      • The Image Toolbar
      • The Interaction Object Toolbar
      • The Style Toolbar
    • The Left Pane
    • The Right Pane
    • Progress Bars
    • The Status Bar
• Instrumenting the Application-Under-Test
  • About Instrumentation
  • Adding the Rational Test Enablers to the AUT BeforeInstrumenting
  • Requirements for Instrumenting the AUT
    • Java Applications and Applets
    • C++ Applications
    • Visual Basic Applications
  • Instrumenting C++, Visual Basic, and Java Object Code
    • Setting the Compiler Option for a Visual Basic 6 Application
    • Setting the Compiler Option for a C++ Application
    • Instrumenting Object Code
  • Instrumenting Visual Basic Source Code
    • The Coverage Dictionary
      • Exporting and Importing the Coverage Dictionary
      • Importing the Coverage Dictionary
      • Specifying the Source File Directory for Browsing Coverage Data
    • Using the Stand-Alone Instrumentor to Instrument Visual Basic Source Code Files
• Developing and Working with the Application Map
  • About TrueMap Technology
  • Mapping the AUT for the First Time
    • Setting Up the Mapping Environment
      • Specifying Support Scripts
    • Using the Application Mapper Wizard to Map the AUT for the First Time
      • On-Screen Events During Mapping
    • Stopping the Mapping Process
  • Viewing and Evaluating the Mapping Summary Report and the Application Map
    • Viewing the Mapping Summary Report
    • Expanding and Navigating the Application Map
  • Application Map Objects and Their Properties
    • Renaming UI Objects in the Application Map
    • Properties of Objects in the Application Map
      • UI Object Properties
      • User Properties
    • Finding Objects in the Application Map
  • Excluding Specific Functions in the AUT from Mapping andTesting
  • Improving the Application Map
  • Using Interaction Objects to Guide the Application Mapper through the AUT
    • Interaction Objects and Interaction Object Components
    • Setting Up an Interaction Object
      • Inserting an Interaction Object
      • Copying and Pasting Interaction Objects
      • Copying and Pasting Interaction Object Components
    • Setting the Properties for a UI Object Component
      • Setting an Interaction Method for a Component
      • Assigning a Style to an Input-Type Component
      • Specifying a Required String Case for a Component Using the Property List
      • Setting the Interaction Order for Components
      • Excluding a Component from Mapping
      • Mapping the Path Set by an Interaction Object
    • Excluding an Interaction Object from Mapping
    • Using Interaction Objects to Map Alternative Paths in theAUT
      • Using an Interaction Object to Map Beyond a Logon Dialog Box
      • Mapping Alternative Paths in an AUT
  • Using UI Object Properties to Specify Input and Interaction Order for Mapping
    • Specifying Actions to Use for Mapping a UI Object
    • Specifying a Required String Case forMapping
    • Controlling the Interaction Order for UI Objects
      • Setting the InteractionOrder Property for UI Objects
    • Restoring the Default Values for UI Object Properties
  • Creating and Mapping a Region Object for an UnmappedControl
    • Creating a Region Object
      • Method 1 (recommended)
      • Method 2
      • Method 3
    • Changing the Size or Position of a Region Object
    • Setting the Action or Input for a Region Object
    • Adjusting the Hot Spot for a Region (or Other UI) Object
    • Deleting a Region Object
  • Mapping Similar Windows
    • Merging Window Objects
    • Splitting Window Objects
    • Redirecting a Shortcut
    • Adjusting Sensitivity to Differences in Window Objects
  • Timing Events During Mapping
    • Specifying a Maximum Wait-For-Idle Time for All Controls
    • Timing Events for a Class or Subclass of Controls During Mapping
    • Timing Events for a Single Control During Mapping
  • Reclassifying a Generic Object
  • Handling Error Messages and Crash Transition Objects in the Application Map
  • Mapping New Builds
    • Mapping a Changed Region of the AUT Using the Map It! Shortcut
    • Mapping a Changed Region of the AUT Using the Application Mapper Wizard
    • Deleting UI Objects Mapped for Controls that Have Been Removed from the AUT
      • Deleting UI Object Components Associated with a Deleted UIObject
    • Running the Application Mapper from the Command Line
  • Mapping Secondary Applications
  • Inserting TestFactory Objects in the Application Map
    • Creating a Marker in the Application Map
  • Creating and Working with TestFactory Reports
    • Configuring a Hierarchy Report
    • Configuring a Listing Report
    • Configuring a UI Checking Report
    • Modifying a Report
    • Rerunning a Report After Changing the Application Map
    • Exporting a Report as a Text File
    • Printing a Report
• Automatically Generating Scripts
  • About Pilots
  • Setting Up and Running Pilots
    • Effective Pilot Placement
    • Inserting a Pilot
    • Setting Up and Starting a Pilot Run
      • Modifying Settings on the Setup Tab
      • Modifying Settings on the Stop Criteria Tab
      • Modifying Settings on the Exclude Tab
      • Restoring Default Pilot Settings
      • Making Best Script Verification Unavailable
      • Starting the Pilot Run
    • On-Screen Events During a Pilot Run
    • Stopping a Pilot Run
  • Examining Pilot Run Results
    • Pilot Run Folder Contents
      • Renaming Generated Scripts
    • Viewing the Script Outline
    • Viewing Coverage Results for a Script
      • Viewing Code Coverage Information for Scripts Generated for Java Applications and Applets
      • The Coverage Browser (C++ and Visual Basic Applications)
      • Changing the Appearance of Text In the Coverage Browser
    • Viewing the Log for a Defect Script
    • Reporting a Defect
    • Viewing a UAW Script
    • Using Pilot Scenarios to Simulate User Action Sequences
      • Creating a Pilot Scenario
    • Using Pilot Mix-Ins to Test Random Interactions
      • Creating a Pilot Mix-In
    • Additional Adjustments for Pilot Runs
  • Changing Default Settings for Pilots
  • Opening and Editing a Best Script in Robot
    • Opening a Best Script in Robot from TestFactory
    • Obtaining Code Coverage for Robot Scripts
  • Creating a Custom TestFactory Script
    • Creating and Opening a Custom TestFactory Script
    • Recording Actions in a Custom TestFactory Script
  • Checking for Memory Errors in Visual Basic and C++ Applications (Windows NT)
    • Preparing to Test for Memory Errors in the AUT
    • Running a Pilot to Check for Memory Errors
      • Checking the Timing of a Pilot Run
      • Viewing the Results of a Pilot Run to Detect Memory Errors
    • Running Scripts to Check for Memory Errors
  • Testing Controls in the AUT During Pilot Runs
    • Selecting a Style and Modifying Data Entry Settings for UI Objects and UI Object Components
      • Specifying a Required String Case for a Style
      • Specifying a Mix of Random Entries for a Style
      • Specifying or Modifying Mask Cases for a Style
      • Specifying or Modifying String Cases for a Style
      • Creating a Custom Data Entry Style
    • Managing Data Entry Styles
    • Modifying Properties to Control TestFactory Actions During PilotRuns
      • Excluding a Control from All Testing
      • Setting the Interaction Order for Controls During Testing
      • Specifying a Delay Interval to Include in GeneratedScripts
      • Specifying a Wait Interval to Apply to an Object During Testing
      • Specifying a Required String Case
    • Specifying the Entry Data Used to Test Input Controls
      • Specifying String Cases to Use During Testing
      • Specifying Mask Cases to Use During Testing
      • Specifying Random Entry Data to Use During Testing
    • Excluding Controls from Testing
    • Restoring the Default Property Values for UI Objects andComponents
• Developing and Running a Test Suite
  • Overview of Test Suite Functionality
  • Creating a Test Suite
    • Creating a Test Suite Using the Find Objects Window
  • Running a Test Suite
    • Running a Test Suite on Your Local Machine
  • Viewing the Results of a Test Suite Run
    • Viewing Test Suite Run Results in the Status Tab
    • Viewing Test Suite Run Results in the Coverage Tab
      • Viewing Logs for Scripts in a Test Suite
      • Viewing Code Coverage Values for Previously Run Scripts
• Using the AutoPilot
  • About the AutoPilot
  • Using the AutoPilot to Run Pilots, Test Suites, and Scripts
    • Running Tests on Your Local Machine
• Testing Code Changes in Visual Studio
  • Overview of the TestCodeChanges Add-In for VisualStudio
  • Setting Up the TestCodeChanges Add-In
  • Preparing to Test Code Changes
  • Using the TestCodeChanges Add-In
    • Starting the TestCodeChanges Add-In
    • Viewing Information in the Test Code Changes Window
      • Viewing and Modifying the Path to the Executable File to Test
      • Viewing Changed Files and the Scripts that Exercise Them
    • Creating and Running a Regression Suite to Test Code Changes
      • Run Results for the Regression Suite
• Using TestFactory Command-Line Arguments
  • TestFactory Command-Line Arguments
    • Logon Arguments
    • Run Arguments
    • Application Mapper Arguments
    • Coverage Dictionary Arguments
    • Control Argument:
  • Command-Line Argument Format
  • Rules for Using TestFactory Command-Line Arguments
• Index