Working Well, The Future of JavaScript Testing
summary
Argues that tests must prove software works well by measuring performance, visual correctness and code necessity with concrete instrumentation rather than vague examples. Cites headless Chrome (Chrome 59, shipped April 13) and the Chrome DevTools Protocol to collect traces, memory and coverage, shows screenshots in about six lines with Puppeteer, basic visual checks in ~50 lines, integrates with Percy and ember macro benchmark, and demonstrates tracking regressions and unused bytes so teams can quantify surprising changes over time.
AI-written summary · about
chapters (5)
- 0:00Start
- 1:21Working Well: The Future of Web Testing
- 1:56Testing Gives Us Confidence That Software Works
- 2:28Testing Should Give Us Confidence That Software Works Well
- 10:25ember-macro- benchmark
related talks
19mWorking Well: The Future of Web Testing
38mModern Web Testing: Going Beyond Selenium
30mModern Web Testing: Going Beyond Selenium
41mDesign Decisions for the Perfect JS Testing Framework
36mModern Web Testing: Going Beyond Selenium
37mAutomated Performance Testing With WebDriver
35mDesign Decisions for the Perfect JS Testing Framework
44mAiming for the Stars
