A checkpoint is a comparison (or verification) operation that is performed during testing. These operations are an essential part of the testing process as they control whether the tested application functions properly.
You may need to perform verifications of different kinds, for instance:
- If you test a new control, you may need to verify that after a user performs actions, certain control properties contain the appropriate values. The operation that will check the property value is called a property checkpoint.
- If the tested application exports data to a file, you may need to compare this file with a baseline copy. This check is called a file checkpoint. Similarly, to verify that the application changes the database as expected, you create a database checkpoint.
- When testing a web page, you may need to verify that the page does not contain broken links or that all the IMG elements have the ALT attribute. This kind of check is called a web checkpoint.
To simplify the creation of the comparison code, you can use TestComplete special dialogs and wizards. You can invoke these wizards and insert the checkpoints into your scripts and keyword tests during the recording. This functionality frees you from reviewing the recorded script or keyword test and inserting checkpoints after the recording is over.
TestComplete includes a special project item, called Stores, that contains collections of images, file references, database values and other elements for comparison purposes. You can use this project item to save baseline copies of the compared elements. TestComplete uses these element to perform the comparison. For more information about this project item, see Stores Project Item.
In TestComplete, you can create checkpoints of the following type:
(Deprecated) Object Checkpoints