Limitations on Testing with the Debug Version of Flash Player

Applies to TestComplete 14.92, last modified on September 16, 2021
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.

There are some known limitations on testing applications with the debug version of Adobe Flash Player:

  • The debug version of Flash Player cannot be installed in Microsoft Edge and Internet Explorer on Windows 10.

    To work around this limitation, you can do any of the following:

    • Test your Flash and Flex applications in other supported web browsers (for example, in Firefox or Google Chrome) on Windows 10.

    • Test your Flash or Flex application in Internet Explorer on Windows 8.

    • Use other approaches to test Flash and Flex applications. For example, you can recompile your application with the FlexClient library. See Which Testing Approach to Choose.

  • The debug version of Flash Player supports only Flash and Flex applications created with ActionScript 3.0. To test applications created with earlier versions of ActionScript, you can use only the Microsoft Active Accessibility (MSAA) engine (see Testing Flash and Flex Applications via the MSAA Engine).

  • We do not recommend that you use the debug version of Flash Player to test applications compiled with the TestComplete FlexClient library, as this may cause some errors when testing such applications.

  • SWF movies can be protected from running by modules preloaded by Flash Player. You would not be able to test such movies.

  • When testing a Flash or Flex application running in Mozilla Firefox, the application’s wmode parameter must be set to opaque. If this parameter is set to window or transparent, TestComplete will not be able to test the application in Firefox.

    This restriction does not apply to applications running in Microsoft Internet Explorer. For more information, see Configuring Window Mode.

  • Some add-ons (for instance, Flash Debugger) can overwrite the mm.cfg file that contains settings of Flash Player. This may cause certain issues with testing Flash and Flex applications. To avoid problems, disable the add-ons. See Configuring Adobe Flash Player for instructions on disabling the Flash Debugger add-on.

  • On Windows 8 and Windows Server 2012, you can test Flash and Flex applications running in Internet Explorer only if Flash Player 13 or later is installed.

See Also

Testing Flash and Flex Applications with the Debug Version of Flash Player
Testing Flash and Flex Applications with the Debug Version of Flash Player - Overview

Highlight search results