Next level of Front end testing with Devtools and WebDriver
summary
Shows how existing Selenium WebDriver suites gain Chrome DevTools power by opening Chromedriver with remote debugging, fetching the WebSocket debugger URL and calling DevTools JSON APIs to do things that were manual or mocked: clearDataForOrigin to wipe site storage, network interception to replace images and mock responses, and Network.emulateNetworkConditions to simulate 3G/4G/offline and geolocation changes. Demonstrates doing this with a manual WebSocket client in WebDriver 3 and via executeCdpCommand / built-in CDP wrappers in Selenium 4, rescuing tests from 1000+ maintenance-heavy mock JSONs.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:27About Fathima
- 3:52Push Notification
- 4:34Testing with Devtools
- 10:11Finding the right API
- 16:23WebDriver version
- 16:55Demo
- 20:04Network
- 24:16Mock geolocation
related talks
44mNext Gen Front end testing with DevTools and WebDriver
30mExploring the Chrome Debugger Protocol for Test Authoring
47mBecome Black Ops QA with Selenium 4 BiDi-DevTools APIs
25mAutomated Performance Testing With WebDriver
19mDevTools and Headless Chrome - The Automation Power-Couple
31mThe Chrome DevTools Protocol!
28mFrontend Testing
30mPowerful Automation with the Chrome DevTools Protocol