Bug Fixes in TestComplete 12.31

Applies to TestComplete 14.91, last modified on July 20, 2021

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

General

  • Fixed: Data Generator failed to create a new Excel worksheet for the Excel 2016 Microsoft Office 365 PropPlus edition.

  • Fixed: TestComplete did not recognize processes launched from applications run in the RunAs mode.

  • Fixed: The Checkpoint wizard switched the user-specified name of verified objects to the object’s mapped name.

  • Fixed: Cloned projects did not include information on variables, test items, settings, and other information of the original projects.

  • Fixed: A number of properties (for example, ObjectIdentifier, Caption, and other) were not available for objects exposed with the Microsoft Active Accessibility (MSAA) engine.

  • Fixed: TestComplete could rename items of tests arbitrarily when editing the test item list of a project.

  • Fixed: Global keyboard shortcuts stopped working for TestExecute.

  • Fixed: TestComplete could randomly change the Auto-wait timeout project property to 50.

  • Fixed: TestComplete could exit unexpectedly upon pressing ESC when editing keyword tests.

  • Fixed: TestComplete could exit unexpectedly when loading interlaced PNG files.

  • Fixed: User Forms did not use specified font attributes during the test run.

Desktop Application Testing

  • Fixed: TestComplete could not recognize the Uninstall button in the Program and Features dialog on Windows 10.

  • Fixed: Performance issues could occur with tests that use UI Automation on Windows 10.

  • Fixed: Native methods of AWT objects in tested Java applications could throw NullPointerException.

  • Fixed: TestComplete could not exit properly after running tests that used the Microsoft Active Accessibility (MSAA) engine.

Web Testing

  • Fixed: TestComplete could fail to recognize objects on a web form opened in Internet Explorer.

  • Fixed: TestComplete could fail to recognize links on a web page opened in Internet Explorer.

  • Fixed: TestComplete could exit unexpectedly when accessing a mapped object in Internet Explorer in the Extended Find mode.

  • Fixed: TestComplete could fail to recognize JavaScript-generated dialogs in the Chrome web browser.

  • Fixed: TestComplete could record user actions over a modal form in the Chrome web browser incorrectly.

  • Fixed: The ObjectIdentifier property was truncated for web objects with long id attributes.

Mobile Testing

  • Fixed: Android applications containing .wav or .mp3 files could exit unexpectedly or work incorrectly after being instrumented in TestComplete.

  • Fixed: TestComplete could not connect to the HTC One M9+ (Prime Camera Edition) device.

  • Fixed: The FileSystemManager.FindFiles and FileSystemManager.FindFolders methods returned incorrect values when searching files and folders on Android 7.x devices.

  • Fixed: The Name property of pages opened in the WebView control was too long if the loadData method was used to load the page content.

  • Fixed: TestComplete could exit unexpectedly when testing applications running on Android Virtual Device (AVD) emulator API 24 - 25.

  • Fixed: TestComplete could randomly disconnect from Android Virtual Device (AVD) emulator API 24 - 25.

  • Fixed: TestComplete could reload the Android Virtual Device emulator when working with the device via the Mobile Window.

  • Fixed: Instrumented iOS applications could throw the “The bundle identifier does not match the application identifier entitlement” error.

UI

  • Fixed: The layout of the Edit Name Mapping Item dialog in TestComplete running on Windows 10 with DPI larger than 100% was corrupted.

Scripting

  • Fixed: If a JavaScript test included many USEUNIT statements, it could take much time for the Watch List panel to show the needed values.

  • Fixed: TestComplete could exit unexpectedly upon clicking outside the TestComplete IDE after renaming a script unit.

  • Fixed: Searching in the Code Editor took much time for outlined scripts.

  • Fixed: TestComplete could fail to access its built-in scripting objects during the test run.

  • Fixed: The Code Completion window could stop showing properties and methods of custom objects implemented by script extensions.

  • Fixed: TestComplete could exit unexpectedly when running a Python script test containing only comments.

Integration With Other Tools

  • Fixed: TestComplete could not export TestComplete projects to QAComplete if the user account, under which the project was exported, was not a Security Administrator in QAComplete.

  • Fixed: In team builds managed with Microsoft Team System, the Run Functional Tests build step did not run TestComplete tests in the Test Plan mode.

  • Fixed: Source control-related operations were not available in TestComplete for a project stored in a Team Foundation Version Control repository.

  • Fixed: TestComplete plugin for Jenkins could fail to create a user session on Jenkins nodes.

See Also

Features Added to TestComplete 12.31
Version History

Highlight search results