Escaping the Tar Pit
summary
Combines code coverage and static metrics into a single “stink score” that prioritizes files to refactor, implemented as the skunk gem that reads Ruby Critic and simplecov output and ranks files by churn × cost and penalizes missing tests (example: identical complexity files diverge when one has 0% coverage and its score jumps ~100×). Uses flog, reek and git churn, produces HTML and console reports, and validates on Solidus core where only one file sits in the high‑churn/high‑complexity quadrant.
AI-written summary · about
chapters (11)
- 0:00Start
- 5:54Tar Pit Symptoms
- 11:36ISO 9126-1 Software Quality Model
- 12:36Code Coverage
- 14:12Code Quality
- 20:33solidus/core
- 24:10Signal #2
- 24:25Coverage & Complexity
- 29:10Ruby Critic
- 29:47Skunk
- 36:04stink_score
