Checkpoints, as the name says it all, it refers to a validation point that compares the current value with the expected value for specified properties of an object OR current state of an object with the expected value, which can be inserted at any point of time in the script. If the current and expected value match it generates a PASS status otherwise FAIL status.
- Standard: compares the expected values of object properties captured during recording to the object’s current values during a run session.
- Bitmap: Verifies the bitmap of an image or a full web page. It does a pixel by pixel comparison between actual and expected images. Bitmap checkpoints are supported for all add-in environments.
- File Content: Verifies the text in a dynamically generated or accessed file such as .txt,.pdf.
- Table: Dynamically verifies the information within a table (contents of cells of a table (grid) appearing in your environment). Not all environments are supported. You can also check various table properties like row height, cell width and so on.
- Text: Check expected text in a web-page or application. This text could be from a specific region of the application or a small portion of text displayed.
- Text Area: Verifies if the text string is displayed within a defined area in a Windows-based application, according to specified criteria.
- Accessibility: Verifies the page and reports the areas of the Web site that may not confirm to the World Wide Web Consortium (W3C) Web Content Accessibility Guidelines. These Guidelines make it easy for disabled to access the web. For example, check if the images on a Web page include ALT properties, required by the W3C Web Content Accessibility Guidelines. Accessibility checkpoints are supported for the Web add-in environment.
- Page: Standard Checkpoints created for a web page. It is used to check total number of links & images on a web page. Page Checkpoints can be used to check Load Time i.e. time taken to load a web page. It can also check for broken links.
- Database: Verifies the contents of a database accessed by the application under test. It creates a query during record time and database values are stored as expected values. Same query is executed during run time and actual & expected values are compared. Database checkpoints are supported for all add-in environments.
- XML: Verifies the content of the .xml documents or .xml documents in Web pages and frames. The XML Checkpoints option is supported for all add-in environments.
- Image: Enable you to check properties like source file location of a web image (XML Data, XML Schema, XML Data, etc.). Image checkpoints are supported for the Web add-in environment.
When the user wants to insert a checkpoint, one has to ensure that most of the checkpoints are supported during the recording sessions only. Once the user stops recording, checkpoints are NOT enabled.
Viewing Checkpoint Properties
After Inserting, in case a tester want to change the values, we can do so by performing right click on the keyword ‘checkpoint’ of the script and navigating to “Checkpoint Properties”.
- By default, the checkpoint name receives the name of the test object on which the checkpoint is being performed. We can change the name of the checkpoint if needed.
- You can locate the same checkpoints in object repository as well. It exactly shows what type of checkpoint and what are the expected values, time out values.
- After we add a checkpoint, UFT adds a checkpoint to the current row in the Keyword View and adds a “Check Checkpoint” statement in the Expert View.
- Standard checkpoints can be created for all supported testing environments (as long as the appropriate add-in(s) are loaded).
Looking for a Job Change in QA/Testing technology? Get Regular Job notifications @ WhatsApp!