You must deploy the Runtime loader components to test Flex
applications that are not compiled using the IBM Rational Functional Tester agent and Flex automation
framework libraries.
About this task
The following steps are for Flex 2.0 applications. Configuring
and testing Flex 3.0, Flex 3.2 , Flex 3.3, Flex 3.4, Flex 3.5, Flex
4.0 and Flex 4.1 applications is similar to Flex 2.0 except that you
use these files:
- RunTimeLoaderFlex30.swf and RuntimeLoadingTestFlex30.html for
Flex 3.0
- RunTimeLoaderFlex32.swf and RuntimeLoadingTestFlex32.html for
Flex 3.2
- RunTimeLoaderFlex33.swf and RuntimeLoadingTestFlex33.html for
Flex 3.3
- RunTimeLoaderFlex34.swf and RuntimeLoadingTestFlex34.html for
Flex 3.4
- RunTimeLoaderFlex35.swf and RuntimeLoadingTestFlex35.html for
Flex 3.5
- RunTimeLoaderFlex40.swf and RuntimeLoadingTestFlex40.html for
Flex 4.0
- RunTimeLoaderFlex41.swf and RuntimeLoadingTestFlex41.html for
Flex 4.1
Note: Testers can also deploy the necessary files
to a web server, provided that testers can access the server. Although
developers might not be familiar with IBM Rational Functional Tester, the developer needs
the Runtime loader source file and the IBM Rational Functional Tester agent to enable and deploy
the Flex application. Testers need to provide these files to the developer.
To
deploy the Runtime loader components and enable testing of applications
that are not compiled using IBM Rational Functional Tester agent
and Flex automation framework libraries, perform the following steps: