About Table Checkpoints

Table checkpoints are available in TestComplete by default.

To be able to create table checkpoints by using optical character recognition for controls that TestComplete does not support directly, the following additional requirements must be met:

See requirements

See requirementsSee requirements

• Your TestComplete version must be 14.40 or later.

• You need an active license for the TestComplete Intelligent Quality add-on.

• The Intelligent Quality add-on must be enabled in TestComplete.

• Optical Character Recognition support must be enabled in TestComplete.

• Your computer must have access to the ocr.api.dev.smartbear.com web service. If you have firewalls or proxies running in your network, they should allow your computer to access the web service.

• Your firewall must allow traffic through port 443.

For details, see Optical Character Recognition - Requirements.

You can add table checkpoints to your tests during the test recording and at design time. TestComplete provides the Table Checkpoint wizard that guides you through the process of creating and modifying table checkpoints. For detailed instructions on using the wizard, see Creating Table Checkpoints.

When you create a table checkpoint, TestComplete retrieves the specified tabular data and stores it in a Table element of the project’s Stores > Tables collection. This data will be used as the expected data during the verification. The name of the object to be verified is also stored by the Table element’s settings.

You can use table checkpoints to verify data of a wide range of standard Windows and third-party controls that display their data in the tabular form. For the complete list of supported controls, see Supported Controls.

If your tested tabular control is not supported by TestComplete, you can still verify its content. TestComplete will extract its data by using optical character recognition (OCR).

When you run the test, the table checkpoint obtains the specified control in your application (the control must exist at the moment), retrieves the actual data contained in the control, checks the actual data against the baseline data stored in the project and reports results.

For detailed information on how the table verification procedure works, see How the Table Verification Works.

During the test run, table checkpoints check the actual data of the control against the baseline data stored in your project.

If the actual and the expected data are equal, the checkpoint posts a success message to the test log.

Otherwise, the checkpoint posts an error message to the test log. The Details panel reports all differences found during the verification.

In addition to table checkpoints, to verify controls that display data in the tabular form, you can use the following approaches:

• To check the actual control’s data against data stored in a Table element, use the Tables.TableName.Compare and Tables.TableName.CompareWithObject scripting methods. These methods are similar to table checkpoints but allow you to specify whether to report differences found when comparing and what kind of message (an error, warning, informative message or no message at all) will be posted if the comparison fails.

• TestComplete provides special scripting methods and properties that let you retrieve data from the most popular controls. If your tested control is not supported by TestComplete and TestComplete cannot access its data by using those properties and methods, you can use optical character recognition to capture the needed data.

  To perform the verification, you can create a custom verification procedure that gets control data and then compares it using the if … then … else statement and comparison operations.

• To verify the number of items that a list-based control contains, create a property checkpoint for the control’s wItemCount property.

• To verify a control’s number of columns and rows, create property checkpoints for its wRowCount and wColumnCount properties.

• To verify that a single cell of a tabular control contains the relevant value:

  • If you can access individual cells of the table, create a property checkpoint for the control’s wValue(Row, Column) property.

  • If your control is not supported and you can only use OCR to capture its values, you can create an OCR Checkpoint for that cell. You can also use the OCR.Recognize.AsTable.Cell or the OCR.Recognize.DetectTable.Cell to get the cell and compare its text contents with a baseline value.

If your table checkpoint fails because the actual data of the control has been modified in your application, in order for the checkpoint to be passed successfully, update its baseline data.

For information on how to do this, see Updating Table Checkpoints.

TestComplete includes a sample project that demonstrates how to create table checkpoints:

<TestComplete Samples>\Desktop\Checkpoints\Table