How does Selenium find Elements?
summary
Slides and experiments show exactly what Selenium does: it asks the browser for elements via the WebDriver protocol, often translating ID/name/class into CSS and calling querySelectorAll, while XPath goes through a different path. The author probes driver logs, uses Postman to hit Chrome/Gecko endpoints, and builds microbenchmarks measuring operations per second. Results show DOM-based selectors (often tag name fastest) beat injected XPath most of the time but browsers vary, so performance surprises appear (Edge differs).
AI-written summary · about
chapters (8)
- 0:00Start
- 7:09Postman Window
- 14:58History
- 18:42Selenium Webdriver Architecture
- 19:44Find Element Command
- 20:22Different Selectors Strategies
- 24:29How Different Browser Works
- 26:20How the Parser Works
related talks
23mLife After Selenium
20mSelenium 4 – What's New and How you Can Use it!
49mSelenium: state of the union
37mHacking Selenium
46mTest Automation with Selenium WebDriver, Java, and JUnit
26mWhat’s new and good in Selenium
26mHow browser automation works behind the scenes
46mSelenium State of the Union, To Infinity and Beyond