Microsoft Visual C++ 2008 Open Applications. TestComplete now supports Visual C++ Open Applications created in Microsoft Visual Studio 2008. So, you can test these applications in white-box mode, by using their internal objects, methods and properties.

Support for Syncfusion bar controls. The new version introduces support for the ToolStripEx and StatusStripEx controls from the Syncfusion Essential Tools library. You can work with these controls using the StripToolBar and StripStatusBar objects, respectively.

Improved recording of web page URLs. TestComplete projects include a new Ignore dynamic URL parameters property. It controls how TestComplete records web pages’ URLs that contain dynamic parameters (that is, parameters passed after the question mark in the URL). If this property is enabled, TestComplete replaces the parameter values with the * wildcard. This makes the recorded script independent of the parameter values and thus more stable.

More information about processes. All process objects have two new properties, FileVersionInfo and SessionId. The FileVersionInfo property lets you get the file version information of the process executable. Using the SessionId property, you can get the identifier of the Terminal Service session under which the process is running.

Unit metrics. The Code Explorer panel has been improved. In addition to the code structure, it now displays a summary about the current project suite, each of its projects and script units.

The Create Property Checkpoint dialog has a new Case sensitive option. You can use this option when creating string property checkpoints to specify whether the comparison should be case-sensitive or case-insensitive.

The Stop Outlining command was added to the context menu of the Code Editor. It lets you quickly cancel outlining in the current script unit.

TestComplete could not recognize some SWT applications as Open applications.

.NET 2.0 applications launched with the /NotOpenApp parameter were still treated as Open.

TestComplete could crash Visual C++ Open Applications while working with them.

An access violation could occur in the VB Runner library (tcVBRunner.dll) during calls to routines located in Visual Basic 6.0 standard executables.

TestComplete could hang while the user was exploring a VCL Open Application in the Object Browser.

In certain cases, Debug Agent generated exceptions that interrupted the test execution.

The Debug Agent performance has been improved.

TestComplete inserted a superfluous Page.ToUrl method call into the recorded script that opened a web page in Firefox.

Sometimes TestComplete traced changes in the Firefox objects tree incorrectly.

TestComplete recorded clicks on APPLET elements incorrectly if the Make Page object a child of the browser process option was enabled.

The Make Page object a child of the browser process option did not work in certain cases.

Web Comparison checkpoints did not report what comparison actions failed.

The performance of Web Comparison checkpoints has been improved.

TestComplete recorded actions with dialog web pages incorrectly.

Sometimes TestComplete did not record clicks on items of combo boxes displayed on web pages.

Sometimes TestComplete could not launch slave projects on remote computers.

Sometimes network suite variables were not updated on slave computers.

The Run State page of the NetworkSuite editor did not display the name of the critical section that the master project entered.

A number of synchronization issues have been fixed.

TestComplete could crash upon errors while converting TestComplete 3 network suites to the new format.

TestComplete could crash while loading an invalid WSDL file.

The names of web services’ overloaded methods were handled incorrectly.

Complex data types set via schema attributes were recognized by the Web Service editor incorrectly.

TestComplete 6 could hang while trying to execute a manual test created in TestComplete 4.

The ManualTests project item was marked as modified right after it was opened, even if no actual modifications were made.

TestComplete attempted to call a manual test event even if the corresponding TestComplete event was removed (both the event item and the corresponding script routine).

The default name mapping template for the System.Windows.Forms.TrackBar control was incorrect.

TestComplete could crash while creating a checkpoint or mapping a certain kind of objects.

Sometimes TestComplete highlighted the found string incorrectly.

The search performance has been improved.

The Code Parameters hint had wrong formatting if the script routine had a large number of parameters.

Sometimes script parsers crashed.

In some cases after the Set Next Statement command was called, the next code line to be executed was calculated incorrectly.

TestComplete hanged upon pressing the Stop button while the script was paused on a breakpoint.

TestComplete crashed on an attempt to map a custom control to a third-party control support for which was disabled.

TestComplete did not break associations between controls and scripting objects after disabling Object Mapping items. In other words, it went on working with controls using extended methods and properties.

TestComplete could not perform actions with a control if it was overlapped by the Indicator icon.

Sometimes TestComplete recorded clicks on Developer Express XtraGrid row indicators as the DevExpressXtraGrid.Click action instead of DevExpressXtraGrid.ClickRowIndicator.

TestComplete failed to simulate actions with cells in the Developer Express XtraGrid and Syncfusion Essential Grid controls if the tested application’s window was minimized.

TestComplete recorded the SyncfusionEssGrid.ClickCellXY action with negative coordinates.

