Everything I know about writing quality software
summary
Practical checklist for making apps stop breaking: test code the way users run it, not only unit internals; use Cypress end-to-end for DOM-driven tests (records video, retries commands, runs in Electron/Chrome, not WebDriver). Combine runtime runs with NYC/Istanbul coverage when spawning Node so coverage stays accurate. Ship a crash pipeline like Sentry crash reporting and treat crashes as test cases. Add JSON Schema validation, data-coverage to collect inputs, treemap to prioritize large complex untested files, and aim roughly 50% happy-path, 20% edge-case, 30% crash-driven tests.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:46Why Does Everything Suck Why Everything Is Broken
- 4:08What Is Quality
- 13:12Code Coverage Tools
- 17:21Tree Map
- 18:12To Test a Web Application
- 27:16Defensive Coding
- 30:08Jason Schemas
- 34:35Why Did Microsoft Buy Github
related talks
39mTesting, Testing, 1, 2, NaN
30mWait, before you write your next test...
31mWriting (Really) Good Tests
20mPanel Discussion on Testing
01h 02mWriting better tests for your JavaScript app
01h 02mThe Pursuit of Quality
21mTesting Javascript: Building JavaScript applications you won't hate
58mDocumenting application behaviours with E2E tests