Home
Rational® Functional Tester
Test Author Guide
This guide describes how to create test scripts and enhances them by applying different test elements such as dataset, variables, and verification points.
Testing in the Functional Test perspective
When you develop Java, HTML, or Terminal-based applications, you can use IBM® Rational® Functional Tester to create traditional functional tests for these applications. You must first record the tests and then use Rational Functional Tester to run the tests before you can view the test results.
Preparing the functional test environment
This section describes the tasks you must perform to configure the functional test environment.
Flex applications testing process
The testing process is based on the tasks that Flex developers and testers perform. The process for automating functional tests of Flex applications differs, depending on the way developers create the application under test.
Testing Rational® Functional Tester enabled Flex applications
Developers can enable the Flex applications for testing by building the Flex application with Rational® Functional Tester agent and Flex automation framework libraries. After compilation, the developer must create an HTML wrapper that embeds the enabled Flex application and provide the application on a web server or on a local test computer for testing.
Configuring Flex applications
You can configure the Flex application with the Rational® Functional Tester agent and Flex automation framework libraries.
Configuring Flex application using tools
You can configure your Flex application for functional testing using the tools like command-line compiler and Flex Builder.

Rational® Functional Tester
- Release Notes
  This document contains information about what's new, installation instructions, known problems in and contact information of IBM Customer Support.
- System Requirements
  This document includes information about hardware and software requirements for IBM® Rational® Functional Tester.
- Getting Started Guide
  This guide provides an overview of Rational® Functional Tester. You can find the task flows to get you started with Rational Functional Tester. This guide is intended for new users.
- Tutorials
  This section contains the tutorials which explains the main features of Rational® Functional Tester.
- Samples
  This section describes about the sample project which can be used with Rational® Functional Tester to test the functionality of an application.
- Administrator Guide
  This guide describes how to install IBM® Rational® Functional Tester software. After you install the software, you can perform administration tasks such as license configuration and integration with other products. This guide is intended for administrators.
