Skip to content
BENIBIX Learn

Data Quality Check

Also known as Data Test, Data Quality Test, Data Quality Rule

A rule data must pass. The pipeline tests it each time.

Think of it like

It is like the guard at the school gate. Each child must show a pass before going in.

Example

Jack adds a check that no price is below zero. A week later it stops a load with a bad currency fix, before any report sees it.

Why it matters

Checks catch bad data at the door, when it is cheap to fix. Without them, users find the problem in a meeting.

Definition

A data quality check is a rule that data must pass, run automatically in the pipeline. It might say a column has no blanks, or a key has no copies. It might say a value sits in a range, or a table is not empty. Checks usually run right after a load or a transform. A failed check can stop the next step, or just warn. Most data tools let you write checks in a few lines.

Example code

yaml
models:
  - name: orders
    columns:
      - name: order_id
        data_tests:
          - unique
          - not_null
Two dbt tests on one column. The build stops if any order ID is blank or appears twice.
A check is the gate at the top. It tests rules you wrote, every time data passes.

Common mistake

Writing hundreds of checks that only warn. People learn to ignore the noise, and the one that matters is missed.

Key takeaways

  1. 1
    A clear rule. Pass or fail, nothing in between.
  2. 2
    Runs in the pipeline. Right after data lands or changes.
  3. 3
    Stop or warn. Decide what a failure blocks.

Compare