Automated Testing for Web-based Systems on Embedded Devices
summary
Embedded web apps on boards like Raspberry Pi or i.MX6/i.MX8 use real WebKit builds and need tests that exercise system APIs and gestures, not just DOM clicks. The proposal uses WebDriver over HTTP for remote control and the newer WebDriver BiDi via WebSockets to enable console.log subscriptions, DOM change events, and the ability to intercept network requests and inject mock responses. Tools discussed: Selenium, WebDriverIO, Playwright (requires patched WebKit/Firefox), and ongoing WebKit BiDi support to run tests directly against embedded browsers.
AI-written summary · about
chapters (7)
- 0:00Introduction and context
- 2:51Embedded app challenges
- 6:28Testing in embedded systems
- 10:55Browser automation evolution
- 17:27The WebDriver BiDi protocol
- 21:32Tooling and frameworks
- 26:01Recap and Q&A
related talks
33mAutomated Testing for Web-based Systems on Embedded Devices
42mAdvancing WebDriver BiDi support in WebKit
04mWe're bad at web integration testing
01h 13mThe multi-year quest for the best web test in the west
19mWorking Well: The Future of Web Testing
32mAll about web application testing
15mBrowser automation/testing with BiDi and minimal dependencies
36mModern Web Testing: Going Beyond Selenium