- Test Author Guide
  This guide describes how to create test scripts and enhances them by applying different test elements such as dataset, variables, and verification points.
  - Testing in the UI Test perspective
    When you develop web applications, Windows-based applications, or mobile applications, you can use IBM® Rational® Functional Tester to create functional tests for these applications. You must first record the tests and then use Rational Functional Tester to run the tests before you can view the test results.
  - Testing in the Functional Test perspective
    When you develop Java, HTML, or Terminal-based applications, you can use IBM® Rational® Functional Tester to create traditional functional tests for these applications. You must first record the tests and then use Rational Functional Tester to run the tests before you can view the test results.
    - Preparing the functional test environment
      This section describes the tasks you must perform to configure the functional test environment.
      - Automatically enabled environment for functional testing
        From Rational® Functional Tester version 8.2.2 onwards, Rational Functional Tester automatically enables the environments for functional testing.
      - Before you record
        Before you can start recording functional test scripts, perform the following setup and configuration tasks:
      - Enabling Java environments
        You need to enable Java™ environments before you can use Rational® Functional Tester to test Java applications. Rational Functional Tester is shipped with a JRE that is automatically enabled during your installation. The JRE is called "Default JRE." To enable other JREs, or if you install a new JRE, you must run the enabler again.
      - Enabling web browsers
        To test the HTML applications in Rational® Functional Tester, you must enable web browsers. You can then record and play back tests by using the browsers that you enabled.
      - Enabling multi-window support to test Functional HTML tests
        You can enable multi-window support for Functional HTML tests to record the actions that you perform in multiple windows of the same browser instance. The playing back of the test finds controls from all the active windows of the browser instance. You can use this capability when an HTML application opens a new browser window after you perform an action from the parent window of the application.
      - Preparing for functional testing in the Google Chrome browser
        You can use Rational® Functional Tester to test HTML applications in the Google Chrome browser. To do this, you must enable the Google Chrome browser and add the Rational Functional Tester extension for Google Chrome™ to the browser.
      - Enabling the Eclipse non-p2 based applications for functional testing
        If the application under test is a non-p2 Eclipse based application, you can enable the Eclipse platform for functional testing using the Eclipse enabler.
      - Enabling the Eclipse p2- based applications for functional testing
        If the application-under-test is based on p2-based Eclipse, you must enable the Eclipse platform for testing using the Eclipse Software Updates feature.
      - Enabling stand-alone Standard Widget Toolkit applications
        You must enable stand-alone Standard Widget Toolkit (SWT) support before using Rational® Functional Tester to test SWT applications in the application under test.
      - Configuring applications for testing
        You must configure your Java™, HTML, VB.NET, SAP GUI, Flex or Windows® applications for functional testing by providing the name, path, and other information that Rational® Functional Tester uses to start and run the application. You use the Application Configuration Tool to configure applications.
      - Configuring Java environments for testing
        You need to configure your JREs for Java™ testing with Rational® Functional Tester. This provides path, run options, and other information that Rational Functional Tester needs to access and use your JREs. You use the Java Environments tab of the Enable Environments dialog box to do this.
      - Configuring browsers for testing
        You need to configure your browsers for HTML testing with Rational® Functional Tester. This provides name, path, and other information that Rational Functional Tester needs to access and use your browsers. You use the Web Browsers tab of the Enable Environments dialog box to do this.
      - Browser enablement diagnostic tool
        The Browser Enablement Diagnostic Tool is used to diagnose problems you might have with enabling your browser for HTML testing. The tool will diagnose the enablement problem and report how to solve the problem.
      - Enabling the Java plug-in of a browser
        The Oracle Java™ plug-in of your browser(s) must be enabled in order for some applets to be tested, and for the View Results link that launches the Verification Point Comparator from the HTML log to work properly. If you get an error regarding the plug-in during HTML testing, or when trying to launch the Comparator, use the following steps to fix the problem.
      - Adding references to external resources
        Functional test scripts or projects may refer to or use external resources like the DLLs in .Net IDE or JAR files in Eclipse IDE. To enable the scripts or projects to use these files, you must add references to these files in Rational® Functional Tester.
      - Setting up the environment for testing AJAX-based web applications
        You can test AJAX-based applications in two different ways; by setting the Auto Trace option to true or by setting the Auto Trace option to false. If you set the Auto Trace option to false, you must use the Rational® Functional Tester APIs for AJAX in the script by manually inserting them.
      - Enabling SAP client and server
        To use Rational® Functional Tester to test SAP applications, you must enable the SAP client and SAP server.
      - Enabling SAP GUI for HTML applications for functional testing
        Objects in SAP GUI for HTML applications contain many dynamically-changing properties, for example .url, .href, and .id. While playing back functional test scripts against these applications, the value of one or more object recognition properties may change causing a high ScriptAssure score that results in script failure. Rational® Functional Tester provides a mechanism to convert the recognition property value to a regular expression for those values that change dynamically. Finding each object's dynamic recognition property and converting it into a regular expression becomes cumbersome while testing SAP GUI for HTML applications.
      - Enabling applications with WebDynPro controls for functional testing
        When you playback functional test scripts to test HTML applications with WebDynPro controls, you may get object not found exception or a weak recognition warning even if the control exists.
      - Enabling the GEF application
        You must enable the GEF support before using Rational® Functional Tester to test GEF objects on the application under test.
      - Enabling response time breakdown
        You can enable response time breakdown to see how much time is spent in each part of the application as the test runs. To collect response time breakdown, the data collection infrastructure must be installed and running on all computers that are used in the distributed application under test.
      - Flex applications testing process
        The testing process is based on the tasks that Flex developers and testers perform. The process for automating functional tests of Flex applications differs, depending on the way developers create the application under test.
        Setting up the development environment for Flex applications
        The developer must set up the development environment before enabling the Flex application for testing with Rational® Functional Tester.
        Setting up the test environment for testing Flex applications
        A correct environment setup for testing Flex applications helps ensure reliable functional testing results. The test environment is typically set up by the testers on the test computer.
        Testing Rational® Functional Tester enabled Flex applications
        Developers can enable the Flex applications for testing by building the Flex application with Rational® Functional Tester agent and Flex automation framework libraries. After compilation, the developer must create an HTML wrapper that embeds the enabled Flex application and provide the application on a web server or on a local test computer for testing.
        Configuring Flex applications
        You can configure the Flex application with the Rational® Functional Tester agent and Flex automation framework libraries.
        Configuring Flex application using the user interface
        You can configure the Flex application for functional testing using the user interface.
        Configuring Flex application using tools
        You can configure your Flex application for functional testing using the tools like command-line compiler and Flex Builder.
        Creating an HTML wrapper
        The developer creates an HTML wrapper after compiling the Flex application with the Rational® Functional Tester agent and Flex automation testing libraries.
        Providing enabled Flex applications for testing
        Developers can deploy a Flex application that is enabled for Rational® Functional Tester for testing on a web server or provide the files for testing locally.
        Testing an enabled Flex application that is deployed on a web server
        Testers can test a Flex application that is enabled for Rational® Functional Tester and is deployed on a web server.
        Testing enabled Flex applications on a local test computer
        Testers can test a Flex application that is embedded in an HTML wrapper on a local test computer.
        Test Flex applications that are not enabled using Rational® Functional Tester
        Developers can enable the RuntimeLoading component for Flex applications and provide the application on a web server for testing.
      - Importing and exporting configuration and customization files
        You can configure and customize files in the configuration and the customization directories. The configuration files contains information such as the application that must be configured for testing. However, the customization files contain information about the external jar files used in your project, customization of any recognition properties, and third-party proxy extensions. You can export these files and later deploy them using the export and import utility. The default location for the configuration and customization file is C:\ProgramData\IBM\RFT . For example: If you want to use the same configuration and customization files on different computers, you can archive these files and later deploy them using this utility.
      - Setting preferences
        You use the Preferences dialog box to customize Rational® Functional Tester in a number of different areas, such as settings for time options; colors for the Verification Point Editor, the Verification Point Comparator, and the Object Map Editor; highlight color for test objects; operating system; playback; delays; log; playback monitor; ScriptAssure(TM); recorder; recording monitor; and the workbench.
    - Managing functional test projects
      A functional test project stores application test assets such as scripts, object maps, verification point baseline files, and script templates. You must create a functional test project before you can record scripts.
    - Working with functional test scripts (Windows-only)
      This section describes the process of creating functional test scripts to test your applications.
    - Working with verification points
      Verification points verify that a certain action has taken place, or verify the state of a control or an object. When you create a verification point, you are capturing information about a control or an object in the application to establish this as baseline information for comparison during playback.
    - Driving functional tests with external data
      This section describes techniques you can use to data-drive functional tests with external data.
    - Managing functional test assets
      You can integrate Rational® Functional Tester with IBM® Rational ClearCase® or Rational Team Concert™ and manage functional test assets using any of these source control management tools.
    - Testing terminal-based applications
      Use the Rational® Functional Tester Terminal-based Applications feature to create test scripts and automate your host-application test cases. You can test host attributes, host field attributes, and screen-flow through a host application. It uses terminal verification points and properties, as well as synchronization code to identify the readiness of terminal for user input.
    - Troubleshooting issues
      You can find information about the issues or problems that you might encounter while working with the Functional Test perspective in Rational® Functional Tester. Details about issues, their causes and the resolutions that you can apply to fix the issues are described.
  - Extending the UI Test perspective with custom code
    You can use custom code to extend the default Web UI testing capabilities. You can write custom Java™ code and call the code from the test. You can also specify that results from the tests that are affected by your custom code to be included in reports.
  - Extending the Functional Test perspective
    You can use custom code to extend the default functional testing capabilities. You can write custom code and call the code from the test. You can also specify that results from the tests that are affected by your custom code to be included in reports.
  - Experimental Features
    Rational® Functional Tester contains a set of pre-releases that enable you to test various experimental features. These experimental features, while still in progress, are introduced early in the release to seek your feedback on its overall functionality and performance. You can play around with these capabilities before they are made available and supported as a general feature in an upcoming release.
