Testing the web without testers — success or failure
summary
A company that builds JavaScript/HTML5 UI components automated end-to-end testing: unit tests using QUnit and Sinon (about 10,000 tests, 1.5 months, 4 developers), functional tests with TestCafe (~1,000 cases running 20–30 minutes on a farm) which reduced release bugs from ~215 to under 50, a mobile pipeline moved from physical devices to emulators with a custom runner, pixel-compare screenshot tooling (built by 2 developers in 1 month plus 6 months stabilization) to halve visual regressions, and performance benchmarks that outperformed some competitors.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:20Unit testing from scratch
- 9:23Functional testing
- 18:00Mobile testing
- 23:18Visual testing
- 27:57Performance testing
- 32:18Summary
- 33:43Q&A
related talks
34mEnd to end testing a world of web, mobile & desktop apps
29mState of Web Integration Testing
53mTransforming testing methodologies: From manual to robust strategies
53mModern Web Testing: Going Beyond Selenium
22mTwo years of UI Testing
56mThe End Game
31m#testedAF: Test All the Things (Not Just Your Units)
38mScaling Automated Testing & Architecture from Startup to Enterprise