Modern Web Testing: Going Beyond Selenium
summary
Argues for moving end-to-end tests from server-side Selenium bindings to client-side JavaScript tooling, shows a to‑do app and real code: webdriverjs for generic browser control, Protractor’s Angular-aware selectors and state sync working reliably on the demo, and newer tools like Cypress and TestCafe offering live reload, record/replay and faster feedback; demonstrates Jest/Jasmine unit and snapshot testing for UI regression; warns of migration cost and advises pick one or two frameworks and measure ROI.
AI-written summary · about
chapters (16)
- 0:00Start
- 2:44lenium WebDriver
- 4:04Case #1
- 4:21there a problem?
- 5:09Hybrid Model
- 6:02main Driven Design
- 9:54Unit Testing
- 13:31Developers
- 14:23Sounds great!
- 20:20Case #2
- 24:29What's Next?
- 25:55Non-Selenium Test Frameworks
- 28:59void Tool Mixups
- 30:39Flexibility
- 31:53Use Case
- 33:17Call For Action
related talks
30mModern Web Testing: Going Beyond Selenium
38mModern Web Testing: Going Beyond Selenium
55mModern Web Testing: Going Beyond Selenium
53mModern Web Testing: Going Beyond Selenium
41mDesign Decisions for the Perfect JS Testing Framework
35mDesign Decisions for the Perfect JS Testing Framework
30mEnd to End Testing: The Game Has Changed
32mAll about web application testing