Checkpoints - Overview
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 Training 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.
Region Checkpoints
A region checkpoint is a test operation that verifies that an application’s window or control or an arbitrary area inside an application’s window or control is displayed correctly. Verification is done by comparing the actual image of the window, control or area in your application with the baseline image stored in your test project.
In keyword tests, region checkpoints are performed using the Region Checkpoint operation:
In scripts, region checkpoints are performed using the
Regions.RegionCheckpointName.Check method:How a Region Checkpoint Works
When you run a test, TestComplete captures an image of the specified window or control in your application (the corresponding window or control must exist in your application at that moment), checks the captured image against the stored baseline image (by performing pixel-by-pixel comparison) and reports the results.
For detailed information on how image comparison in TestComplete works, see How Image Comparison Works. For information on factors that may affect verification results, see Factors Affecting Image Comparison.
How to Create Region Checkpoints
You can add region checkpoints to your test during the test recording and at design time.
TestComplete provides the Checkpoint wizard that guides you through the creation and configuration of region checkpoints. For detailed instructions on using the wizard, see Creating Region Checkpoints.
When you create a region checkpoint, TestComplete captures an image of the specified control or window in your application and stores the image to the project’s Stores | Regions collection. This image will be used as a baseline image during the test run.
Region Checkpoint Results
During the test run, region checkpoints perform a pixel-by-pixel comparison of actual images of objects and areas in the application under test with baseline images.
If images match, the checkpoint logs a success message. Otherwise, it logs an error message.
The Additional Info panel of the test log reports differences (in size, color or pixels) found between images.
The Picture panel of the test log displays the expected and the actual images.
On the Picture panel, you can activate the comparison mode to see the difference between the expected and the actual images easily.
For More Information Visit Mindmajix
Comments
Post a Comment