What’s new in TestComplete 6.20
The changes listed below have also been applied to TestExecute 6.20 and TestRecorder 6.20, as these products are based on TestComplete’s technology.
New Features
The script debugger has been improved. Now you can change variables during script debugging.
TestComplete now supports Windows Server 2008, both 32-bit and 64-bit editions. This means that you can record and play back tests under Windows Server 2008. However, in order to run tests on Windows Server 2008, TestComplete must have the same or higher security privileges that those of the application under test.
The Playback group of the project's properties contains a new Recreate object after script stops setting that specifies how TestComplete manages ActiveX objects added to the ActiveXObjects project item.
You can now limit the number of child objects exposed by the MSAA Open Applications plug-in for the parent MSAA objects by using a new MSAAMAXCHILDCOUNT argument in the command line of your tested application.
When comparing two images of different sizes with the
Picture.Difference method, the method returned nil. Now, it posts an image to the test log that highlights the difference between the images.
When specifying class names in the WPF group of the project's properties, you had to skip namespaces. This limitation has been removed.
The speed of the Web testing engine has been improved. Also, the engine is now more stable.
Bug Fixes
The "Save All" command functioned too slowly if the project was opened in networked mode.
In some cases, the Clone Project operation did not work correctly.
TestComplete generated invalid C#Script code snippet for property checkpoints.
An exception occurred when calling the
NetworkSuite.Variables.AddVariable method.
The name of SOAP request parameters may be invalid script identifiers. It was impossible to assign values to these parameters from script code.
TestComplete could hang or crash when running a TestComplete 5.14 project suite on Windows 2000.
In certain cases, the Ctrl+Backspace shortcut did not function in the Object Browser.
The Sys.OSInfo object returned incorrect information for Microsoft Windows Server 2008 operating system.
A crash could occur in the Code Explorer panel when closing TestComplete.
The Code Editor might hang for some time when working with large script units and large projects.
The
Win32TrackBar.wTicPosition property could return an invalid value.
If the row indicator and titles were hidden in a
TDBGrid control, the ClickColumnHeader and ClickRowIndicator actions of the BorlandTDBGrid object did not post error message to the log and simulated mouse clicks over the grid cells.
A number of crash dumps reported by our customers.