Building a Driver: Lessons Learned from Developing the Internet Explorer Driver
summary
Rewrites the IE driver as a C++ standalone executable server that speaks the JSON Wire Protocol, so language bindings can x‑copy deploy without native runtime installs. Reuse of JavaScript automation atoms centralizes browser logic (at the cost of IE JavaScript slowness), while OS-level native events replicate real user input but introduce focus and timing flakiness. Binding code shrinks dramatically (from 683 lines to 32 lines of code); logging remains weak.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:56Solo History
- 4:39Language Independent
- 7:09Distribute a standalone executable
- 13:57Code size comparison
- 16:27Automation
- 19:23Pop Quiz
- 21:22Native Events
- 23:33Automating IE
- 26:14Log everything
- 28:56Questions
related talks
38mThe Internet Explorer Driver Revisited The Quickening
22mClosing Keynote
31mRevolutionising Browser Automation: A Deep Dive into the WebDriver BiDi Project and...
26mHow browser automation works behind the scenes
48mThe Nuts and Bolts of WebdriverIO- 31mRevolutionising Browser Automation: A Deep Dive into the WebDriver BiDi Project and its Integration with Selenium
15mBrowser automation/testing with BiDi and minimal dependencies
33mBeyond WebDriver!