How to test web applications
summary
A practical history that actually says what changed and why: a crowdsourced archive and timeline shows 178 responses and a concrete lineage of tools JS Test Driver → Karma → Jest and why bundlers and runtimes force new runners. Expect specific examples of what was built like a browser‑launching test runner, why phantomjs and headless Chrome mattered, and one surprising number — manual testing at Google for Android — that argues manual checks still solve deployment and infra problems.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:20Early web testing mystery
- 3:22CGI testing in 1990s
- 5:23Manual testing challenges
- 8:03Rise of JS test runners
- 10:51First browser war impact
- 12:30Second browser war & unit testing
- 15:52In-browser unit testing breakthroughs
- 17:40Node test runners & modern tooling
- 19:18Today's testing landscape
- 21:07Conclusion
related talks
22mTwenty Years of Web Testing: From Selenium's Dawn to Vitest's Promise
19mWorking Well: The Future of Web Testing
21mWorking Well, The Future of JavaScript Testing
47mPractical Testing with JavaScript
39mTesting, Testing, 1, 2, NaN
36mModern Web Testing: Going Beyond Selenium
30mModern Web Testing: Going Beyond Selenium
55mModern Web Testing: Going Beyond Selenium
