Bug Fixes in TestComplete 14.50

Applies to TestComplete 14.80, last modified on April 21, 2021

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

General

  • Fixed: TestComplete could not be installed if the installer was located in the drive root folder.

  • Fixed: TestComplete could exit unexpectedly on computers with the McAfee antivirus installed.

  • Fixed: TestComplete could exit unexpectedly if custom docking was used.

  • Fixed: Slow loading time of projects containing very large keyword tests, Name Mapping files, log files.

  • Fixed: An error occurred after opening a large project.

  • Fixed: After test recording was paused or stopped, TestComplete could exit unexpectedly.

  • Fixed: An “Out of system resources” error occurred when trying to add a script routine as a test item.

  • Fixed: TestComplete could exit unexpectedly after a user opened several panels.

  • Fixed: Actions in the Code Explorer and TODO panels could cause TestComplete to exit unexpectedly.

  • Fixed: An “Invalid variant type” message appeared sometimes upon hovering over Table variables in the Variables editor.

  • Fixed: Selecting an object from the screen could cause TestComplete to exit unexpectedly.

  • Fixed: Closing the Object Spy during the Point and Fix selection mode caused TestComplete to exit unexpectedly.

  • Fixed: Test items that used tags did not evaluate variables used to specify the tag value.

  • Fixed: The image captured by Regions.GetPicture included the playback indicator.

  • Fixed: The asterisk (*) character was not properly escaped in the recorded item names in ClickItem actions.

  • Fixed: TestComplete could exit unexpectedly after a user added multiple tests in the CrossBrowserTesting manager.

  • Fixed: Buttons on user forms did not use the colors specified in button properties.

  • Fixed: A script extension without icon caused TestComplete to exit unexpectedly.

  • Fixed: Errors could occur when TestComplete was closed.

Desktop application testing

  • Fixed: An incorrect error message was displayed if an MFC application with StingrayObjectiveGrid controls was missing debug information.

  • Fixed: The Object Spy could not select objects in Java applications that contained a transparent MatlabOpenGLWindow window on top of other content.

Web testing

  • TestComplete now retries connecting to the CrossBrowserTesting several times before timing out.

  • Fixed: SetText did not fire event handlers for React input fields.

  • Fixed: SetText did not fire the change event for text boxes in Internet Explorer.

  • Fixed: Click did not work in certain Safari versions on macOS.

  • Fixed: FindElement could not find objects inside the Shadow DOM during playback.

  • Fixed: The Object Spy could not select objects on web pages in Chrome if one of the intermediate element containers had zero size.

  • Fixed: The Object Spy could not select objects in popup windows in Internet Explorer.

  • Fixed: TestComplete could not recognize objects in applications created with EO.WebBrowser if the eowp.exe file was renamed or if the EO assemblies were in GAC.

  • Fixed: getComputedStyle() returned an error if called via the document.defaultView object rather than via the Script object.

  • Fixed: getComputedStyle() returned an error if the target element was in an IFRAME.

  • Fixed: getComputedStyle() returned an empty string if the second parameter (pseudo-element to match) was an empty string.

Mobile testing

  • Fixed: The Keys action did not work for web page elements on some mobile devices.

  • Fixed: The tested iOS application exited unexpectedly when TestComplete tried to mock GPS coordinates.

  • Fixed: TestComplete could not simulate touch actions on some ImageView controls.

  • Fixed: TestComplete could not identify web objects in Cordova-based Hybrid Android applications.

  • Fixed: The address bar in SmartBearBrowser did not update after some web page redirections even though the new page was actually displayed.

Name Mapping

  • Fixed: Moving a mapped object to a higher level in the Name Mapping editor could cause TestComplete to exit unexpectedly.

  • Fixed: Changes in Name Mapping templates were not saved immediately, but only when TestComplete was closed.

  • Fixed: WaitAliasChild slowed down the tested application.

  • TestComplete exited unexpectedly if AddNamedChild was called with the Properties parameter containing a Python array.

  • Fixed: Some Android application objects could be automatically mapped with empty property names which caused TestComplete to exit unexpectedly.

Checkpoints

  • Fixed: Table checkpoints containing floating-point values could fail even though the values appeared to be the same.

  • Fixed: Property checkpoints failed if the value included Unicode characters such as bullet points or smart quotes.

  • Fixed: Black background in the File Comparison Result panel in test logs.

  • Fixed: Table checkpoints could not be updated by the Update the … checkpoint link in the test logs if the corresponding test object did not exist.

Test logs

  • Fixed: Clicking “Export Summary as JUnit” in the Summary report could cause TestComplete to exit unexpectedly.

  • Fixed: Incorrect data in the Summary report exported by the /ExportSummary command-line argument.

  • Fixed: Missing the root.xml file in logs exported by the /ExportLogToXMLAlso command-line argument.

  • Fixed: Logs exported to MHT had incorrect external links in message details.

Keyword tests

  • Fixed: Performance issues occurring when using Table variables in code expressions.

  • Fixed: An error occurred when editing operation values containing new line characters (#13#10) in DelphiScript projects.

  • Fixed: When a Run Script Routine operation was copied in a keyword test in a Python project, and a different routine was selected, the editor displayed the argument list for the old routine instead of the new one.

Code Editor

  • Fixed: The incorrect cursor position after using the Find Usages and Rename commands in the Code Editor.

  • Fixed: When a keyword was selected in a script using text selection, F1 did not look up the help page for this keyword and opened a generic help page instead.

BDD testing

  • Fixed: BDD step definitions could not be found if they were in different files.

Distributed testing

  • Fixed: If a network suite job was run as a test item, and the test item was configured with a timeout and On Error=Stop current item, and the job execution time exceeded the timeout, then the entire project was stopped instead of just this test item.

Test debugging

  • Fixed: The Locals and Watches panels did not show the variable values in certain cases.

  • Fixed: TestComplete could exit unexpectedly during keyword test debugging if the Locals panel was active.

  • Fixed: TestComplete could exit unexpectedly during script debugging.

Integration with other tools

  • TestComplete now retries connecting to the Zephyr server upon encountering network errors.

  • Fixed: When creating issues in Jira instances with more than 500 users, user selection fields displayed only a partial user list.

  • Fixed: TestComplete (TestExecute) kept the project files on Azure DevOps agents locked after pipeline execution which caused errors during subsequent pipeline runs.

See Also

What's New in TestComplete 14.80
Version History

Highlight search results