The Object Mapping settings have been improved. In earlier versions you could only map custom controls to Win32 objects. Now, you can map the controls to any components supported by TestComplete: Win32, .NET, Java, WPF, Microsoft, Developer Express, Syncfusion, Infragistics and others. This feature lets you enable recording and scripting support for descendants of these controls and allow you to create table checkpoints for verifying their data.

By using the new Disable mouse project property you can now specify whether TestComplete should ignore the mouse actions that a tester performs during the test execution. Using this feature you can guarantee that a tester’s actions will not affect the test during the run.

TestComplete’s script debugger includes a new powerful command called Set Next Statement. Using this command you can change the execution flow, which allows you to skip or re-execute some code parts within a routine.

The set of built-in functions have been extended with five new routines:

TestComplete now includes a zip archiving functionality (InternalZip). You can use it to compress test results.

Now, TestComplete includes a SQL Designer which you can use to view and create custom queries for database checkpoints.

Support for Mozilla Firefox has been extended. Now TestComplete can automatically change the proxy settings of this browser when it records HTTP traffic. Also, all Mozilla applications have obtained a pair of extended properties that provide scripting access to application’s internal information and options.

TestComplete now includes compiled executables of its demo applications, where before, TestComplete’s installation package only included their source code and the complied samples were available on AutomatesQA’s web site.

TestRecorder can now be embedded in Java applications.

A TestRecorder Demo for 64-bit platforms has been added.

A performance slowdown while testing .NET applications has been eliminated.

Sometimes, TestComplete could not recognize objects in .NET applications if they were addressed directly by their name.

Sometimes, TestComplete failed to obtain windows of .NET applications.

Due to certain errors that occurred during the TestComplete installation, TestComplete failed to recognize 64-bit Open Applications as Open.

TestComplete could raise Access Violation errors in Delphi and C++Builder Open Applications while reading debug information from them.

TestComplete could hang when reading debug information from C++ applications.

When TestComplete was reading object properties in a C++ application, either TestComplete, or the application under test could hang.

In certain cases, the Debug Agent could not read debug information from statically linked libraries.

The Debug Agent performance has been improved.

The “Cannot load the tcOpenAppHook.dll library” error occurred when launching a Delphi or C++Builder Open Application with the TestRecorder component if TestComplete was not installed on the computer.

Sometimes, scripts that called “native” methods and properties of Delphi and C++Builder Open Applications and that were created in TestComplete 5 could not be executed successfully in TestComplete 6.

An attempt to call a “native” MFC method of a C++ Open Application caused an error.

If calls to “native” methods of Delphi or C++Builder Open Applications used variables as parameter values, TestComplete could pass an incorrect value to the application.

Sometimes, TestComplete could not convert a routine parameter to the needed “native” type, which resulted in the “Parameter type mismatch” error.

In certain cases, TestComplete did not catch exceptions that occurred in Visual Basic.NET, Visual C# and Visual C++ Open Applications.

If the Record short names when possible option was enabled and a control’s “native” name started with an underline character ( _ ), TestComplete recorded the name without the underline character.

A number of minor issues have been fixed in the Debug Agent.

If the Make Page object a child of the browser process option was enabled, TestComplete still recorded scripts over Internet Explorer pages using the nested Page object.

If the Make Page object a child of the browser process option was enabled, TestComplete only recorded the Page.ToUrl method call for the first page that was open in the browser, and did not record this method for the subsequent pages.

TestComplete inserted the Page.ToUrl method call to a script recorded over an MHT file, which caused an error during script execution.

There was an error in naming web page frames displayed in Firefox.

TestComplete rebuilt the Firefox process tree too often after a new Firefox window was opened.

The Page.PagePicture method captured images incorrectly if the browser displayed an active content warning.

On Windows Vista, TestComplete recorded keyboard input in Internet Explorer 7 slowly.

An application with the WebBrowser control could hang when TestComplete was recording user actions over the control.