- Test Execution Specialist Guide
  This guide describes how to automate the playback of the tests by using different methods such as Docker, IBM® Cloud Private, Jenkins and so on. The test results can be pushed to Rational® Test Control Panel.
- Test Manager Guide
  This guide describes how to keep track of the performance of the application by evaluating the test results. Following topics cover how you can work with the test results.
- Troubleshooting
  This guide describes how to analyze and resolve some of the common problems that you might encounter while you work with Rational® Functional Tester.
- Reference Guide
  This guide describes the additional topics to gain more knowledge about Rational® Functional Tester.
- All Guides (PDF)
  You can find the link to view or download the content of the release notes, system requirements, and persona guides of IBM® Rational® Functional Tester as a PDF file.
- Security Considerations
  You can take certain actions to ensure that your installation is secure, customize your security settings, and set up user access controls.
- Notices
  This document provides information about copyright, trademarks, terms and conditions for the product documentation.

Configuring Flex application using tools

You can configure your Flex application for functional testing using the tools like command-line compiler and Flex Builder.

Using the command-line compiler to enable Flex applications

Developers can compile a Flex application with the IBM® Rational® Functional Tester agent and Flex Automation Libraries from a command line and enable the application for functional testing.

About this task

Compile the Flex application using the Rational® Functional Tester agent and Flex Automation Libraries by running the following command.

