How TestComplete Records and Simulates Actions Over Visual Basic Controls
TestComplete provides support for standard Windows controls of Visual Basic applications. It automatically recognizes individual controls by their classes (the value of the
WndClass property) and lets you interact with them both at design time and during test recording or playback. Based on the object type, TestComplete provides a set of object-specific methods and properties for automating various interactions with the object. For example:
- Clicking a button is recorded and played back using the
Item selection in combo box, list box and list view controls -- using the
Clicks on grid cells -- using the
And so on.
When you are recording user actions over supported Visual Basic controls, TestComplete records these special methods and properties applied to the corresponding objects, rather than just coordinate clicks. You can see some of these methods, specifically,
ClickButton, in the sample test below.
Some controls, such as Label, do not have specific high-level operations associated with them, because users do not generally interact with these objects. However, these objects are also available in the application’s object hierarchy, and you can use them in your tests if needed. For example, you can create checkpoints for these objects.
List of Supported Visual Basic Controls
For a complete list of supported controls of Visual Basic applications and for a list of properties and methods that TestComplete provides for automating these controls, see the following topic:
Note that TestComplete provides support both for the listed controls and for their descendants. However, to make this possible, you need to specify the class name of your inherited control in the corresponding group of the project’s Object Mapping options.
Support for Tabular Controls
TestComplete allows creating Table Checkpoints for some Visual Basic controls that represent information in a tabular form (for a complete list of these controls see About Tables Collection). With table checkpoints you can retrieve and compare data of Visual Basic tabular controls.
Using Native Properties and Methods of Visual Basic Controls
In addition to control-specific methods and properties for automating operations over Visual Basic controls, TestComplete provides access to native properties and methods of these objects. These are the same properties and methods that are used in the application’s source code. You can use these native properties and methods to extend your tests and perform custom operations that are not available with standard properties and methods provided by TestComplete. For more information, see Accessing Native Properties and Methods of Visual Basic Objects.
Automating Unsupported Visual Basic Controls
You can test unsupported Visual Basic application controls by using the properties and methods provided by TestComplete to onscreen objects. Interactions with these controls are typically recorded as coordinate clicks.
You can also automate these controls by calling their native properties and methods from your test or by using various helper techniques described in the Interacting With Non-Compatible Application Objects topic.
To learn how to perform simple testing operations over application controls, see Working With Standard Windows Controls. This section includes a description of most common control-specific operations you may need to perform over the tested controls (for example, checking a button’s state, determining the number of combo box items, getting tab page images, expanding and collapsing tree view items and so on). For detailed information on approaches you can use to test your application controls, see the Working with Application Objects and Controls section.
In addition to control-specific operations, there are common tasks you may need to perform over any application object (for example, checking the object state, searching for an object or checking whether an object exists). For a complete list of these basic operations and for a description of how to perform them, see Common tasks.