Enough Coverage To Beat The Band
summary
Walks through using Ruby's coverage module to answer concrete questions: run lines to get per-line counts (found 16 broken strings over 10 shows), run one-shot lines to see presence/absence (three of four synth patches used), run methods to spot unused fixtures (projector trigger never called), and run branches to find an off-by-one bug hiding on a ternary that skipped a chorus branch. Demonstrates coverage.start modes, parses the returned hashes, and shows fixes that make the show work.
AI-written summary · about
chapters (6)
related talks
23mDigging Up Code Graves in Ruby
43mAn introduction and future of Ruby coverage library
26mImproving Coverage Analysis
24mWhat it Means to Have Good Test Covearage...
03mTest coverage
43mTest coverage in Go, the whole package
10m99% is not enough - full test coverage and why it's awesome
58mCoverage, quality, and Goodhart's Law