 |
Flash Player has reached end of life on December 31, 2020. Support for Flash and Flex applications is now deprecated in TestComplete and will be removed in a future release. |
The information in this topic applies to web tests that locate web objects by using internal identification properties provided by TestComplete and run in local environments.
In order to get access to Flash or Flex applications’ internals using the Runtime Loader helper utility, you have to run the tested application under the Runtime Loader utility. To prepare your application properly, you have to do the following:
1. Copy Runtime Loader Files to the Tested Server1. Copy Runtime Loader Files to the Tested Server
In order for Runtime Loader to be able to load your Flash or Flex application successfully, the Loader’s file must reside on the computer where the tested application resides.
Copy Runtime Loader files from the <TestComplete>\Open Apps\Flex\RuntimeLoader folder to the computer where the application to be tested resides. If the application is located on a web server, deploy Runtime Loader to that server. We recommend that you put Runtime Loader’s files to the same folder where the tested application’s SWF file resides.
If the location of your application does not change, you can copy Runtime Loader files only once when you start creating tests for your application. There is no need to copy them before each test.
2. Use RuntimeLoader.html as Start Page
Runtime Loader exposes objects of those Flash and Flex applications that were launched by it, so you should make the RuntimeLoader.html web page the start page for your tests. For a detailed description of how to open the page and specify the tested application manually and how to automate this process, see Running Tested Applications With Runtime Loader.
See Also
Preparing Flash and Flex Applications for Testing with the Runtime Loader Utility