Known Issues - Web-based SAP

General Limitations

It is not recommended to work with other Web-based add-ins when the SAP Solutions Add-in is loaded. The SAP Solutions Add-in modifies certain Web configuration settings that may affect other add-ins or applications.

Object Identification
  • In some cases, when more than one browser is open during the test run, 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 BoxObject Identification dialog box for future test recording.

  • Minimized or collapsed iViews may not be recognized correctly.

  • 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 will be able to recognize it during the test run.

  • When using the Object Spy or creating a checkpoint on an object inside an SAP Web table cell, 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.

  • 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.

Recording
  • When recording and running steps on a table control, only the table content that is visible on the client is actually available.UFT 11.51 Perm Lim, No Defect

  • 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.

  • 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.

  • When recording a SAPList object, you need to click the input part of the list, not its button part in order to enable to recognize the object. UFT11.50 Defect 106871

  • 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.

Running tests on SAP applications
  • During a run session, the SAP platform response time may be slower than the time it takes for to run the corresponding step.

    Workaround: Add a Wait statement prior to the relevant step. UFT 11.51 Defect id 106862

  • In some cases, when running tests on SAPEdit, SAPNavigationBar, or SAPPortal, you may receive a Cannot find object error. UFT 12.02 Defect 120915

    Workaround: Do one of the following:

    • Ensure that the object properties are unique and correct.

    • Modify the registry as specified below:

      For 32 bit computers: In the HKEY_LOCAL_MACHINE\Software\Mercury Interactive\QuickTestProfessional\MicTest\AbortIfHangInSendData key, set the value of DWORD to 0.

      For 64-bit computers: In the HKEY_LOCAL_MACHINE\Software\Wow6432Node\Mercury Interactive\QuickTestProfessional\MicTest\AbortIfHangInSendData key, set the value of DWORD to 0.

  • 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 using 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.

SAPUI5-specific limitations
  • Because the SAPUI5 add-in supports both desktop and mobile applications, not all methods for all objects are supported for both desktop and mobile applications. UFT 12.50 Defect 124418

  • When running a test or component on SAPUI5 test objects, application Alert messages for some objects are not displayed.

    Workaround: Do one of the following:

    • Make sure your test does not contain steps that need to be performed on the Alert message.

    • Add an If statement to your test for the object that triggers the alert to check if the Alert exists.

  • If your SAPUI5 application contains nested table objects, inserting a checkpoint on the nested table object shows only the parent SAPUITable object. UFT 12.02 120966

    Workaround: Select the nested WebTable objects and create checkpoints for the WebTable object instead of the parent SAPUITable object.

  • When using the Object Spy to view an SAPUIMenu object or recording an SAPUIMenu object which is hidden in closed status, you may be unable to: UFT 12.50 Defect 121953, 123369 UFT 12.51 Defect 23226

    • Add the menu object to the repository on Firefox and Chrome browsers with the Add Object to the Repository button

    • Record the object on Chrome browsers.

    • Add checkpoint or output value steps in Firefox and Chrome browsers

  • When working with mobile SAPUI5 applications, cannot use the Object Spy on some disabled controls (like the SAPUIButton and SAPUITextEdit) due to the application object properties. UFT 12.50 Defect 122446

  • When working in Internet Explorer 11, if your application requires you to scroll down to perform a button click, the SAPUIButton.Click method does not click the button.

    Workaround: Use a SAPUIButton.Submit method instead. UFT 12.54 Defect 27862

  • Using the ChildObjects method on some objects returns a different result between browsers. UFT 12.51 Defect 23697

SAPWDJ-specific limitations
  • If you try to record objects in a SAP WDJ application without the SAPWDJ add-in loaded, records only some of the objects correctly. UFT 12.50 Defect 123393

    Workaround: Restart and load the SAP WDJ Add-in.

  • During a run session, the response time of the SAP platform running a SAP Web Dynpro Java (WDJ) application may be slower than the time it takes for to run the corresponding step.

    Workaround: Add a Wait statement prior to the relevant step or set the Delay each step execution option in the Test Runs pane of the Options dialog box (Tools > Options >  Testing tab > Test Runs node) to the necessary wait period (in milliseconds) UFT 11.51 Defect id 106862, 123776

  • The following functionalities are not supported for SAP WDJ applications:

    • Selection of non-visible table rows

    • Interaction with the application scroll bar

    • Menus inside table cells UFT 12.50 Defect 122754

    • Date navigator windows inside the application UFT 12.50 Defect 123388

  • When recording steps on an SAPWDJTable object, the SelectCell method is not always recorded if you are selecting non-editable cells. UFT 12.50 Defect 124675

  • If your table contains links that open a popup window, when using the SAPWDJTable.SelectItemInCell method to click thel link, does not run the the .SelectItemInCell properly. UFT 12.51 Defect 122756

    Workaround: Associate the linkFuncLibr function library with your test. This function library is found at <UFT installation directory>\dat\Extensibility\Web\Toolkits\SAPWDJ\FunctionLibraries\linkFuncLibr.qfl.

SAP Business Networks applications
  • Spying or adding checkpoints on an SAPWebExt List in SAP FieldGlass is not supported.

  • Checkpoints on SAPWebExtTable objects are not supported. UFT 12.54 Defect 28854

    Workaround: Do one of the following:

    • Restart UFT, clear the SAPWebExt addin and then add a checkpoint on a WebTable object.

    • Use the .GetCellData method

    • Add a checkpoint on the child WebTable of a SAPWebExtTable object.

SAP WebDynpro ABAP applications
  • A click operation on a SAPTable object is not recorded. UFT 14.00 Defect 30845

    Workaround: Manually add the object as a WebElement and add a WebElement. Click step to your test.

  • If a table object disappears in the application immediately after a select operation is performed, SelectCell methods are not recorded on the table object. UFT 14.00 Defect 30789

    Workaround: Manually add the SAPTable.SelectCell method after recording.

  • For some table objects which display dynamically during scrolling, the SAPTable.GetCellData method may not retrieve invisible cell data which is invisible.

    Workaround: Add steps to click the arrow of scroll bar to make the row visible and then use the GetCellData method with current row value.

    For example:

    'get value in row 1
    print Browser("WDR_TEST_C_TABLE [Web").Page("Web Dynpro Test Suite").SAPTable("[Demo Table Part 1]").GetCellData (2,4)
    For Iterator = 1 To 4 Step 1
        wait 1
        Browser("WDR_TEST_C_TABLE [Web").Page("Web Dynpro Test Suite").SAPButton("SAPButton_2").Click
    Next
    'get value in row 7 which is shown in line 4 after scroll
    print Browser("WDR_TEST_C_TABLE [Web").Page("Web Dynpro Test Suite").SAPTable("[Demo Table Part 1]").GetCellData (4,4)