Automated Testing for Web-based Systems on Embedded Devices
summary
Embedded web apps require testing on live hardware (Raspberry Pi, i.MX6/8) because they access system APIs and run inside customized engines; browser automation proves the viable approach. WebDriver BiDi uses WebSockets to enable two‑way events so tests subscribe to console logs and JS exceptions instead of polling, and can observe DOM changes and perform network interception to return mocked responses. Options include Selenium, WebDriverIO, and Playwright (with Playwright A8 checks that reduce flaky clicks), while WebKit BiDi support is actively landing to run remote tests on embedded boards.
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
24mWebDriver BiDi: work in progress.
31mRevolutionising Browser Automation: A Deep Dive into the WebDriver BiDi Project and its Integration with Selenium- 31mRevolutionising Browser Automation: A Deep Dive into the WebDriver BiDi Project and...
15mBrowser automation/testing with BiDi and minimal dependencies
42mAdvancing WebDriver BiDi support in WebKit
01h 26mWorkshop: Reactive Browser Testing with WebDriver BiDi
11mThe Future of Cross-Browser Automation: WebDriver BiDi