To compile and enable a Flex 2.0 application for functional testing:

At the command line, type the following, and press Enter:

"flex builder installation directory\Flex SDK 2\bin\mxmlc" -include-libraries+="flex builder installation directory\Flex SDK 2\frameworks\libs\automation.swc;flex builder installation directory\frameworks\libs\automation_agent.swc;flex builder installation directory\Flex SDK 2\frameworks\libs\automation_charts.swc;functional tester installation directory\FunctionalTester\bin\rft.swc;functional tester installation directory\FunctionalTester\bin\rftProp.swc" Test.mxml

To compile and enable a Flex 3.0 application for functional testing:

At a command line, type the following command, and press Enter. In the command, Test.mxml is the name of your .mxml file.

"flex builder installation directory\Flex Builder 3\sdks\3.0.0\bin\mxmlc.exe"-include-libraries+="flex builder installation directory\Flex Builder 3\sdks\3.0.0\frameworks\libs\automation.swc;flex builder installation directory\Flex Builder 3\sdks\3.0.0\frameworks\libs\automation_agent.swc;flex builder installation directory\Flex Builder 3\sdks\3.0.0\frameworks\libs\automation_dmv.swc;flex builder installation directory\rftFlex3.0.swc;functional tester installation directory\rftProp_Flex3.0.swc" Test.mxml

To compile and enable a Flex 3.2 application for functional testing:

At a command line, type the following command, and press Enter:

"flex builder installation directory\Flex Builder 3\sdks\3.2.0\bin\mxmlc.exe"-include-libraries+="flex builder installation directory\Flex Builder 3\sdks\3.2.0\frameworks\libs\automation.swc;flex builder installation directory\Flex Builder 3\sdks\3.2.0\frameworks\libs\automation_agent.swc;flex builder installation directory\Flex Builder 3\sdks\3.2.0\frameworks\libs\automation_dmv.swc;flex builder installation directory\rftFlex3.0.swc;functional tester installation directory\rftProp_Flex3.0.swc" Test.mxml

To compile and enable a Flex 3.3 application for functional testing:

At a command line, type the following command, and press Enter:

"flex builder installation directory\Flex Builder 3\sdks\3.3.0\bin\mxmlc.exe"-include-libraries+="flex builder installation directory\Flex Builder 3\sdks\3.3.0\frameworks\libs\automation.swc;flex builder installation directory\Flex Builder 3\sdks\3.3.0\frameworks\libs\automation_agent.swc;flex builder installation directory\Flex Builder 3\sdks\3.3.0\frameworks\libs\datavisualization.swc;flex builder installation directory\rftFlex3.0.swc;functional tester installation directory\rftProp_Flex3.0.swc" Test.mxml

Note: The above command has Flex 3.3 SDK deployed at flex builder installation directory\Flex Builder 3\sdks\ with directory as 3.3.0.

To compile and enable a Flex 3.4 application for functional testing:

At a command line, type the following command, and press Enter:

"flex builder installation directory\Flex Builder 3\sdks\3.4.0\bin\mxmlc.exe"-include-libraries+="flex builder installation directory\Flex Builder 3\sdks\3.4.0\frameworks\libs\automation.swc;flex builder installation directory\Flex Builder 3\sdks\3.4.0\frameworks\libs\automation_agent.swc;flex builder installation directory\Flex Builder 3\sdks\3.4.0\frameworks\libs\datavisualization.swc;flex builder installation directory\rftFlex3.0.swc;functional tester installation directory\rftProp_Flex3.0.swc" Test.mxml

Note: The above command has Flex 3.4 SDK deployed at flex builder installation directory\Flex Builder 3\sdks\ with directory as 3.4.0.

To compile and enable a Flex 3.5 application for functional testing:

At a command line, type the following command, and press Enter:

"flex builder installation directory\Flex Builder 3\sdks\3.5.0\bin\mxmlc.exe"-include-libraries+="flex builder installation directory\Flex Builder 3\sdks\3.5.0\frameworks\libs\automation.swc;flex builder installation directory\Flex Builder 3\sdks\3.5.0\frameworks\libs\automation_agent.swc;flex builder installation directory\Flex Builder 3\sdks\3.5.0\frameworks\libs\datavisualization.swc;flex builder installation directory\rftFlex3.0.swc;functional tester installation directory\rftProp_Flex3.0.swc" Test.mxml

