Skip to main content

Using chrome console to test xPath and css selectors

Note: If you are new to java and selenium then start with selenium java training videos. 
 
 
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 -


Screenshot from 2016-07-27 13:35:38.png

Hit escape key and console would open another pane to write element locators -


Screenshot from 2016-07-27 13:37:30.png

And now you can start writing xPath or css selectors in chrome console and test them -
The syntax for writing css id - $$(“”)


Screenshot from 2016-07-27 13:43:27.png


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 -


Screenshot from 2016-07-27 13:45:11.png


If you mouse over the html snippet in chrome console then it would highlight the corresponding element in application -

Screenshot from 2016-07-27 13:47:51.png

If you want to clean console of previously written element selectors then just hit ctrl+L keys and chrome console would be empty again.


Process of testing xPath selector is same as css selector except that syntax to test xPath is -


$x(“your_xpath_selector”)


Screenshot from 2016-07-27 13:55:04.png

So no more using any plugin to test element locators :-)

Is there any other innovative way you use to test your element locator?

Popular posts from this blog

Verify email confirmation using Selenium WebDriver

Note: If you are new to java and selenium then start with selenium java training videos .   How to Verify Email Confirmation Using Selenium 4 and JavaMail (2026 Guide) Email confirmation is a critical part of most registration flows — account activation, password reset, multi-factor authentication, and onboarding. Every automation engineer eventually faces the same challenge: How do you verify an email confirmation link inside a Selenium test without making it slow and flaky? The wrong instinct is to automate Gmail's UI with Selenium. It's fragile, slow, and breaks constantly. The right approach: Use Selenium for browser automation Use JavaMail (IMAP) to read the email directly Extract the confirmation link Continue the test in Selenium Why Not Automate Gmail UI With Selenium? Automating the Gmail UI means logging in, searching, clicking a message, and parsing content from a third-party interface that changes frequently. This leads to: Flaky...

Selenium Tutorial: Ant Build for Selenium Java project

Ant is a build tool which could be used to have your tests running either from command line or from Hudson CI tool. There is detailed documentation available for ant here but probably you need to know only a little part of it for you selenium tests. The essentials which are needed to know are: Project Target (ant execution point and collection of tasks) Tasks (could be as simple as compilation) And there would usually be following targets for Selenium tools - setClassPath - so that ant knows where you jar files are loadTestNG - so that you could use testng task in ant and use it to execute testng tests from ant init - created the build file clean - delete the build file compile - compiles the selenium tests run - executes the selenium tests Here is my project set up for ant -

Recording curl request with JMeter Recorder

Just use https://jmeter.apache.org/usermanual/curl.html and no JMeter proxy etc needed : )   Though it is quite east to convert curl requests to corresponding JMeter request. At times you might be stuck with issue like I faced when uploading a file with  JMeter HTTP request In a gist I kept getting 404 error when using REStful service to upload a file. After days of investigations I found it that I should be using HTTP request implementation java and not HttpClient4. JMeter HTTPs Test Script recorder was of great help to debug this issue. This post describes the process of recording curl request through JMeter HTTPs Test Script recorder. If you have never used JMeter HTTPs Test Script recorder then create a new JMeter Plan and under WorkBench > Add > Non Test Element > HTTP(s) Test Script Recorder.  Specify Global Setting > Port as 8090 If we were using browser to record web application then we would configure its proxy to 127.0.0.1 (Since http...