Coverage Report — daily_revenue

Generated from the Scope × Basis matrix on 2026-06-29 (platform: dbt).

Generated artifacts

• schema.yml — row-level absolute test (amount >= 0) + traceability notes
• tests/daily_revenue_amount_sum_within_2_stddev.sql — aggregate relative, severity error
• tests/daily_revenue_row_count_within_20pct_of_prior_day.sql — aggregate temporal, severity warn

Scope coverage

Row-level: ✓ (1 automated test + 1 human check, not automated) Aggregate-level: ✓ (2 tests) Transformation-level: ✗ (0 tests — GAP, all matrix cells empty)

Basis coverage

Absolute: ✓ (1 test — row-level, severity error) Relative: ✓ (1 test — aggregate, severity error) Temporal: ✓ (1 test — aggregate, severity warn) Human: — (1 check noted, not automatable — spot-check 5 rows vs billing UI)

Totals

Automated tests: 3 Manual checks noted: 1 (row-level human) Severity breakdown: error ×2, warn ×1

Gaps flagged

1. Transformation-level scope has ZERO tests (0). Every transformation-level cell (absolute / relative / temporal / human) in the matrix is empty. The framework's definition-of-done requires at least one check per scope level, so this scope fails coverage. Recommend adding a source-fidelity check, e.g. sum(amount) in daily_revenue reconciles to the upstream billing source for the same window (transformation-level × relative).

Dependencies / assumptions

• dbt_expectations package available (used for expect_column_values_to_be_between).
• Model exposes a revenue_date date column (required by both aggregate tests).
• Both aggregate tests are self-contained (LAG / self-join over revenue_date); no separate _snapshot table needed.