How to Use Checkpoint in QTP

A checkpoint allows you to identify if the Web site or application is functioning properly controlled or not by comparing a current value of a particular property with the expected value for that property.

By default, the control point name of the object is called to verify that the checkpoint is being performed. They can alter the name of the checkpoint if necessary. After adding a checkpoint, QuickTest adds a checkpoint in the current row in the view of keywords and adds a checkpoint Time statement at the hearing of experts.

Types of Checkpoints:

• Standard checkpoint.
• Image checkpoints.
• Bitmap Checkpoint.
• Bitmap Checkpoint.
• Accessibility Checkpoint.
• Text Checkpoint.
• Page Checkpoint.
• XML checkpoints.

Standard checkpoints permit checking the object property values in the Website or application under check. Standard checkpoints evaluate (compare) the expected values of object properties captured during recording to the object's current values during a run session. For example they can check that a radio
button is activated after it is selected. Standard checkpoints are supported for all add-in environments.
Standard checkpoints can be used to perform checks on

Images,

Tables,
Other objects within your application or Web site.

Standard checkpoints can be created for all supported testing environments (as long as the appropriate add-in(s) are loaded).
Image checkpoints let you check the properties of an picture in the application or Web page. For example, you can check that a selected image's source file is correct or not. An picture checkpoint can also be created by inserting a standard checkpoint on an picture object. Picture checkpoints are supported for the Web add-in environment.
With Bitmap Checkpoint they can check an area of a Web page or application as a bitmap. While generating a check, they must specify the area to check by selecting an object. An entire object or any area within an object can be checked. Bitmap checkpoints are supported for all add-in environments.
By adding table checkpoints to the check, they can check the content of tables displayed in the application. For example, they can check that a specified value is displayed in a positive cell. Positive environments also support checking the properties of the table object. For example, a check that a table has the expected number of rows & columns. A table checkpoint can also be created by inserting a standard checkpoint on a table object.
Accessibility Checkpoint recognizes areas of your Web-site that may not conform to the World Wide Web Consortium (W3C) Web Content Accessibility Guidelines. For example, check if the images on a Web page include ALT properties, necessary by the W3C Web Content Accessibility Guidelines.
Accessibility checkpoints are supported for the Web add-in environment        
Checkpoint control page features a Web page. For example, you can check the time a web page takes to load or if a Web page contains broken links. A page checkpoint can also be created by inserting a standard checkpoint on the page object. Page checkpoints are supported for the Web add-in environment.
QuickTest can check that a string is displayed in the appropriate place in an application or a Web page with text Checkpoint. The text checkpoints are compatible with the Web add-in environment, and some Web-based add-in environments.
The contents of a database to access your application may be verified by the Checkpoint database. The checkpoint database is compatible with all the add-in settings
By adding XML checkpoints for verification, you can check the contents of individual files or XML data documents that are part of the Web application. Checkpoint XML option is compatible with all the add-in settings.