Working Well: The Future of Web Testing
summary
Automated tests move from “it works” to measuring real quality: headless Chrome plus the Chrome DevTools Protocol let tests record performance traces, runtime code coverage and DOM accessibility checks. High-level tooling like Puppeteer and axe-core integrates with browser instrumentation, and application-level suites such as ember macro benchmark produce reproducible macro‑benchmarks. Examples include automated accessibility sweeps of every linkable page, repeatable render time boxplots, and coverage maps that flag unused JS shipped to users.
AI-written summary · about
chapters (12)
- 0:00Start
- 1:54Benefit of Automated Testing
- 2:43What Is a Quality Experience for a Web App
- 5:15The Chrome Dev Tools Protocol
- 5:33Webdriver
- 6:37Puppeteer
- 9:47Accessibility
- 11:36Performance
- 12:24Macro Benchmarks
- 12:55Ember Macro Benchmark
- 14:34Code Coverage
- 15:20Code Coverage Tool
related talks
21mWorking Well, The Future of JavaScript Testing
38mModern Web Testing: Going Beyond Selenium
30mModern Web Testing: Going Beyond Selenium
37mAutomated Performance Testing With WebDriver
35mState of end-to-end testing for modern web applications
55mModern Web Testing: Going Beyond Selenium
53mModern Web Testing: Going Beyond Selenium
36mModern Web Testing: Going Beyond Selenium