The Finder tool selected combo box controls on a web page incorrectly.

The Object Browser did not display extended and “native” properties of web pages’ OBJECT elements if the Tree web model was active. The

Object Browser did not refresh the captions of Open Application windows and Internet Explorer 7 tabs.

TestComplete crashed upon pressing the Show Tested Applications Only button if the current project suite was empty.

In certain cases, TestComplete hung when the user switched to the Object Browser.

Incorrect help topics could be displayed when the user pressed F1 while a property, method, action or event was selected in the Object Browser.

TestComplete read unit files byte-by-byte, thus decreasing the performance if one unit referred to another.

An identifier whose name started with the “file_” prefix was considered as invalid.

It was impossible to paste data form the clipboard when the Code Completion window was displayed.

TestComplete could crash when parsing a DelphiScript unit.

TestComplete crashed when invoking the Code Completion window within a While…End While block in a VBScript unit.

TestComplete crashed when invoking the Code Completion window or the Code Parameters hint in a VBScript unit on a line that followed a line-continuation character ( _ ).

It was impossible to invoke the Code Parameters hint in a function call whose result was assigned to a variable.

The Code Parameters hint could not be displayed if the routine’s string parameter contained spaces.

It was impossible to invoke the Code Parameters hint in a VBScript routine call if the statement started with the Call keyword.

If a statement was entered after a comment, the Code Completion suggested an incorrect statement.

If a method name was inserted from the Code Completion, it was automatically enclosed in parentheses.

A double click on a code segment could also highlight a semicolon that followed the code.

Some common constants (skShift, cbChecked and others) were not listed in the Code Completion window when in the Autocompletion mode.

The behavior of the search dialog was improved to handle the situation when the same unit is opened in several editor windows.

When the user closed the Search dialog, the input focus was not set to the Code Editor.

The After Replacement column of the Replace Results panel did not contain new values.

Sometimes, TestComplete could not perform a search in all of the projects of a project suite.

A number of minor issues in the script parsers have been fixed.

The Find method did not refresh the object tree.

The projects’ Tree model options were corrupted after the Options.Web.TreeModel property was modified from a script.

The DDT.CSVDriver method failed to create a driver object if the file name contained an exclamation mark ( “!” ) or the “select” substring.

The DDT.CloseDriver method did not release the Excel file that the driver was reading.

The slPacker.Pack method did not report an error if a script configuration was not selected in the project’s Packer options or if the selected script configuration was not adjusted.

The slPacker object created incorrect RAR archives if WinRar 3.7 was installed on the computer.

TestComplete generated an incorrect constructor for arrays used in web services’ method calls.

Evaluating a non-existent object and monitoring a lot of non-existent objects in the Watch List panel took a long time.

In certain cases, a variable that stored an object obtained a “stub” object value, although the corresponding object still existed and had not been recreated.

The DevExpressQuantumGrid object methods and properties could raise errors when applied to QuantumGrid v.4.

Some DevExpressQuantumGrid properties posted unnecessary error messages to the log.

Sometimes, TestComplete could not recognize Infragistics WinGrid controls during playback.

TestCompete could not click the label of the first item in Microsoft's PropertyGrid.

In certain cases, clicks on grid cells were recorded incorrectly and TestComplete recorded the Click action instead of ClickCell, ClickLabel, etc.

The performance of TestComplete’s interaction with WPF controls has been improved.

Actions over WPF tree view items were recorded as coordinate clicks.

TestComplete recorded the selection of items in a data-bound WPF combo box incorrectly.

If a window that contained a ToolStrip toolbar was minimized, the StripToolBar.ClickItem action did not bring it back to the normal state.

If a ToolStrip button was invisible, TestComplete clicked on the toolbar’s left edge instead of reporting an error.

The StripToolBar.wChecked property raised an error if the specified item was not a toggle button.

