What’s new in TestComplete 6.12
The changes listed below have also been applied to TestExecute 6.12 and TestRecorder 6.12, as these products are based on TestComplete’s technology.
New Features
The Code Explorer panel now traces problematic routines and statements in your script code, such as hard-coded numeric and string values, routines having a great number of parameters, and so on. New metrics can help you improve script code in accordance with the coding conventions used in your company.
The
WebComparison.Compare method has a new Timeout parameter, which specifies the time that the web comparison checkpoint will wait until the web page contents match the stored one. This parameter is useful if the web page contents are generated dynamically after the page was loaded in the browser.
Bug Fixes
Controls Support
Grids
Sometimes, TestComplete could not click on Microsoft PropertyGrid cell labels.
TestComplete recorded actions over unsupported views of Developer Express XtraGrid controls using extended methods instead of black-box methods.
In some cases, TestComplete could not play back the recorded script if it performed actions over Developer Express QuantumGrid.
In Infragistics WinGrid controls, TestComplete recorded actions over the “Add New” row incorrectly.
Sometimes, TestComplete recorded a double click on Syncfusion EssentialGrid cells as a single click.
Menus
In certain cases, TestComplete recorded clicks on
SwingMenu items incorrectly.
In certain cases, TestComplete could not click several
EssMainMenu items in sequence.
TestComplete could record clicks on nested
EssMainMenu items incorrectly.
The depth of nested popup menus handled by the
PopupMenu object was limited.
The
Window.SystemMenu property was unavailable to the child windows of MDI applications.
When recording actions over the context menus of .NET applications, mouse clicks could be interpreted either as
Window.Click or as PopupMenu.Click actions. Now only the latter is possible.
Actions performed over owner-drawn menu items were not recorded via item indexes.
The ability to verify whether a menu item can act as a check box has been restored for the
Menu.Check action.
Toolbars and Status Bars
Checking the
WPFToolBar.wIsCheckButton and WPFToolBar.wIsDropDownButton property values applied to items located on popup windows caused these items to appear on screen.
Selection of items from dropdown menus of Syncfusion ToolStripEx and StatusStripEx controls was recorded incorrectly.
Sometimes TestComplete recorded clicks on Syncfusion Essential Tools toolbar items as clicks on menu items.
Other
It was possible to select a disabled tabbed page in WPF tab controls using the
ClickTab action.
In WFC applications, the
Win32ListView.ClickItem method could mistakenly click another element.
An incorrect message was posted when calling
Win32ListView.SelectItem with the parameter -1. This parameter value is used to unselect all the items, whereas it was reported that all the items were selected.
The
Win32TrackBar.wTicPosition property returned an incorrect value.
The Index parameter of the
Win32UpDown.wAcceleration property could accept values exceeding the total number of acceleration information items.
The
Win32HotKey object could confuse some system buttons (Ins, Del, Home, End, Page Up, Page Down, and arrow keys) with their NumPad analogs.
Applications Testing
TestComplete treated Open Applications with the *ras.exe name as black-box ones.
In Oracle Forms applications, TestComplete recorded user actions over the top-level application object instead of appropriate child objects.
Sometimes, TestComplete recorded actions over Java Swing applets on pages displayed in Firefox or Netscape Navigator incorrectly.
Checkpoints
TestComplete crashed upon creating a Web Service checkpoint if the user had not specified the contents of complex parameters for a web service method call.
TestComplete logged incorrect information about the first failed verification of a Web Comparison checkpoint.
Program Objects
In certain cases, TestComplete hung while executing the
Page.Wait method.
After executing the
Page.PagePicture method, the top frame of the web page became invisible.
If ODT objects were created via the
Runner.CallMethod method, they were not released after the test was finished.
The
Log.Picture method could not log images in the TIFF format with the CCITT compression type.
Installation
In certain cases, errors could occur when modifying TestComplete installation.
TestExecute could not be installed in silent mode.
Miscellaneous
The performance of Code Completion has been improved.
A number of synchronization issues in network suites have been fixed.
The event handlers of ActiveXObjects were not preserved when opening projects created in earlier TestComplete versions.
TestComplete searched in the Source view of the XMLCheckpoint Element editor incorrectly.
If project scripts were organized into folders, the order of items in the Script project item file (.tcScript) changed after adding a new script unit. As a result, it was hard to merge the files in a source control system.
The Compression combo box located in the Packer Configuration dialog did not open if the Internal Zip archiver was selected.
TestExecute’s icon was not displayed in the system tray after restarting the Explorer process.
A number of errors in TestRecorder samples have been fixed.
Borland Delphi samples included in TestComplete SDK could not be compiled.
A number of crashes reported by our customers have been fixed.