Browser Testing
summary
Overview of automated browser testing options and practical pitfalls: compares Selenium (proxy mode), Watir and WebDriver drivers, and headless HTMLUnit, and shows real Selenium/Watir-style scripts that open a browser, type, click and assert. Explains the proxy-host workaround for same-origin restrictions, why multi-domain redirects and Flash/popups break proxy tests, and why WebDriver’s browser-specific drivers are more reliable. Recommends using Selenium/WebDriver merge, running real OS VMs for Windows/Mac, and using a unique-user prefix to avoid test collisions.
AI-written summary · about
chapters (13)
- 0:00Browser testing intro
- 1:49Why browser-specific testing matters
- 3:36Selenium proxy challenges
- 5:22WebDriver and browser APIs
- 8:11Testing frameworks compared
- 10:20Cloud Selenium solutions
- 13:11Stable test patterns
- 17:46Disposable vs crafted tests
- 20:31Parallel testing & DB isolation
- 24:50External service interactions
- 26:14Quick vs crafted tests
- 27:59Recording tools for tests
- 29:47Testing infrastructure
related talks
30mLessons from testing browsers using WebDriver
32mAll about web application testing
15mBrowser automation/testing with BiDi and minimal dependencies
41mDesign Decisions for Perfect JavaScript Testing Framework
39mTesting web apps with Selenium
42mReliable and Maintainable Webdriver Tests
46mTest Automation with Selenium WebDriver, Java, and JUnit
26mHow browser automation works behind the scenes