Note: The above command has Flex 3.5 SDK deployed at flex builder installation directory\Flex Builder 3\sdks\ with directory as 3.5.0.

To compile and enable a Flex 4.0 application for functional testing:

At a command line, type the following command, and press Enter:

"flash builder installation directory\Flash Builder 4\sdks\4.0.0\bin\mxmlc.exe"-include-libraries+="flash builder installation directory\Flash Builder 4\sdks\4.0.0\frameworks\libs\automation.swc;flash builder installation directory\Flash Builder 4\sdks\4.0.0\frameworks\libs\automation_agent.swc;flash builder installation directory\Flash Builder 4\sdks\4.0.0\frameworks\libs\datavisualization.swc;flash builder installation directory\Flash Builder 4\sdks\4.0.0\frameworks\libs\automation_spark.swc;flash builder installation directory\rftFlex4.0.swc;functional tester installation directory\rftProp_Flex4.0.swc" Test.mxml

Note:

The above command has Flex 4.0 SDK deployed at flash builder installation directory\Flash Builder 4\sdks\ with directory as 4.0.0.
The automation_spark.swc file has been included for Spark controls.

To compile and enable a Flex 4.1 application for functional testing:

At a command line, type the following command, and press Enter:

"flash builder installation directory\Flash Builder 4\sdks\4.1.0\bin\mxmlc.exe"-include-libraries+="flash builder installation directory\Flash Builder 4\sdks\4.1.0\frameworks\libs\automation.swc;flash builder installation directory\Flash Builder 4\sdks\4.1.0\frameworks\libs\automation_agent.swc;flash builder installation directory\Flash Builder 4\sdks\4.1.0\frameworks\libs\datavisualization.swc;flash builder installation directory\Flash Builder 4\sdks\4.0.0\frameworks\libs\automation_spark.swc;flash builder installation directory\rftFlex4.0.swc;functional tester installation directory\rftProp_Flex4.0.swc" Test.mxml

Note:

The above command has Flex 4.1 SDK deployed at flash builder installation directory\Flash Builder 4\sdks\ with directory as 4.1.0.
The automation_spark.swc file has been included for Spark controls.

To compile and enable a Flex 4.5 application for functional testing:

At a command line, type the following command, and press Enter:

"flash builder installation directory\Flash Builder 4\sdks\4.5.0\bin\mxmlc.exe"-include-libraries+="flash builder installation directory\Flash Builder 4\sdks\4.5.0\frameworks\libs\automation.swc;flash builder installation directory\Flash Builder 4\sdks\4.5.0\frameworks\libs\automation_agent.swc;flash builder installation directory\Flash Builder 4\sdks\4.5.0\frameworks\libs\datavisualization.swc;flash builder installation directory\Flash Builder 4\sdks\4.0.0\frameworks\libs\automation_spark.swc;flash builder installation directory\rftFlex4.0.swc;functional tester installation directory\rftProp_Flex4.0.swc" Test.mxml

Note:

The above command has Flex 4.5 SDK deployed at flash builder installation directory\Flash Builder 4\sdks\ with directory as 4.5.0.
The automation_spark.swc file has been included for Spark controls.

Note: The datavisualization.swc component is separately available at the Adobe site.

The default Flex Builder installation directory on Windows is C:\Program Files\Adobe.

This command is also available as a batch file with Rational® Functional Tester installed. Testers can provide this batch file to the developer to enable the Flex application for testing. Provide the flex application source code filename as the parameter to the batch file.

The batch file is available in product installation directory\Functional Tester\Flex folder.

Example

For example, if your .mxml file is Test.mxml, the command to run the batch file is as follows:

For Flex 2.0:

buildapplicationwithadaptor.bat Test.mxml

For Flex 3.0:

buildapplicationwithFlex3adaptor.bat Test.mxml

For Flex 3.2:

buildapplicationwithFlex32adaptor.bat Test.mxml

Using Flex Builder to enable Flex applications

Developers can use the Flex Builder to make Flex applications ready for functional testing.

About this task

Flex Builder is useful for developers who want to develop Flex applications (.swf files) that are ready for functional testing. To set up Flex Builder to support Flex automation and functional testing:

Procedure

Start Flex Builder.
Create a new Flex project.
Select the Flex project in the navigator.
Click Select Project > Properties > Flex Compiler.

Type the following argument in the Additional compiler arguments field:

For Flex 2.0:

