Bug Fixes in TestComplete 14.71

Applies to TestComplete 14.91, last modified on July 20, 2021

The following bugs reported by our customers have been fixed in TestComplete 14.71.

General

  • Fixed: TestComplete (TestExecute) could exit unexpectedly when showing a message informing that a new version of the product is available.

  • Fixed: TestComplete could exit unexpectedly when running a distributed test.

  • Fixed: When a function in a script unit was renamed by using the Rename command, any Keyword Test operation that referred to that function was not updated to use the function’s new name.

Desktop testing

  • Fixed: A tested Qt application could stop responding when a test was simulating user actions over it.

Web testing

  • Fixed: TestComplete was not able to access objects in a CEF-application if the bitness of the application’s main process differed from the bitness of its subprocesses.

Android testing

  • Fixed: TestComplete could fail to instrument, deploy, or launch a tested Android application and reported the “Unable to load the Android application package” error.

  • Fixed: TestComplete could fail to launch a tested Android application if the Android SDK path included spaces.

  • Fixed: TestComplete could fail to launch a tested Android application if the JAVA_HOME environment variable was not set or if the system locale was not set to English.

  • Fixed: TestComplete could exit unexpectedly when trying to connect to a tested Android device or when instrumenting, deploying, or launching a tested Android application.

  • Fixed: A tested Android application instrumented automatically and launched from TestComplete could go background after start.

  • Fixed: On a computer with the non-English system locale, TestComplete could exit unexpectedly when launching a tested Android application instrumented automatically.

  • Fixed: TestComplete could exit unexpectedly when launching a tested Android application.

Mobile web testing

  • Fixed: SmartBear Browser could not access the current GPS location.

BDD testing

  • Fixed: When generating step definitions for a Gherkin feature file, TestComplete unexpectedly interpreted numerical values as parameters.

Name mapping

  • Fixed: When a user tried editing mapping criteria of an object mapped in conditional mode and the object did not exist, TestComplete would show no appropriate warning message.

Integration with other tools

  • Fixed: The Save logs for option of the Enable support for TestComplete tests task was ignored if the Azure DevOps pipeline used a test plan to run tests.

See Also

What's New in TestComplete 14.91
Version History

Highlight search results