~/talk

Working Well: The Future of Web Testing

Talkat dotJS 2017 · on Friday, 2017-12-01· [testing, observability]
slides:none on file

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

  1. 0:00Start
  2. 1:54Benefit of Automated Testing
  3. 2:43What Is a Quality Experience for a Web App
  4. 5:15The Chrome Dev Tools Protocol
  5. 5:33Webdriver
  6. 6:37Puppeteer
  7. 9:47Accessibility
  8. 11:36Performance
  9. 12:24Macro Benchmarks
  10. 12:55Ember Macro Benchmark
  11. 14:34Code Coverage
  12. 15:20Code Coverage Tool
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.