Turn a business invariant into dbt tests

fact_orders feeds monthly revenue reporting. It has a not-null test on order_id, but Finance found negative net revenue caused by refund rows mixed with sale rows. Invariant -> failure mode -> test type Adding generic column tests without naming the business assumption can create a false sense of coverage. Name the grain invariant One row represents one order line, so order_id plus line_id must be unique and not null. Grain tests prevent duplicate facts, which are often more damaging than missing descriptive fields. Name the relationship invariant Every customer_id in facts must exist in dim_customer, so add a relationship test.…

Sign up free — one personalized lesson every day, matched to your role and goals.

Already have an account? Sign in