{"id":575,"date":"2021-06-13T05:27:22","date_gmt":"2021-06-13T05:27:22","guid":{"rendered":"https:\/\/rahulshettyacademy.com\/blog\/?p=575"},"modified":"2021-10-31T12:34:10","modified_gmt":"2021-10-31T12:34:10","slug":"appium-inspecting-elements-using-uiautomatorviewer","status":"publish","type":"post","link":"https:\/\/rahulshettyacademy.com\/blog\/index.php\/2021\/06\/13\/appium-inspecting-elements-using-uiautomatorviewer\/","title":{"rendered":"Appium : Inspecting elements using UIAutomatorViewer"},"content":{"rendered":"

Inspecting elements using UIAutomatorViewer<\/h3>\n

Before starting writing test scripts, we need to identify elements using attributes such as  id, name, class etc to perform actions. In order to identify elements, we use UIAutomatorViewer<\/b>  and Appium inspector<\/b> to capture a snapshot of the current device screen which shows the hierarchy of the UI components arranged in the screen.<\/p>\n

UI Automator Viewer<\/a> is a GUI tool that comes with Android SDK which is used to inspect UI components of an Android Application and view the properties associated. We can find it in the Android SDK \u201ctools\u201d folder with the file name ‘uiautomatorviewer.bat’ on Windows.<\/p>\n

How to work with UIAutomatorviewer?<\/h3>\n

There are several ways by which we can launch the uiautomatorviewer.<\/p>\n

    \n
  1. From manually going to the path where uiautomatorviewer exists (android SDK folder) and run the batch file (for windows).<\/li>\n
  2. Manually to the location via terminal and run the uiautomatorviewer sh file (for mac). Note: Execution permission should be given to the file.<\/li>\n
  3. You can add alias to run directly via terminal. In Mac machine add it in bash_profile file.<\/li>\n<\/ol>\n

    Example:<\/strong><\/p>\n

    alias inspector=’$ANDROID_HOME\/tools\/bin\/uiautomatorviewer’<\/p>\n

    For Windows<\/h5>\n

    \"\"<\/p>\n

    For Mac<\/strong><\/p>\n

    \"\"<\/strong><\/p>\n

    How to access elements using UIAutomatorViewer?<\/h3>\n
      \n
    1. Connect device to the PC via USB cable.<\/li>\n
    2. Ensure that you have enabled USB Debugging mode for the device connected.<\/li>\n
    3. Run adb devices command in command prompt\/terminal to check if device is detected and online\/available.<\/li>\n
    4.  If the device is not detected then below error would be shown.<\/li>\n<\/ol>\n

      \"\"<\/p>\n

      5. The UiAutomatorviewer will be shown below screen.<\/p>\n

      \"\"         <\/p>\n

                  6. Open an application and click the device screenshot <\/b>icon from right up corner.<\/p>\n

      \"\"<\/p>\n

      7. After clicking on ‘Device Screenshot’<\/b>, an image of the current screen will be loaded in the UIAutomatorViewer and we can use the mouse to click on any element and see the details of that element. You can also use the hierarchical tree in the top right to browse to a particular element.<\/p>\n

      \"\"<\/p>\n

      In the above image, the left side of the uiautomatorviewer shows captured screenshot and the right side panel is divided into two parts:<\/p>\n

      Part 1<\/b> – Upper part shows the UI XML snapshot shows the hierarchy of UI components arranged in the screen layout<\/p>\n

      Part 2<\/b> – The \u2018Node Detail\u2019 at the right bottom shows details of that element based on the UI components selected.<\/p>\n

      In the above screen shot, text area \u2018Enter your Name\u2019 shows with a red outline and its details are shown in the bottom right section ‘Node Detail’.<\/p>\n

      Note: UIAutomatorviewer works with Android native app elements only.<\/b><\/p>\n

      How to work with Appium inspector?<\/h3>\n

      A default inspector available in standalone appium (not in the npm version)  is called appium inspector<\/b>. Which can be used to inspect android and iOS elements. It simply mirrors the screen of the device and we can interact with it and get the details of the elements. Lets see how we can launch and work with it.<\/p>\n

        \n
      1. Launch appium for your application\/programs menu.<\/li>\n
      2. Click to search icon from right up corner.<\/li>\n<\/ol>\n

        \"\"<\/p>\n

                 3.Add correct desired capabilities as per your device\/emulator and application. Then click on the start session<\/b> button.<\/p>\n

        \"\"<\/p>\n

                 4. It will open the App screen , App Source (the hierarchy of element) and Selected Element Pane (The attributes and associated values of the element).  You can use this to create locators which will uniquely identify the element.<\/p>\n

        \"\"<\/p>\n

                  5. You can provide .apk or .app file in desired capabilities inside appium inspector which will install and launch the app. Refer to the screenshots below.<\/p>\n

        \"\"<\/p>\n

        \"\"<\/p>\n

                   6. Best thing about appium inspector is that you can verify your written locator on screen. Check below screenshots.<\/p>\n

        \"\"<\/p>\n<\/p>\n

        If your locator is correct then it will highlight the associated element.<\/p>\n

        \"\"<\/p>\n

        Writing locators<\/h3>\n
        How to capture screenshot<\/h5>\n
          \n
        • Open the app on simulator.<\/li>\n
        • From terminal run below command<\/li>\n<\/ul>\n

          xrun simctl io booted screenshot <filename.jpg><\/strong><\/em><\/p>\n

          How to record iOS simulator screen from terminal<\/h5>\n
            \n
          • Open the app on the simulator.<\/li>\n
          • From terminal run below command<\/li>\n<\/ul>\n

            xrun simctl io booted recordVideo <filename>.<file extension><\/strong><\/em><\/p>\n

              \n
            • Press ctrl+c<\/strong> to stop recording.<\/li>\n<\/ul>\n

              I hope you learned something new on inspecting elements using UIAutomatorViewer<\/b> .<\/p>\n","protected":false},"excerpt":{"rendered":"

              Inspecting elements using UIAutomatorViewer Before starting writing test scripts, we need to identify elements using attributes such as  id, name, class etc to perform actions. In order to identify elements, we use UIAutomatorViewer  and Appium inspector to capture a snapshot of the current device screen which shows the hierarchy of the UI components arranged in […]<\/p>\n","protected":false},"author":1,"featured_media":886,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[19],"tags":[],"class_list":["post-575","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-appium","post-wrapper","thrv_wrapper"],"_links":{"self":[{"href":"https:\/\/rahulshettyacademy.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/575","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rahulshettyacademy.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rahulshettyacademy.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/rahulshettyacademy.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/rahulshettyacademy.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=575"}],"version-history":[{"count":6,"href":"https:\/\/rahulshettyacademy.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/575\/revisions"}],"predecessor-version":[{"id":1276,"href":"https:\/\/rahulshettyacademy.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/575\/revisions\/1276"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/rahulshettyacademy.com\/blog\/index.php\/wp-json\/wp\/v2\/media\/886"}],"wp:attachment":[{"href":"https:\/\/rahulshettyacademy.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=575"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rahulshettyacademy.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=575"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rahulshettyacademy.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=575"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}