In UFT, you can insert checkpoints to check to see that your application is running correctly. These checkpoints run as a separate test step in the overall test flow. You use output values to take a value produced by a specific step or object and pass this value to another step.
You can check a variety of different application objects using checkpoints:
|Object Type||Description of Checkpoint||Example of Use|
|Standard||Checks the values of an object's properties.||Check that a radio button is selected.|
Checks the property value of an image.
You check an image by selecting the Standard Checkpoint option and then selecting an image object.
|Check that the image source file is correct.|
Checks information in a table.
You check a table by selecting the Standard Checkpoint option and then selecting a table object.
|Check that the value in a table cell is correct.|
Checks the characteristics of a Web page.
You check a table by selecting the Standard Checkpoint option and then selecting a Web page in a browser.
|Check how long a Web page takes to load or if a Web page contains broken links.|
|Text||Checks that a text string is displayed in the appropriate place in an application.||Check whether the expected text string is displayed in the expected location in a test object.|
|Text Area||Checks that a text string is displayed within a defined area in a Windows-based application.||Check that an area of a dialog box includes text that was entered in another part of the application.|
|Bitmap||Checks an area of an application after capturing it as a bitmap.||Check that a Web page (or any portion of it) is displayed as expected.|
|Database||Checks the contents of databases accessed by an application or Web site.||Checks that the value in a database query is correct.|
|Accessibility||Identifies areas of a Web site to check for Section 508 compliance.||Check if the images on a Web page include ALT properties, required by the W3C Web Content Accessibility Guidelines.|
|File Content||Checks the text in a document generated or accessed during a run session.||Checks that the headers in a dynamically-generated PDF display the regional corporate headquarters contact information correctly.|
|XML||Checks the data content of XML documents.||
Check the content of an element to make sure that its tags, attributes, and values have not changed.
XML file checkpoints are used to check a specified XML file; XML application checkpoints are used to check an XML document within a Web page.
You can use a variety of different types of output values:
|Type of Object||Description||Example|
|Standard||Takes the value from most objects in your application and stores it.||Take the string output of an edit field.|
|File Content||Takes the output of a selected file or part of a selected file.||Take the output of an HTML page.|
|Table||Takes the output of the cells or selected cells of a table object.||Take the output of the cell in row 1, column 1 in a table object.|
|Text/TextArea||Takes the text output of an object or an area in the application.||Take the text output of an error message.|
|Database||Takes the output of database cells or selected database cells||Take the output of the database accessed by an object in your application.|
|XML||Takes the output of elements included in an XML document.||Take the output of the <price> attribute in an XML defining prices for a product.|
You can add most checkpoints and output values either while editing steps in the Keyword View or Editor or recording. The following exercises explain how to create some of the checkpoints described above.
When UFT creates a checkpoint or output values, it assigns a name based on information inside the checkpoint or output value - the checked value, for example. The checkpoint or output value name remains unchanged, even if you modify the information on which it was based. Keep this in mind when looking for checkpoints or output values displayed in the Keyword View. Note also, that UFT may shorted the name displayed in the Keyword View.
For additional details on checkpoints and output values, see the Unified Functional Testing User Guide.