Bug Fixes in TestComplete 14.40

Applies to TestComplete 14.72, last modified on December 24, 2020

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

General

  • Fixed: TestComplete could exit unexpectedly when opening a project suite that included invalid log files.

  • Fixed: TestComplete allowed creating projects and project suites with the name too long to work with and then failed to access the project files.

  • Fixed: In some TestComplete panels, pressing Shift unexpectedly scrolled the panel to the currently selected item.

  • Fixed: If a modal window appeared on the screen while a user was interacting with the TestComplete Object Spy, the Object Spy would overlap the modal window making the window inaccessible and the entire TestComplete UI unresponsive.

  • Fixed: TestComplete could exit unexpectedly when a user was exploring object properties via the Object Spy or after the test run was over.

  • Fixed: TestComplete could report an access violation error and exit unexpectedly when a user was exploring values in the Locals and Watch List panels.

  • Fixed: It was not possible to delete auto-completed entries in the Watch Properties dialog.

  • Fixed: TestComplete could unexpectedly modify the project file during the test run.

  • Fixed: The tcHostingProcess.exe process, which is a helper TestComplete process for calling external routines from tests, could exit unexpectedly during the test run.

  • Fixed: Sometimes, a TestComplete instance created by using the Test Runner REST API could not be obtained because the TestComplete service exited unexpectedly.

  • Fixed: The SessionCreator utility did not wait until a user session is created and reported an error.

  • Fixed: If the HASP service was configured to use a non-default port, TestComplete (TestExecute) could not start.

  • Fixed: If a project included user forms with event handlers added, cloning such a project made all event handlers in the resulting project invalid.

  • Fixed: TestComplete could report an access violation error and exit unexpectedly right after running a test.

  • Fixed: TestComplete could exit unexpectedly during the test run.

  • Fixed: TestComplete could report an unexpected error upon closing.

Desktop application testing

  • Fixed: When running a tested application from a test by using the RunAs method, the method posted an unexpected error message to the test log.

  • Fixed: During the test run, a tested Delphi application could exit unexpectedly when a test was modifying the tested application's object string properties.

  • Fixed: When exploring a JavaFX application, the jp2launcher process was missing from the Object Browser.

Web testing

  • Fixed: Sometimes, when mapping objects automatically during the test recording in a web application in Chrome, TestComplete could ignore Name Mapping templates.

  • Fixed: When recording tests in Chrome for a web application that uses large tables, TestComplete could map table elements as immediate children of the Page object making the mapping unreliable and making it take much time to find the mapped object during the test run.

  • Fixed: In Chrome, when simulating user actions, TestComplete could scroll the web page incorrectly.

  • Fixed: TestComplete could stop responding when getting the VisibleOnScreen property of an object in Chrome.

  • Fixed: In Edge, the ClickItem method did not scroll the combo box items to the target item and simulated the click incorrectly.

  • Fixed: A CEF application could exit unexpectedly when being launched from TestComplete.

  • Fixed: TestComplete could fail to test some CEF applications.

  • Fixed: A tested CEF application could throw an error or exit unexpectedly when being run from TestComplete.

  • Fixed: TestComplete could fail to parse the tested web service response.

Mobile testing

  • Fixed: A tested iOS application could exit unexpectedly when a user was exploring it via the Object Browser.

  • Fixed: On Android devices, TestComplete could not simulate touch actions if a transparent full-screen ImageView control was present.

  • Fixed: TestComplete could fail to instrument Android application correctly leaving some controls unavailable to the test engine.

  • Fixed: TestComplete tests could not interact with popups in Android Xamarin.Forms applications.

  • Fixed: TestComplete could not record test input for Android applications.

  • Fixed: Tested Android applications could exit unexpectedly after being instrumented with TestComplete.

  • Fixed: In a Hybrid Android application, the SetText method reported an error if the text to set included a quote character.

  • Fixed: Performance issues occurring when running tests or exploring objects of a Hybrid Android application.

Optical character recognition

  • Fixed: TestComplete could exit unexpectedly when creating an OCR checkpoint.

  • Fixed: If the Intelligent Quality add-on was activated after installing TestComplete (TestExecute), the third-party terms of service agreement confirmation message kept popping up every time when the product was launched.

Name mapping

  • Fixed: When cloning a project with the Name Mapping item added from an external source, the Name Mapping item in the resulting cloned project was invalid.

Checkpoints

  • Fixed: When running a file checkpoint in the update mode, TestComplete reported an unexpected error.

  • Fixed: During the test recording, TestComplete could show the message about a quick checkpoint being added to the test even if the checkpoint was not actually added.

  • Fixed: Quick checkpoints were created for applications that were not added to the list of tested applications if the Record user actions over tested applications only option was enabled.

Test logs

  • Fixed: TestComplete could exit unexpectedly when generating a test log after the test run was over.

  • Fixed: If a test ran longer than 20 hours, the Summary report showed the test execution duration incorrectly.

Keyword tests

  • Fixed: TestComplete could exit unexpectedly when a user was modifying a keyword test that was updated outside of TestComplete.

Script tests

  • Fixed: When exporting JavaScript functions after renaming a script unit, TestComplete could report the "List index out of bounds" error in an infinite loop.

  • Fixed: The aqFileSystem.ExpandFileName method could convert the path relatively to the current path rather than the project path.

  • Fixed: In JavaScript, the Code Completion did not to show functions added to the script unit via the module.exports syntax.

BDD testing

  • Fixed: If a TestComplete project included the OnStartTest event handler, TestComplete would not generate the test results for scenarios run from TestComplete IDE.

  • Fixed: When running BDD tests by a tag, the test engine did not call the BeforeFeature and AfterFeature hooks.

Distributed testing

  • Fixed: The Set Variable Value operation failed to update network suite variables values.

Integration with other tools

  • Fixed: When sending test results to Zephyr for Jira, TestComplete could fail to attach images posted to the test log to the exported results.

  • Fixed: TestComplete could fail to send test results to Zephyr for Jira if there were too many test executions to create.

  • Fixed: Performance issues that occurred if a TestComplete project included test items linked to Azure DevOps test cases.

  • Fixed: TestComplete could not link test items to test cases in localized versions of Team Foundation Server.

  • Fixed: If a TestComplete project included a script unit with a dependency to another script unit missing from the project, an incorrect error message was posted to the test log when the project was run from Azure DevOps.

  • Fixed: When adding a Team Foundation Server to the server list via the Add Team Foundation Server dialog, TestComplete could stop responding.

  • Fixed: When running TestComplete tests by using the TestComplete support plugin for Jenkins, the test start time posted to the TestComplete Test Results report was incorrect.

  • Fixed: When running Ready API tests from TestComplete, TestComplete would preserve the previous test results and show the test status incorrectly.

See Also

What's New in TestComplete 14.72
Version History

Highlight search results