An error occurred in the InfragisticsWinGrid.ClickRowIndicator action if the specified row indicator was not visible.

TestComplete recorded actions with the first row in Microsoft DataGrid controls incorrectly.

TestComplete could not set the scrollbar position in Microsoft DataGridView controls.

The MicrosoftPropertyGrid.Expand action did not post an error message upon an attempt to expand a non-expandable item.

Sometimes the MicrosoftPropertyGrid.ClickValue action failed.

There was a long delay before the first click on an EssMainMenu item.

The Window.EssMainMenu.Check method reported that an item was successfully checked though it was not actually checked.

Sometimes TestComplete recorded clicks on wrong EssMainMenu items.

TestComplete could fail to play back recorded actions with XtraMainMenu edit items.

TestComplete was unable to record actions with owner-drawn MFC menus using item captions. Only item indexes were recorded.

Memory leaks occurred while testing applications that used some third-party controls if the TestComplete 3 Compatibility plug-in was enabled.

TestComplete recorded actions with Java applications’ pop-up menus incorrectly.

TestComplete could record clicks on WPF applications’ controls incorrectly.

WPF applications could hang due to incorrect usage of the ClickButton action.

The WPFTrackBar.wNumTics and wTicPosition properties returned wrong values. 

Sometimes TestComplete recorded double-clicks on WPF RepeatButton controls as the Click action.

The WPFToolBar.wIsCheckButton and wIsDropDownButton properties returned an incorrect value if the toolbar was located on a popup. 

The WPFTreeView.ExpandItem, Win32TreeView.CollapseItem, Win32TreeViewItem.Expand and Win32TreeViewItem.Collapse actions did not check whether the item was already expanded or collapsed.

The WPFMenu.Close action did not close the menu.

The WPFToolBar.wIsCheckButton property returned False for ToggleButton items.

TestComplete recorded actions with Visual Basic 6 tab controls (TabStrip) in black-box mode.

Log messages posted by the Win32TreeView object actions now contain the full path to the specified tree node.

TestComplete posted a wrong log message upon expanding (collapsing) an already expanded (collapsed) tree view node.

The Win32ListView.ClickItem action worked twice slower in TestComplete 6 than in TestComplete 5.

The Win32ListView.ClickItem action did not activate the .NET application window that contained the list view control.

The Win32ListView.ClickItem action logged the “Improper command” error when the specified subitem was not found.

The Win32ListView.ClickItem action could miss the specified item.

The Win32ListView.CheckItem action did not verify whether the list view had check boxes.

The Win32ListView.SelectItem action did not post the message about an item being selected to the test log.

The Win32ListView.FocuseItem and HotTrackSelect actions posted an incorrect error message in case -1 was passed as the Item parameter value.  

In certain cases, the Win32ListView.wItem property could not retrieve captions of list view items and subitems.

In certain cases, the Win32ListView.wImage property returned an incorrect value.

The Win32ListVeiw.wStateImage property returned an incorrect value.

The Win32ListView.wIconBounds, wItemBounds, wSelectBounds and wTextBounds properties returned incorrect values.

The Win32ListView.wGroup property did not work if the tested .NET application didn’t have a manifest.

The Win32ListBox.SelectItem action could not select or deselect all list box items.

The Up and Down actions of the Win32UpDown object posted incorrect messages to the test log.

TestComplete could not minimize a window if its main menu was opened.

The Minimize and Restore actions did not have any effect on the command interpreter (cmd.exe) window.

Some actions posted incorrect messages to the test log.

The text of log messages included names of the controls’ items with unexposed wildcards.

The script execution engine has been optimized.

The process of TestRecorder 6 Demo did not close upon closing the application being recorded.

The Yahoo messenger crashed when TestComplete was recording a script.

An access violation could occur when calling an ODT class method with parameters.

TestComplete could crash while populating the Locals panel.

TestComplete could crash upon reactivating the Data-Driven Testing plug-in.

The Size column of the Files editor displayed an empty value for empty files (that is, files having the size of 0 bytes).

The Project Explorer panel displayed the project node description even after closing the project.

The Picture.Compare method parameters were in a wrong order in the code generated by the Create Region Checkpoint dialog if the Transparent option was enabled.

The Storages.Registry.Section.Clear method deleted the corresponding section instead of clearing it.

The script failed to start if it was recorded via low-level procedures and the corresponding procedures collection was renamed both in the Project Explorer and in the script code.

A number of issues in the MSBuildTC6Task.dll assembly have been fixed.

The –console command-line parameter of the PRegister utility did not work.

PRegister had exit code 0 even if wrapper files were not generated.

A number of crash dumps reported by customers have been fixed.