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.
To enable UFT to record steps on standard Windows controls during an SAP GUI for Windows recording session, it is a must to switch to Standard Windows Recording mode prior to performing steps on these controls. (If switching to Standard Windows Recording mode after performing an operation on a standard Windows control, both UFT and the SAP application may sometimes become unresponsive.)
This task describes how to toggle between the relevant recording options.
To switch to Standard Windows recording mode while recording a test in an SAP GUI for Windows application:
On the Record toolbar, select Standard Windows Recording from the Recording Modes drop-down, or press Alt+Shift+F3.
To record steps as SAP GUI for Windows objects again:
Do one of the following:
· On the Record toolbar, select Default from the Recording Modes drop-down.
· Stop the recording session.
This restores the normal recording mode for SAP GUI for Windows.
The theoretical limit is 32766, but the practical limit depends on a number of factors:
– How the licenses are used;
– Network bandwidth;
– The machine the License Server is installed on.
– How many users are attempting to get a license at a time, etc.
If 32766 machines are all trying to get a single license key (feature) from the License Server at the exact same time, this would not work on any setup. A more practical limit, of what would be considered general usage, should be closer to 100, but it depends more on factors other than what the License Server itself can handle.
When recording and running tests or business components on SAP GUI for Windows applications, consider the following:
· When working in tests, the Record and Run Settings dialog box in UFT enables to specify a server and client to open at the beginning of every test record and run session. The servers available in the dialog box are the same as those available in the SAP Logon Pad and SAP Logon dialog box.
· When recording a business component on an SAP GUI for Windows session, the Record and Run Settings dialog box is not available. Instead, it is needful to open the SAP session manually or include statements in the business component that connect to the SAP server (using the SAPGuiUtil test object).
· It can also be recorded specific operations in SAP GUI for Windows Application in Standard Windows Recording mode, if required.
· As recording a test or business component on the SAP GUI for Windows application, UFT records the operations performed. UFT works directly with the SAP GUI Scripting API to record operations. Therefore, although UFT records a step for each operation performed, it adds the steps to the test only when API events are sent to UFT (when information is sent to the SAP server).
· When selecting a test step in UFT, the corresponding object is highlighted in the Active Screen (unless not choosing to capture Active Screen information when reordering the test). However, the values of the object properties stored with the Active Screen are the values of the properties at the time that the steps were added to the test (when the step are performed that sent information to the SAP server). These values may potentially be different from the values of the properties at the time that the selected step was actually performed.