-include-libraries flex builder installation directory\Flex SDK 2\frameworks\libs\automation.swc�? flex builder installation directory\Flex SDK\frameworks\libs\automation_agent.swc�? flex builder installation directory\Flex SDK\frameworks\libs\automation_charts.swc functional tester installation directory\Functional Tester\bin\rft.swc�? functional tester installation directory\Functional Tester\bin\rftProp.swc�?

Note: In Flex 2.0, the automation_charts.swc file is required only if your application contains charting controls. The include-libraries compiler option is relative to the Flex Builder installation directory. The default Windows location is C:\Program Files\Adobe\Flex Builder.

For Flex 3.0:

-include-libraries flex builder installation directory\Flex Builder 3\sdks\3.0.0\frameworks\libs\automation.swc�? flex builder installation directory\Flex Builder 3\sdks\3.0.0\frameworks\libs\automation_agent.swc�? flex builder installation directory\Flex Builder 3\sdks\3.0.0\frameworks\libs\automation_dmv.swc functional tester installation directory\rftFlex3.0.swc functional tester installation directory\rftProp_Flex3.0.swc

For Flex 3.2:

-include-libraries flex builder installation directory\Flex Builder 3\sdks\3.2.0\frameworks\libs\automation.swc�? flex builder installation directory\Flex Builder 3\sdks\3.2.0\frameworks\libs\automation_agent.swc�? flex builder installation directory\Flex Builder 3\sdks\3.2.0\frameworks\libs\automation_dmv.swc functional tester installation directory\rftFlex3.0.swc functional tester installation directory\rftProp_Flex3.0.swc

For Flex 3.3:

-include-libraries flex builder installation directory\Flex Builder 3\sdks\3.3.0\frameworks\libs\automation.swc�? flex builder installation directory\Flex Builder 3\sdks\3.3.0\frameworks\libs\automation_agent.swc�? flex builder installation directory\Flex Builder 3\sdks\3.3.0\frameworks\libs\automation_dmv.swc functional tester installation directory\rftFlex3.0.swc functional tester installation directory\rftProp_Flex3.0.swc

For Flex 3.4:

-include-libraries flex builder installation directory\Flex Builder 3\sdks\3.4.0\frameworks\libs\automation.swc�? flex builder installation directory\Flex Builder 3\sdks\3.4.0\frameworks\libs\automation_agent.swc�? flex builder installation directory\Flex Builder 3\sdks\3.4.0\frameworks\libs\datavisualization.swc functional tester installation directory\rftFlex3.0.swc functional tester installation directory\rftProp_Flex3.0.swc

For Flex 3.5:

-include-libraries flex builder installation directory\Flex Builder 3\sdks\3.5.0\frameworks\libs\automation.swc�? flex builder installation directory\Flex Builder 3\sdks\3.5.0\frameworks\libs\automation_agent.swc�? flex builder installation directory\Flex Builder 3\sdks\3.5.0\frameworks\libs\datavisualization.swc functional tester installation directory\rftFlex3.0.swc functional tester installation directory\rftProp_Flex3.0.swc

For Flex 4.0:

Note: You can include the automation_spark.swc for Spark controls.

-include-libraries flash builder installation directory\Flash Builder 4\sdks\4.0.0\frameworks\libs\automation.swc�? flash builder installation directory\Flash Builder 4\sdks\4.0.0\frameworks\libs\automation_agent.swc�? flash builder installation directory\Flash Builder 4\sdks\4.0.0\frameworks\libs\datavisualization.swc�? flash builder installation directory\Flash Builder 4\sdks\4.0.0\frameworks\libs\automation_spark.swc functional tester installation directory\rftFlex4.0.swc functional tester installation directory\rftProp_Flex4.0.swc

For Flex 4.1:

Note: You can include the automation_spark.swc for Spark controls.

-include-libraries flash builder installation directory\Flash Builder 4\sdks\4.1.0\frameworks\libs\automation.swc�? flash builder installation directory\Flash Builder 4\sdks\4.1.0\frameworks\libs\automation_agent.swc�? flash builder installation directory\Flash Builder 4\sdks\4.1.0\frameworks\libs\datavisualization.swc�? flash builder installation directory\Flash Builder 4\sdks\4.1.0\frameworks\libs\automation_spark.swc functional tester installation directory\rftFlex4.0.swc functional tester installation directory\rftProp_Flex4.0.swc

Elements in italics are variables and depend on your directory structure.

Click OK to save your changes.
Click OK.
The Properties dialog box closes.
Compile your Flex application.