Skip to Content

I am writing this article to explain a unique-out-of-the-box  concept of automating UI5 applications which addresses most of the  challenges faced in automating  UI5 applications

Some of the most common challenges in automating UI5 applications are:

  • Ids not stable

          In UI5 applications IDs are unique in a given page, but there is no guarantee that these IDs will remain stable across multiple iterations of the business flow, which makes it unfeasible to use it as a identifying locator for entire business flow.

  • No standard way of identifying UI5 element

          There are multiple ways (locators) to identify a UI5 element , some of them are   XPath,css,HTML tags,Ids (not stable over iterations as discussed above) etc. Stability of the automation scripts largely depends on how well these locators are used and how unique they are in identifying the UI5 element.

  • Sync issues

          Script failure due to syncing of UI5 elements is one of the biggest concern which is causing a lot of discomfort for the automation developers

    

  • Ease of use

          All of the points mentioned above makes it really difficult for automation developers to write stable scripts easily

  • Customization and Maintenance

          Again for the points mentioned above a lot of effort is required in maintaining the script stability whenever the properties of the locators change over       period of time

Solution

This UI5 Automation framework is a JavaScript based solution with two components

Browser extension – Displays the DoM structure of the UI5 page in UI5-elements-format, and a context menu  to capture the properties/events of selected UI5 element as shown in the figure below

Extension of Protractor – A JavaScript based tool, handles sync between UI5 elements exceptionally well. The data captured through browser extension context menu is used to create the business flow and run via this tool against any browser (perhaps mobile too…not yet tested)

The uniqueness of this framework is that the automation is based on the UI5 element structure and not normal HTML DoM, which makes it very stable in identification and maintainable ..

Screenshot (3).png

If this concept interests you, let me know if you want to understand the framework in depth and I can share more details. I will be modifying this blog to make it more elaborate and more clearer in coming days

Regards,

Asif Navalur

To report this post you need to login first.

12 Comments

You must be Logged on to comment or reply to a post.

    1. Asif Iqbal Navalur Post author

      Hello Haipeng,

      I doubt if that is possible, you can email to me and I can share you more details on how you could do integration testing of UI5 with Protractor

      (0) 
        1. Ravikant Kumar

          Hi Ivan,

          https://video.sap.com/media/t/1_h70s4kcs this link is not navigating us to the desired video. We are still stuck to index page of go.sap.com.

          Could you please tell us how to access content/video/information about Vyper for non-sap users.

          Guys,

          if anybody is aware of Release strategy (or) Date of release (or) any info/Learning material/ of Vyper. Please reply.

          thanks in advance.

          Regards
          Ravikant

          (0) 
    1. Ivan Mirisola

      Hi Farheen Taj,

      As of today, this extension has not been made publicly available to Google’s Chrome Web Store.
      Therefore, you will not be able to download it from any public site as of now.

      Maybe Asif can elaborate on the topic – if this will ever be made a public open source product or it will be made available from SAP Software Download Center as a licensed product.

      Regards,
      Ivan

      (0) 

Leave a Reply