Help a developer decide which data-quality tests to apply to a scope of dbt models, then implement them correctly. Use when someone asks "what tests should this model have?", "how do I test uniqueness / grain / freshness / a foreign key / an enum / a numeric range / SCD2 / an anomaly?", or wants to close test coverage on staging/marts before a PR. Walks the testing-taxonomy decision tree in references/, opens the matching vignette (the worked pattern + why it matters + which dbt package to reach for), and grounds the final implementation in current practice with a web search because vignette code samples and package recommendations date. This is the decide-and-justify guide for specific models — not a whole-project coverage scorer and not a unit-test YAML generator.
2026-06-24