Forum Discussion
HKosova
Alumni
14 years agoHi Pasha,
I'm glad it's working fine now!
As for your question about table checkpoints. A table checkpoint compares data in the grid with baseline data stored in the project item Stores > Tables > checkpoint_name. The baseline data is copied from the grid when you create the checkpoint, that is, the grid's current data at that moment is considered as the baseline data. You can view and edit the baseline data by double-clicking this item in the Project Explorer.
If data in your tested grid changes during the test run and you need to verify data at different moments, you have several options:
* create and use several checkpoints with different baseline data;
* use the same checkpoint in different places in your test, and set the checkpoint's baseline data at run time via Tables.checkpoint_name.Values(row, column);
* write a custom verification routine that will iterate through the grid cells using the wValue(row, column) property and compare cell values with the baseline values.
When using table checkpoints, you can also exclude some rows, columns or cell values from comparison -- either when creating the checkpoint, when editing the checkpoint's baseline data in the editor or at run time via Tables.checkpoint_name.ValuesSelected(row, column).
For more information about using table checkpoints, please see Creating Table Checkpoints and How the Table Comparison Works in the TestComplete documentation.
I'm glad it's working fine now!
As for your question about table checkpoints. A table checkpoint compares data in the grid with baseline data stored in the project item Stores > Tables > checkpoint_name. The baseline data is copied from the grid when you create the checkpoint, that is, the grid's current data at that moment is considered as the baseline data. You can view and edit the baseline data by double-clicking this item in the Project Explorer.
If data in your tested grid changes during the test run and you need to verify data at different moments, you have several options:
* create and use several checkpoints with different baseline data;
* use the same checkpoint in different places in your test, and set the checkpoint's baseline data at run time via Tables.checkpoint_name.Values(row, column);
* write a custom verification routine that will iterate through the grid cells using the wValue(row, column) property and compare cell values with the baseline values.
When using table checkpoints, you can also exclude some rows, columns or cell values from comparison -- either when creating the checkpoint, when editing the checkpoint's baseline data in the editor or at run time via Tables.checkpoint_name.ValuesSelected(row, column).
For more information about using table checkpoints, please see Creating Table Checkpoints and How the Table Comparison Works in the TestComplete documentation.