WebDriver: Controlling your Web Browser
summary
An open source Erlang WebDriver implementation lets Erlang code control Chrome Opera and Firefox via the WebDriver REST/JSON API (about 80 commands) and runs QuickCheck-driven random scenarios that shrink failing sequences to minimal counterexamples. It lives on GitHub under MIT, records Selenium scripts and translates them to EUnit, and runs headless HTMLUnit for fast runs. The implementation works but uncovers real interoperability faults including bugs in Erlang's httpc module Chrome Driver and the Selenium server.
AI-written summary · about
chapters (19)
- 0:00Intro
- 1:12Creating a poll
- 4:09Who am I
- 4:50The problem
- 5:40Getting involved
- 6:17Prowess
- 7:19Selenium
- 7:51Automation
- 9:44WebDriver API
- 10:50WebDriver REST API
- 12:54Implementation
- 15:03Raw protocol
- 19:05Wrapper protocol
- 21:35QuickCheck
- 23:40QuickCheck Line
- 24:49Testing
- 28:06First problem
- 29:31Second problem
- 37:39Questions
related talks
15mBrowser automation/testing with BiDi and minimal dependencies
26mHow browser automation works behind the scenes
29mNext level of Front end testing with Devtools and WebDriver
30mLessons from testing browsers using WebDriver
30mModern Web Testing and Automation with Puppeteer
19mWorking Well: The Future of Web Testing
49mSelenium: state of the union
01h 13mThe multi-year quest for the best web test in the west