~/talk

How to test web applications

Talkat dotJS 2024 · on Thursday, 2024-06-27· [testing]
slides:none on file

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

  1. 0:00Introduction
  2. 1:20Early web testing mystery
  3. 3:22CGI testing in 1990s
  4. 5:23Manual testing challenges
  5. 8:03Rise of JS test runners
  6. 10:51First browser war impact
  7. 12:30Second browser war & unit testing
  8. 15:52In-browser unit testing breakthroughs
  9. 17:40Node test runners & modern tooling
  10. 19:18Today's testing landscape
  11. 21:07Conclusion
~/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.