The new TestComplete version 6 that was released just several days
ago includes lots of new exciting functionalities. Beta testers had a
chance to play with and check them during the beta testing period.
However, there are some nice features that were left beyond the beta. I
would like to highlight them, so you can start using them in your work.
- New Web Testing setting. The Web Testing group of your project properties includes a new setting called Make Page object as child of the browser process. This property specifies the location of the
Page object in the Objects tree. In earlier versions of TestComplete, to obtain the
Page object, you had to go through a hierarchy of windows that belonged to the browser process. For instance, if you tested web pages displayed in Firefox, the
Page object resided on the 7th level:
The new setting improves the situation. If it is enabled, TestComplete makes the
Page objects children of the browser process (iexplore for Internet Explorer or firefox for Firefox). So, now it is much easier to locate the
Page object in the objects hierarchy:
- Support for Firefox controls. TestComplete 5 did not recognize Firefox browser toolbars, menus and controls, so you were unable to simulate user actions on them. Version 6 recognizes the Firefox UI components and provides a special object -
UIPage - that lets you work with these components from your TestComplete scripts. All the UI сomponents are displayed as children of this
UIPage object. Firefox uses special XUL objects to implement toolbars, menus, dialog boxes and other controls. So, each object that corresponds to a Firefox UI component has two groups of methods and properties:
- Methods and properties of the appropriate XUL object (see www.xulplanet.com).
- Methods and properties provided by TestComplete for onscreen objects.
- New Pick Object button. TestComplete contains the Add Text to Script dialog that is used to insert arbitrary statements and comments into the script during recording. For instance, you can insert a call to an object’s method or the
if statement that checks an object’s property value. To refer to the desired object, you should type its name such as
Sys.Process("notepad", 2).Window("Notepad", "MyDoc - Notepad", 1).Window("Edit", "", 1). However, quite often you simply does not know the object name, so addressing the desired object in the dialog can be a problem.
In TestComplete 6, the Add Text to Script dialog contains a new Pick Object button that solves this problem:
By clicking this button you open the Pick Object dialog, in which you can specify the desired object by dragging the Finder icon () to that object:
After you close the Pick Object dialog, TestComplete will insert the specified object’s name into the current cursor position in the Add Text to Script dialog.
As you can see, now it is much easier to specify the object’ names.
A new Pick Button button has also been added to the Copy Text to Clipboard dialog that is used in some operations to copy generated script code to the clipboard and paste it to the script.