Bug Fixes in TestComplete 12.42

Fixed: TestComplete could display the "The action key is duplicated" error on opening multiple log tabs.

Fixed: The Test Indicator could interfere with the test run (for instance, it could be captured by a region checkpoint or it could overlap an area where user actions were to be simulated).

Fixed: TestComplete could exit unexpectedly when creating Quick Checkpoints for objects with Null property values.

Fixed: TestComplete converted date and time values in tested web service responses incorrectly.

Fixed: The Sys.OSInfo.VMWare property returned an incorrect value on VMWare virtual machines.

Fixed: TestComplete could exit unexpectedly when recording or running tests.

Fixed: TestComplete reported the "Unable to create an item" error when exporting test results to Microsoft Visual Studio Team System.

Fixed: A tested Qt application could exit unexpectedly during the test run if two versions of the same Qt library were loaded in the application.

Fixed: If custom language settings were specified in the operating system, a tested application could exit unexpectedly when the Keys method was used.

Fixed: When running tests in the Chrome web browser, TestComplete could not select items from a drop-down list in the tested web application.

Fixed: TestComplete could not navigate to a web page in Edge and reported the “Environment is incorrect” error if Edge had the AdBlock extension installed and enabled.

Fixed: TestComplete could freeze when capturing a Tab control in a web application.

Fixed: When accessing a tested web application running in Internet Explorer, TestComplete could freeze or exit unexpectedly, or it could cause Internet Explorer to freeze or crash.

Fixed: A tested iOS application could exit unexpectedly when being explored in the Object Browser or Object Spy.

Fixed: When launching instrumented applications on iPhone 7 or iPhone 8 Plus running under iOS 11, TestComplete could report an unexpected error.

Fixed: Performance issues with the Code Editor when automatic outlining was enabled.

Fixed: If a project contained multiple USEUNIT statements, it could take much time for TestComplete to start running a test.

Fixed: TestComplete treated whitespaces at the end of the USEUNIT statement as part of a unit name.

Fixed: If a project included a script unit containing only USEUNIT statements, TestComplete was unable to run tests in that project.

Fixed: TestComplete could report the “List index out of bounds” error upon renaming the script unit to which USEUNIT statements refer.

Fixed: TestComplete could exit unexpectedly when opening a project containing USEUNIT statements.

Fixed: TestComplete parsed strings containing the USEUNIT substring as USEUNIT statements.

Fixed: Manipulating To Do items could corrupt Python script tests.

Fixed: Performance issues when calling chr(34) in JScript or JavaScript tests.