Modern Web Testing: Going Beyond Selenium
summary
Argues that teams can drastically cut slow, flaky Selenium end-to-end suites by moving most tests to fast unit/integration layers and using a few Protractor or Cypress.io UI tests for real user flows; demos include Jest snapshot testing for React components, TestCafe/Cypress handling automatic waits and parallel runs, and Protractor’s Angular-aware sync. Recommends writing tests in Node/JavaScript when front end is JS, keeping one webdriver regression test and pushing the rest to API tests, and warns against chasing coverage quotas.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:28Test pyramid basics
- 6:05Problems with Selenium
- 8:11Backend vs frontend testing
- 13:23JavaScript for web tests
- 16:30Unit tests for web
- 18:41Integration tests with Jest
- 21:31Developer-focused testing
- 23:17User-centric end-to-end tests
- 25:46Selenium WebDriver overview
- 27:10WebDriverJS for JavaScript teams
- 30:42Testing Angular apps with Protractor
- 35:35Non-Selenium UI test frameworks
- 38:03TestCafe features
- 41:58Cypress.io capabilities
- 44:02Choosing the right tool
- 48:11Key takeaways and advice
- 49:36Q&A on code coverage and tools
related talks
38mModern Web Testing: Going Beyond Selenium
30mModern Web Testing: Going Beyond Selenium
55mModern Web Testing: Going Beyond Selenium
36mModern Web Testing: Going Beyond Selenium
41mDesign Decisions for the Perfect JS Testing Framework
30mEnd to End Testing: The Game Has Changed
41mDesign Decisions for Perfect JavaScript Testing Framework
32mAll about web application testing
