Bug Fixes in TestComplete 14.20

Fixed: VBScript and JScript projects fully stopped upon an error, even if they were configured to stop only the current test item or to ignore errors.

Fixed: On computers with the DPI setting set to 150%, the Name text box of the Map Object dialog did not show the selected object name.

Fixed: User actions recorded on computers with a 4K display and the DPI setting set to 150% were simulated with an offset.

Fixed: If a computer had several monitors, and different DPI values were set for them, the Code Completion window was shown incorrectly.

Fixed: TestComplete could exit unexpectedly when a user clicked “Find All” in the Find dialog if the Match case and Search in collapsed section options were enabled.

Fixed: TestComplete could exit unexpectedly when creating a region checkpoint if a user had canceled creation of the Regions collection.

Fixed: The 32-bit version of Report Generator launched the 64-bit version of TestComplete (or TestExecute).

Fixed: When a JavaScript project’s test item was stopped upon an error, the variable values were set to an empty value.

Fixed: Cloning projects could result in a corrupted project.

Fixed: TestComplete could exit unexpectedly when cloning a project if the project contained corrupted data.

Fixed: TestComplete could exit unexpectedly when running on older versions of Windows 10.

Fixed: Access violation errors when running tests on the Windows Server 2008 R2 system.

Fixed: TestComplete could exit unexpectedly when it was unable to access a proper license.

Fixed: TestComplete could stop responding during the test run.

Fixed: TestComplete could report the “Index out of bounds’ error and exit unexpectedly.

Fixed: TestComplete could exit unexpectedly when a user was exploring a tested application by using the Object Spy.

Fixed: TestComplete could exit unexpectedly upon starting.

Fixed: TestComplete could close incorrectly.

Fixed: TestComplete (or TestExecute) could stop responding when testing a .NET application.

Fixed: Memory issues when accessing string properties of objects in a tested Delphi application.

Fixed: On Windows 10, calling the ClickCell method of a Stingray control in a Visual C++ application could cause TestComplete to exit unexpectedly.

Fixed: The items of drop-down list objects recognized by using UIAutomation didn’t have the Select method.

Fixed: In WPF applications, the ClickItem method of list box and list view controls reported an error even if a click was simulated correctly.

Fixed: TestComplete (TestExecute) could exit unexpectedly when testing a CEF application.

Fixed: TestComplete (TestExecute) could stop responding when running tests for CEF applications.

Fixed: TestComplete could exit unexpectedly when running tests in the Chrome browser or could lose access to the tested web application's internal objects.

Fixed: Sometimes, the tcCrHost.exe process (a TestComplete extension for Google Chrome) could exit unexpectedly during the test run.

Fixed: The Chrome browser could exit unexpectedly when TestComplete was recording user actions over the Open File and Save File dialogs of Chrome.

Fixed: The “External exception E06D7363” error could occur when running web tests in Firefox.

Fixed: Firefox could stop responding during the test run if the tested web application used web components.

Fixed: Performance issues when recording keystrokes in Internet Explorer.

Fixed: The FindChild method didn’t recognize data- attributes in web applications running in Internet Explorer.

Fixed: The Run method could fail to correctly open the needed web page in Internet Explorer.

Fixed: TestComplete could exit unexpectedly when stopping test recording in a web application.

Fixed: SmartBearBrowser always opened videos in full-screen mode in JW-Player version 7.

Fixed: SmartBearBrowser could exit unexpectedly when collapsing the video running in JW-Player.

Fixed: When recording a mobile test, the Recording toolbar could stop responding or responded very slowly.

Fixed: TestComplete could exit unexpectedly after a user re-connected a mobile device to the computer.

Fixed: TestComplete could exit unexpectedly when accessing the tested mobile devices.

Fixed: TestComplete and the tested Android application could exit unexpectedly when a user was exploring the application in the Object Browser or by using the Object Spy if the application had been instrumented by TestComplete.

Fixed: Tested Android applications created with Xamarin Forms 3.4 could exit unexpectedly during the test run.

Fixed: TestComplete could simulate text input in a wrong text box.

Fixed: TestComplete could not get a list of installed applications from Huawei Y6 devices.

Fixed: TestComplete could stop responding when mapping an object of a Xamarin.Forms application running on an Android device.

Fixed: A tested Android application running on Android 5.0 could exit unexpectedly when a user was exploring it in the Object Browser or Object Spy.

Fixed: TestComplete could exit unexpectedly during the test run if the SendKeys method was used in a data-driven loop.

Fixed: TestComplete could exit unexpectedly when editing operations residing within a data-driven loop of an OCR keyword test.

Fixed: JUnit reports generated by TestComplete were incompatible with the xUnit log format.

Fixed: The Log.SaveResultsAs method always included the Summary report in the generated reports even if it was not supposed to do that.

Fixed: Test logs exported to an HTML file didn’t include the Summary report.

Fixed: An MHT file containing test results could open for a long time.

Fixed: On Windows with Korean regional settings, the test log displayed timestamps incorrectly.

Fixed: TestComplete organized data in the printed version of a test log in an inconvenient way, making it difficult to read the reports.

Fixed: TestComplete could exit unexpectedly when a user was editing a value of the Item column of an On-Screen Action operation.

Fixed: TestComplete could exit unexpectedly when running a keyword test.

Fixed: The Highlight on Screen command of the context menu called for checkpoint operations in keyword tests was disabled.

Fixed: A Python script test could stop responding when running loops using the in operator.

Fixed: TestComplete could exit unexpectedly during a script test run if the Watch List panel was used.

Fixed: An unexpected stack overflow error could occur when the aqConvert.DateTimeToFormatStr method was called.

Fixed: TestComplete could exit unexpectedly when calling the Log.Error method in event handlers.

Fixed: The aqFileSystem.CreateFolder method created a folder successfully, but reported an error.

Fixed: TestComplete could stop responding when a user was editing scripts.

Fixed: TestComplete could stop responding during test recording if the test project had lots of BDD test steps that had not been implemented yet.

Fixed: TestComplete could exit unexpectedly if a user pressed the “Record Next Step” button during test recording.

Fixed: TestComplete showed results of distributed tests incorrectly.

Fixed: When TestComplete was verifying a network suite host, and its login mode was set either to Automatic RDP Session or to Automatic Console Session, the current session was not closed on the host.

Fixed: TestComplete (TestExecute) could stop responding when stopping tasks of a distributed test.

Fixed: The master project of a distributed test could not access projects on remote hosts after TestComplete or TestExecute was updated on the hosts.

Fixed: TestComplete did not show any proper message when authorization errors occurred on connecting to Zephyr for Jira.

Fixed: An error could occur when connecting to Zephyr for Jira by using an account with no administrator privileges.

Fixed: TestComplete could fail to get a list of Zephyr test items from a Jira project.

Fixed: Sometimes, it was impossible to edit the default Zephyr for Jira properties of a project.

Fixed: TestComplete could exit unexpectedly when getting a list of projects from Team Foundation Version Control.

Fixed: TestComplete could exit unexpectedly when getting a project from Team Foundation Version Control.

Fixed: If a project was stored in the Team Foundation Version Control repository, TestComplete handled renaming of project items incorrectly.

Fixed: It was impossible to submit an issue to an issue-tracking system from a test item log.

Fixed: TestComplete could fail to convert a keyword web test to a LoadComplete test if the keyword test took parameters.