Next Gen Front end testing with DevTools and WebDriver
summary
Shows Chrome DevTools + Selenium WebDriver actually doing things: opening Chrome with remote debugging, using CDP over WebSocket to clear browser storage, mock network responses (images replaced in the demo), simulate slow mobile network via throttling, and set geolocation override so the page reports a different latitude/longitude. Selenium 3 requires a manual WebSocket client; Selenium 4 exposes CDP hooks and executeCdpCommand. Demos run live and produce the claimed results.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 1:10Network simulation
- 1:58Mocking
- 2:58Geolocation
- 3:34Service Workers
- 4:45DevTools
- 5:05How to use DevTools
- 6:02How to use Chrome
- 7:13What is WebSocket
- 8:05WebSocket object structure
- 9:26Demo
- 16:27Recap
- 17:23WebDriver Architecture
- 18:55Multi Client Remote Debugging Protocol
- 20:04Demo Overview
- 20:57Making WebSocket Connection
- 22:38Mocking Requests
- 24:39Selenium 4 Features
- 27:57Execute CDP Command
- 29:35Geo location test
- 30:49Geolocation override
- 31:57Summary
- 32:45Other opensource tools
- 34:12Questions
- 36:42Integration
related talks
29mNext level of Front end testing with Devtools and WebDriver
47mBecome Black Ops QA with Selenium 4 BiDi-DevTools APIs
28mFrontend Testing
20mSelenium 4 – What's New and How you Can Use it!
44mBecome Black Ops QA with Selenium 4 BiDi-DevTools APIs
46mSelenium 4
31mThe Chrome DevTools Protocol!
23mLife After Selenium