The StripToolBar.wIsDropDownButton property returned False if the drop-down button had the ToolStripDropDownButton class.

TestComplete could not record the selection of a combo box item on a ToolStrip toolbar.

Sometimes, TestComplete recorded clicks on StatusStrip items using the Click action rather than ClickItem.

An error could occur when selecting an item from the dropdown menu of a ToolStrip button.

The Menu.Click action did not scroll a data-bound WPF menu to the needed item.

If a Menu object corresponded to a submenu, it was still impossible to specify a relative path to submenu items.

An error message reporting that the main menu was not found contained an incorrect menu name.

If a toolbar or a menu item was addressed via wildcards, the log messages included a wildcard mask rather than the item’s actual text.

The Win32ToolBar.Click action worked incorrectly if the TestComplete 3 Compatibility plug-in was installed.

In certain cases, TestComplete could not recognize the main menus in Java applications during playback and when exploring the application in the Object Browser.

Sometimes, TestComplete recorded actions over SWT controls incorrectly.

TestComplete recorded the selection of a combo box item on a web page incorrectly.

Scrolling of list box items was recorded as the Drag action rather than setting the Win32ListBox.VScroll.Pos property.

Attempts to obtain the Window.ActionMainMenu property from scripts or read it from the Object Browser caused an error.

The Click and Keys actions failed to simulate actions over Infragistics PVDate controls.

An attempt to perform a click out of the screen bounds displayed an error message that contained unclear information.

In certain cases, tested applications could not be launched in the Simple and RunAs run modes.

The Step Description field could not store strings containing more than 128 characters.

The Manual Test editor controls had an incorrect Tab order.

No tooltips displayed for buttons on the Manual Test editor toolbar.

Sometimes, the Run State page of the Network Suite editor was not displayed after a network suite was launched.

The network suite log now displays the address of the host where a task was performed.

The Engines | Visualizer  | Capture style combo box did not have option values in the drop-down list.

The image format of images captured by Visualizer could not be adjusted since the Configure button was not displayed in the Visualizer Options dialog.

The startup dialog of the TestExecute Demo contained incorrect information and its Buy Now button took users to the wrong web page.

The Global Shortcuts options included the Fix Information shortcut. This has been removed since it is not used in TestExecute.

TestComplete did not include a 64-bit version of the tcUIAHook.dll library.

TestComplete could hang when closing.

TestComplete did not use mapped names in checkpoints.

If the tested application was launched on a Virtual PC, TestComplete could crash the application when trying to access its objects.

TestComplete could crash an MDI application when trying to access an object in a child window.

A number of issues regarding the conversion of TestComplete 3 projects to the format used in TestComplete 6 were fixed.

TestComplete could crash upon disabling a plug-in if the editor provided by that plug-in was open at that time.

When the total number of editor windows exceeded the value specified in the Maximum number of editors option, TestComplete could close the editor without saving the changes.

An error occurred when creating a new project if the project suite was bound to a source control system.

Sometimes, a cloned project did not have the same physical folder name as the original project.

If a project included custom folders, a project item was moved from this folder to the project level when the user disabled the plug-in that provided this item. After enabling the plug-in, the project item remained in the project folder.

The Test Items page of the Project editor displayed the wrong description for JScript routines that had no parameters.

Project Explorer’s context menu did not close upon pressing the Esc key.

TestComplete did not initialize the Engines | Packer | Script configuration option during installation.

If the Error dialog option was disabled, the Minimize TestComplete option was enabled and an error occurred during playback, TestComplete restored its main window and opened the erroneous unit, thus ignoring the options.

Sometimes, TestComplete recorded Boolean parameters as -1/0 instead of True/False.

The Unit Testing demo application created in Borland Delphi worked incorrectly.

A number of errors occurred during compilation of the Project Item and Project Item Editor samples included in the TestComplete SDK.

There were minor differences in Delphi and C++ variants of the Project Item Step 2 sample included in the TestComplete SDK.