TestComplete 6 is currently under development, the information contained in this article is not final and may change at any time.
In general, to check if a test operation is successful, you gather data from an application's output, web page or other test item and compare it against an expected set of data, the baseline data.
If the captured and baseline data are the same, then the test is considered a success. A difference between the two signals possible bugs, so the tester should thoroughly investigate the test and application to find out the cause of the error.
Previous versions of TestComplete included special objects that let you compare files, images and object properties. In TestComplete 6 the comparison functionalities go further.
In addition to files, images and object properties you can easily compare databases, XML documents, web pages, web service responses and data of tabular controls. TestComplete 6 includes special dialogs and menu and toolbar items that greatly simplifies the creation of checkpoints.
We call the comparison actions checkpoints.
TestComplete 6 includes special dialogs and menu and toolbar items that greatly simplify the creation of checkpoints: you specify all the comparison settings in the dialogs and TestComplete automatically generates the comparison code, which you can insert into your script.
Using the new dialogs and menu items, you can create checkpoints for the following data items:
- Individual properties of an object
- Collecitons of objects’ properties
- Data of controls that display information in tabular form
- Data retrieved from a database’s table, view or query
- XML documents
- Web service responses
- Web pages
The baseline copies of data and comparison settings are stored in the Stores project item, which offers special collections for each checkpoint type:
You can create checkpoints at design time or during test recording. To create a checkpoint at design time, you select an item from TestComplete’s Checkpoints toolbar:
The same items are also added to the Recording toolbar. This gives you a possibility to create checkpoints during test recording:
The checkpoint creation procedure is similar for every data item, however it has specific traits.
Upon selecting the toolbar item, TestComplete displays the dialog or wizard, where you can specify various comparison settings. This dialog (or wizard) is specific to the checkpoint you are creating. You need to specify the comparison precision, the baseline copy location and so on. For instance, in when creating a property checkpoint, you specify the property name, the object to which the property belongs, the comparison condition and the expected value. When creating a database checkpoint, you specify the connection parameter to the database and the database’s table, view or query:
Create Property Checkpoint dialog
Create Database Checkpoint dialog
The parameters specified in the dialog (or wizard) are used to generate the script code that will perform the comparison or verification operation. This code is generated automatically upon closing the checkpoint creation dialog:
If you create a checkpoint during test recording, the generated code will be inserted into the recorded script. If a checkpoint was created at design-time, then you can copy the generated code to the clipboard and use it is copied to the clipboard.
TestComplete can also automatically save the baseline copy of data to the appropriate collection of the Stores project item.
During test execution, TestComplete gathers the actual data from the tested application or web page and verifies this data or compares it against the baseline copy stored to your TestComplete project. If the comparison fails, the test engine posts a detailed report to the test log. For instance, the following image shows the XML comparison results:
By using the described dialogs and menu items you can create the checking code easier and faster than in previous versions of TestComplete.
For complete list of features added to TestComplete 6, see http://www.automatedqa.com/betatest/tc6wn.asp.