Bug Fixes in TestComplete 12.40

Fixed: When cloning a DelphiScript project in TestComplete, the cloned project was converted to JavaScript.

Fixed: It was impossible to change the default project in a project suite. The Set as Default Project command did not work.

Fixed: When migrating projects to version 12.30, object names in keyword tests could become blank if there were errors in script tests.

Fixed: If a test log exported to the HTML format could not show the file comparison results in Google Chrome due to security reasons, no proper warning was displayed about it.

Fixed: The Undo command in the Code Editor could fail to return code to its previous state correctly (for instance, it did not return the insertion point to its previous position).

Fixed: TestComplete could exit unexpectedly when pasting text from the clipboard to the Code Editor.

Fixed: When running a test on remote computers, TestComplete could exist unexpectedly when calling Network Suite variables in the OnNetTaskStateChange event handler.

Fixed: The NativeVBObject.Name property returned the "Parameter not optional" error.

Fixed: TestComplete could report errors when exploring 64-bit applications compiled with Delphi Tokyo 10.2.

Fixed: TestComplete could fail to call properties and methods added to a TStringGrid control in applications compiled with Delphi Tokyo 10.2.

Fixed: During the test run, TestComplete could stop recognizing some Windows Forms controls after the application froze.

Fixed: TestComplete failed to recognize controls by using the Text Recognition technology if text characters in the application were associated with glyphs by using the IDWriteTextAnalyzer::GetGlyphs method.

Fixed: TestComplete could exit unexpectedly when running JavaScript tests in Google Chrome.

Fixed: When the Firefox web browser was running in multi-process mode, TestComplete could fail to recognize web pages correctly.

Fixed: Firefox could exit unexpectedly when accessing the Page object.

Fixed: TestComplete identified object coordinates in the Edge web browser incorrectly.

Fixed: When capturing objects in a CEF application by using the Object Spy, the application could stop working.

Fixed: When exploring the object hierarchy in an Android application containing a Scroll View control with an invisible Web View control, the application could crash.

Fixed: The tested Android application could crash when TestComplete accessed the properties it had added to the DatePicker object.

Fixed: TestComplete Android Agent failed to start if one of Android device subsystems (for instance, GPS, Bluetooth, Wi-Fi, and so on) was malfunctioning or missing.

Fixed: If TestComplete failed to find the needed object on the current device when running tests by using the Device loop operation with several mobile devices connected, it would search for the object on other devices. If the object was found on another device, TestComplete continued running the test on that device.

Fixed: Sometimes, the tested iOS applications could not be installed on an iOS device after it was rebooted.

Fixed: On Windows 10 Creator Update, object recognition performed via UI Automation could work incorrectly (for instance, the NativeUIAObject.Name property could not return a proper value).

Fixed: Some objects in the object hierarchy of an application recognized by using UI Automation could be duplicated.

Fixed: TestComplete could fail to recognize all grid rows in an application recognized by using UI Automation.

Fixed: It took much time for TestComplete to map or identify objects in projects with large Name Mapping repositories.

Fixed: TestComplete mapped context menus in Windows Forms applications incorrectly - the parent node of mapped context menus was missing in the Name Mapping repository.

Fixed: TestComplete allowed creating region checkpoints for windows and controls blocked by modal windows. The created checkpoints always failed due to the "Unexpected window" error.

Fixed: When editing a Property Checkpoint operation in keyword tests, a carriage return was added to the baseline string value.

Fixed: Columns in the Edit Name Mapping dialog were too narrow when they were displayed on large resolution monitors.

Fixed: TestComplete could exit unexpectedly when working with its UI on a computer with several monitors with various DPI settings.

Fixed: Python script tests could stop running right after the start if the PYTHONPATH and PYTHONHOME environment variables were specified on the computer, or if there were several Python versions installed.

Fixed: If a keyword test called a Python script routine, double-clicking on any test step result in the test log could open the script routine code instead of the appropriate step in the keyword test.

Fixed: Double-clicking a message in the Python script test log highlighted an incorrect code line.

Fixed: TestComplete consumed a lot of memory upon opening a test project containing large JavaScript tests.

Fixed: In JavaScript, if calling a property of a TestComplete program object (for example, Sys, Log, Variable and so on) caused an exception, the exception was not raised properly, and the property returned the "undefined" value. Now, the exception is raised correctly in JavaScript.

Fixed: the aqFileSystem.CopyFile and aqFileSystem.CopyFolder methods could not copy a file if the file's base name was "null" (for instance, null.gif).

Fixed: It was impossible to navigate to a script unit listed in the USEUNIT section quickly by clicking the unit name with the CTRL key pressed.

Fixed: The TableVariable.AddColumn method did not add columns to variables of the Table type.

Fixed: TestComplete could exit unexpectedly when editing a script if automatic outlining was enabled.

Fixed: TestComplete recorded a property checkpoint for C#Script incorrectly: the aqObject object was recorded as a method.

Fixed: Runner.CallObjectMethodAsync was called incorrectly in JavaScript: TestComplete did not call the specified method until the script run was over.

Fixed: When setting date/time values, the WebServices object always specified the local time zone.

Fixed: Sometime, the Code Editor could not collapse or expand code blocks in Python scripts.

Fixed: Visual Studio Integration Package could not detect Visual Studio 2017 or Visual Studio 2017 Test Agent Update 15.3 installed on the computer.