Details for checkpoints and output values in SAP GUI
· When inserting a table checkpoint (tests only), consider how other steps performed on the table may affect the checkpoint.
Example 1: If having a step in test that clicks the Total toolbar button on a grid control, that click refreshes all data in the table. The refresh could potentially cause a table checkpoint on a cell in the table to fail.
Example 2: If clicking a toolbar button in a grid control that adds rows to table before creating a table checkpoint, the extra rows are captured as part of the grid checkpoint (if capturing all rows). Therefore, confirm that the same rows are displayed during the run session.
· To insert a new table checkpoint while editing test or business component, the actual table or grid must be open to the appropriate level or view. This is true even if Active Screen (tests only) contains a capture of the table or grid.
· In general, it is not necessary to open the table or grid in the application to edit an existing checkpoint. However, if going to modify the row range for the checkpoint, the actual table or grid must be open to the appropriate level or view.
· When creating a checkpoint on ActiveX grid controls (these generally have toolbars), UFT captures the data from all columns and all rows in the grid in the table checkpoint. If not doing the needed to check data from all rows in the grid, it can be specified which rows to include in the checkpoint in the Define Row Range dialog box. It can be also increase or decrease the number of rows included in the checkpoint at a later time.
· The Visible Rows option in the Define/Modify Row Range dialog box is not available for checkpoints created on grid controls.