Deploying the Runtime loader components

You must deploy the Runtime loader components to test Flex applications that are not compiled using the HCL OneTest™ UI agent and Flex automation framework libraries.

About this task

The following steps are for Flex 2.0 applications. Configuring and testing Flex 3.0, 3.2, 3.3, 3.4, 3.5, 4.0, 4.1 and 4.5 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
  • RunTimeLoaderFlex45.swf and RuntimeLoadingTestFlex45.html for Flex 4.5
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 HCL OneTest UI, the developer needs the Runtime loader source file and the HCL OneTest UI 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 HCL OneTest UI agent and Flex automation framework libraries, perform the following steps:

Procedure

  1. Deploy the RuntimeLoadingTest.html and RuntimeLoader.swf files from the functional tester installation directory\FunctionalTester\Flex directory to the web server.
  2. Provide the URL of RuntimeLoadingTest.html page to the testers, for example, http://localhost/RuntimeLoadingTest.html?automationswfurl=applicationtotest.swf, where applicationtotest.swf is the name of the Flex application to be tested.
Feedback