Skip to main content

Mobile site element identification on emulator or device

When writing automated test for desktop web application then it is quite easy to identify application elements. Almost all popular browsers have built-in developer tool bar to facilitate the element identification.
It is also quite easy to identify element locator for mobile app by appium directly for ios and android apps (or UIautomatorviewer for android apps on Ubuntu). But how do you identify application elements for mobile site? Chrome browser comes for our rescue. Chrome can be used to identify mobile site elements loaded on a mobile device or emulator.


Launch chrome:/inspect on the chrome browser and you would see following screen when no device/emulator is configured -


Screenshot from 2016-07-04 11:45:59.png
Make sure your emulator version is on Android 4.0 or higher. Once I launch the android emulator then it is listed on chrome inspect panel -


Screenshot from 2016-07-04 12:15:21.png


Launching the browser would display corresponding information on chrome inspect panel -


Screenshot from 2016-07-04 12:16:51.png


Click the inspect link and it would open bring developer toolbar, displaying the elements of mobile site just like a desktop website.


Screenshot from 2016-07-04 12:19:48.png


Click on the “Switch to portrait screencast” in developer toolbar and you will see image of emulator in developer tool bar -
Screenshot from 2016-07-04 12:25:15.png


Hence no need to switch back and forth between chrome and mobile device/emulator as you will be able to drive the mobile site UI from within developer toolbar -


Screenshot from 2016-07-04 12:28:16.png


Doing any operation on device image on developer toolbar would also reflect it on emulator/device  -


Screenshot from 2016-07-04 13:24:42.png


To bring control on a specific element, click the magnifying glass icon on developer toolbar and hover it on the element on which control is to be brought -


Screenshot from 2016-07-04 13:42:38.png


Screenshot from 2016-07-04 13:44:42.png


Now hit the escape key on your developer toolbar and start testing your element locators :)


Screenshot from 2016-07-04 14:07:48.png


Screenshot from 2016-07-04 14:14:06.png


Popular posts from this blog

How can you save resources when instantiaing driver?

I asked on my previous post about what was wrong in instantiating driver on set up method? And here is the solution video on my YouTube channel (After 5 years of gap I finally added new video tutorial :)) The solution described on video tutorial uses following set up - public class BaseClassOnDemandDriverSetup { private WebDriver driver ; @BeforeMethod public void setupTest () { // Any other set up goes here } @AfterMethod public void teardown () { if ( driver != null ) { driver .quit() ; } } public WebDriver getDriver () { if ( driver == null ) { WebDriverManager. chromedriver ().setup() ; driver = new ChromeDriver() ; } return driver ; } }

Security Testing and Selenium

I have come across many articles which talk of carrying out security testing with selenium however I found it very cumbersome to set up such tests. This is what this tutorial is going to make easy for you. It cover. My next Security Testing and Selenium YouTube video covers following - Importance of having security testing on CI What is dynamic application security testing Recommended tools from https://owasp.org/www-community/Vulnerability_Scanning_Tools What is https://owasp.org/ ?   Using https://www.zaproxy.org/    Project setup  <dependency> <groupId> org.zaproxy </groupId> <artifactId> zap-clientapi </artifactId> <version> 1.9.0 </version> </dependency> <dependency> <groupId> org.zaproxy </groupId> <artifactId> zap </artifactId> <version> 2.10.0 </version> </dependency> Start ZAP daemom (headless) mode  ./zap.sh -daemon -host 127.0.0.1 -port 8080 -config api.addrs.a

Using chrome console to test xPath and css selectors

Since the advent of selenium there have been many plugin to test xPath / css selectors but you don’t need any of them if you have chrome browser. Using Chrome console you can test both xPath and css selectors. Launch website to be tested in chrome browser and hit F-12 and you would see chrome console opened in lower pane of application - Hit escape key and console would open another pane to write element locators - And now you can start writing xPath or css selectors in chrome console and test them - The syntax for writing css id - $$(“ ”) And hit the enter key. If your expression is right then html snippet of the application element corresponding to the css selector would be displayed - If you mouse over the html snippet in chrome console then it would highlight the corresponding element in application - If you want to clean console of previously written element selectors then just hit ctrl+L keys and chrome console would be empty again. Pro