Why testing ensures data quality in dbt

Introduction

Testing helps catch mistakes in data early. It makes sure data is correct and reliable for decisions.

When you want to check if new data matches expected rules

Before using data to create reports or dashboards

When combining data from different sources to ensure consistency

After changing data pipelines to confirm nothing broke

To monitor data quality regularly and catch errors fast

Syntax

dbt

version: 2
models:
  - name: your_model_name
    tests:
      - unique:
          column_name: id
      - not_null:
          column_name: id
      - accepted_values:
          column_name: status
          values: ['active', 'inactive']

Tests are defined in YAML files inside your dbt project.

Common tests include unique, not_null, and accepted_values.

Examples

This test checks that customer_id has no duplicates.

dbt

version: 2
models:
  - name: customers
    tests:
      - unique:
          column_name: customer_id

This test ensures order_date is never empty.

dbt

version: 2
models:
  - name: orders
    tests:
      - not_null:
          column_name: order_date

This test confirms category only contains allowed values.

dbt

version: 2
models:
  - name: products
    tests:
      - accepted_values:
          column_name: category
          values: ['electronics', 'furniture', 'clothing']

Sample Program

This example shows a dbt test setup for a sales model. It checks that sale_id is unique, sale_date is not empty, and region only has allowed values.

dbt

version: 2
models:
  - name: sales
    tests:
      - unique:
          column_name: sale_id
      - not_null:
          column_name: sale_date
      - accepted_values:
          column_name: region
          values: ['north', 'south', 'east', 'west']

Important Notes

Tests help find data problems before they affect reports.

Failing tests mean you should fix data or logic in your models.

Regular testing builds trust in your data.

Summary

Testing checks data correctness automatically.

It catches errors early to avoid bad decisions.

dbt makes it easy to add and run data tests.

Practice

1. Why is testing important in dbt for data quality?

easy

A. It automatically checks if data meets expected rules.

B. It speeds up data loading into the warehouse.

C. It creates visual reports for data trends.

D. It deletes old data to save space.

Solution

1. Step 1: Understand the purpose of testing in dbt

   Testing in dbt is designed to check if data follows certain rules or expectations automatically.

2. Step 2: Compare options with testing goals

   Only It automatically checks if data meets expected rules. describes automatic checking of data correctness, which matches testing's role.

3. Final Answer:

   It automatically checks if data meets expected rules. -> Option A

4. Quick Check:

   Testing = automatic data checks [OK]

Hint: Testing means automatic checks for data correctness [OK]

Common Mistakes:

• Confusing testing with data loading speed
• Thinking testing creates visual reports
• Assuming testing deletes data

2. Which of the following is the correct syntax to add a test in a dbt model's YAML file?

easy

A. tests: - unique: column_name

B. test: unique column_name

C. tests: unique(column_name)

D. test: - unique: column_name

Solution

1. Step 1: Recall dbt YAML test syntax

   In dbt, tests are added under the 'tests' key as a list with test name and column.

2. Step 2: Match syntax with options

   tests: - unique: column_name correctly shows 'tests:' followed by '- unique: column_name' which is valid YAML for dbt tests.

3. Final Answer:

   tests: - unique: column_name -> Option A

4. Quick Check:

   YAML tests list = tests: - unique: column_name [OK]

Hint: Tests in YAML use 'tests:' with dash list [OK]

Common Mistakes:

• Using 'test' instead of 'tests'
• Missing dash '-' before test name
• Incorrect parentheses usage

3. Given this dbt test result output:

{"failures": 3, "total_tests": 5}

What does this mean about the data quality?

medium

A. No tests were run on the data.

B. All tests passed, data is perfect.

C. 5 tests failed, data is unusable.

D. 3 tests failed, indicating some data issues.

Solution

1. Step 1: Interpret test result fields

   'failures' shows how many tests failed; 'total_tests' is total run.

2. Step 2: Analyze given numbers

   3 failures out of 5 means some tests failed, so data has issues but not all tests failed.

3. Final Answer:

   3 tests failed, indicating some data issues. -> Option D

4. Quick Check:

   failures = 3 means some errors [OK]

Hint: Failures number shows how many tests found problems [OK]

Common Mistakes:

• Assuming failures means all tests failed
• Thinking zero failures means errors
• Ignoring total_tests count

4. You wrote this test in your dbt model YAML:

tests:
  - not_null: id
  - unique: id

But dbt throws an error when running tests. What is the likely problem?

medium

A. The tests list is missing a dash before 'not_null'.

B. The tests should be under 'columns', not directly under 'tests'.

C. The test names 'not_null' and 'unique' are invalid.

D. The YAML file must be named 'schema.yml' to run tests.

Solution

1. Step 1: Recall correct YAML structure for dbt tests

   Tests on columns must be nested under 'columns:' key, not directly under 'tests:'.

2. Step 2: Identify error cause

   Placing tests directly under 'tests:' causes syntax error; they belong under 'columns:' with column name and tests list.

3. Final Answer:

   The tests should be under 'columns', not directly under 'tests'. -> Option B

4. Quick Check:

   Tests belong under columns key [OK]

Hint: Tests on columns go under 'columns:' in YAML [OK]

Common Mistakes:

• Putting tests directly under 'tests:' without 'columns:'
• Using wrong test names
• Wrong YAML file naming

5. You want to ensure no duplicate emails exist in your users table using dbt tests. Which YAML snippet correctly applies this test?

hard

A. columns:
- email:
tests:
- unique

B. tests:
- unique: email

C. columns:
- name: email
tests:
- unique

D. columns:
- name: email
test: unique

Solution

1. Step 1: Recall correct YAML format for column tests

   Tests are listed under 'columns:', each with 'name' and 'tests' list.

2. Step 2: Match options with correct syntax

   columns: - name: email tests: - unique correctly uses 'columns:', '- name: email', and 'tests:' with '- unique'.

3. Final Answer:

   columns: - name: email tests: - unique -> Option C

4. Quick Check:

   Correct YAML structure = columns: - name: email tests: - unique [OK]

Hint: Use 'columns:' with 'name' and 'tests:' list [OK]

Common Mistakes:

• Using 'test' instead of 'tests'
• Missing 'name:' key for column
• Placing tests outside 'columns:'