Use the Table Checkpoint operation to compare the data displayed in a tabular form with a baseline copy of the data that is stored in your project, or to update the baseline copy with the data retrieved from a control.
Whether the operation compares or updates the content depends on the Update Table elements setting (you can modify it in the Stores Options dialog). By default, the setting is disabled, and the operation performs the comparison. Enable the setting for the operation to update the stored baseline copy.
When you add the operation to your test, TestComplete displays the Checkpoint wizard, where you specify tabular data to verify. It can be either the data displayed by a grid control or the data rendered on the screen (for example, as part of a PDF file or in chart). TestComplete will retrieve the tabular data and save it as a new Table element of the Stores > Tables collection. This data will be used as a baseline copy. If the operation works in comparison mode, during the test run, TestComplete will compare the actual data with this saved copy. If the operation works in update mode, TestComplete will update the baseline copy with the actual data retrieved during the test run.
The operation is available in TestComplete and can verify the data displayed by supported controls by default.
To be able to retrieve tabular data from controls by using optical character recognition, the following requirements must be met:
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.
In comparison mode, if the control’s data coincides with the saved baseline copy, the operation returns True and posts a checkpoint message () to the test log. Otherwise, the operation returns False and posts an error message () to the log.
In update mode the operation always returns True.
The operation is analogue to the
Table.Check scripting methods.
The operation cannot have child operations.
The operation has one parameter:
To specify another Table element that will be used by the comparison procedure:
Select the operation’s row in the test.
Select the Operation cell and then click within it or press F2. This will activate the in-place editor.
Choose the desired Table element from the drop-down list.
Press Enter to confirm the change and close the in-place editor, or press Esc to close the editor discarding any changes.
An alternative approach to modifying checkpoint parameters is to repeat the operation’s setup steps in the Table Checkpoint wizard. To invoke this wizard, double-click the operation in the Keyword Test editor.
By default, if the Table Checkpoint operation cannot find or access the object the contents of which it verifies, it waits for the object for a period that the Playback > Auto-wait timeout property of your project specifies. If the object has not been found by the end of the period, the operation fails.
For information on database checkpoints, on creating and modifying them and on how the comparison procedure works, see the About Table Checkpoints section.