QTP/UFt tip: Troubleshooting and Limitations for Web-based SAP application
- It is not recommended to work with other Web-based add-ins when the UFT Add-in for SAP Solutions is loaded. The Add-in for SAP Solutions modifies certain Web configuration settings that may affect other add-ins or applications.
- When recording and running steps on a table control, only the table content that is visible on the client is actually available.
- During a run session, the SAP platform response time may be slower than the time it takes for UFT to run the corresponding step.
Workaround: Add a Wait statement prior to the relevant step.
SAP Enterprise Portal
- Operations on the iView option menu and on objects within the page title bar of SAP Enterprise Portal are recorded as Web operations on the Frame object and not as SAP operations on the iView object.
-Minimized or collapsed iViews may not be recognized correctly.
- In some cases, when more than one browser is open during the test run, UFT is unable to correctly identify certain objects.
Workaround: Clear the Enable Smart Identification check box for the Browser test objects in the Object Repository window. You may also want to disable the Enable Smart Identification option for Browser test objects in the Object Identification dialog box for future test recording.
- In some cases, a frame in SAP Enterprise Portal may be recognized as a Web Frame object instead of an iView object. In some of these, the frame name is generated dynamically. Because the Web Frame object uses the name property to identify the object, you must modify the recorded name value to use an appropriate regular expression so that UFT will be able to recognize it during the test run.
SAP GUI for HTML—Internet Transaction Server (ITS)
- When using the Object Spy or creating a checkpoint on an object inside an SAP Web table cell, UFT may recognize the object as a WebElement (and not as the appropriate SAP Web object), if a click has not yet been performed on the object.
Workaround: Click on the object inside the SAP Web table cell before using the Object Spy or creating a checkpoint on it.
- Dragging the SAP GUI for HTML table scroll bar is not recorded.
Workaround: You can record scrolling in SAP GUI for HTML tables by clicking the scroll button. Alternatively, use the Step Generator or Editor to insert a SAPTable.Object.DoScroll ("up") or SAPTable.Object.DoScroll("down") statement in your test.
- The appearance of toolbar buttons may differ, and toolbar buttons may or may not be displayed, depending on the size of your browser window.
Workaround: Try to maintain the same browser window size and the resulting menu appearance when recording and running your test.
- When running a test on an ITS frame in an SAP Enterprise Portal iView, the ITS menu sometimes fails to operate properly.
Workaround: Enlarge the iView size and/or increase the Object Synchronization Timeout and then run the test again.
- When recording a SAPList object, you need to click the input part of the list, not its button part in order to enable UFT to recognize the object.
Using the Active Screen
- The Active Screen may not display the entire HTML page captured while recording your test.
Workaround: Resize the Active Screen so that it best fits the HTML page size.
- When testing an SAP Enterprise Portal application, it is recommended to set advanced authentication for Active Screen access (File > Settings > Web).
- Avoid using an Active Screen that was captured when a pop-up dialog was open to add an object from the main window to the object repository. Doing this results in an incorrect object hierarchy in the object repository.
Web-based CRM Systems
- When using UFT to test Web-based CRM systems, make sure that the CRM system is in test mode. You can do this by adding "?sap-testmode=X" to the URL.
You can find these details on the Add-ins guide document For UFT: http://support.openview.hp.com/selfsolve/document/KM00629369 from page 275 to 276