Running tests with dbt test - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to run all tests in a dbt project.

dbt

dbt [1]

Drag options to blanks, or click blank then click option'

Atest

Bseed

Ccompile

Drun

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'dbt run' instead of 'dbt test'.

Trying to use 'dbt compile' to run tests.

Use dbt test to run all tests defined in your dbt project.

2fill in blank

medium

Complete the code to run tests only for the 'models' directory.

dbt

dbt test --select [1]

Drag options to blanks, or click blank then click option'

Asources

Bsnapshots

Cmodels

Dseeds

Attempts:

3 left

💡 Hint

Common Mistakes

Selecting 'sources' or 'snapshots' instead of 'models'.

Omitting the --select flag.

The --select models option runs tests only on models.

3fill in blank

hard

Fix the error in the command to run tests on a specific model named 'customers'.

dbt

dbt test --select [1]

Drag options to blanks, or click blank then click option'

Acustomers

Bmodels.customers

Cmodel.customers

Dmodels/customers

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'models.customers' or path formats like 'models/customers' which are invalid selectors.

Use the model name directly with --select to run tests on that model.

4fill in blank

hard

Fill both blanks to run tests on models in the 'finance' directory and limit output to errors only.

dbt

dbt test --select [1] --[2]

Drag options to blanks, or click blank then click option'

Afinance

Bquiet

Cverbose

Dmodels

Attempts:

3 left

💡 Hint

Common Mistakes

Using --verbose instead of --quiet.

Selecting 'models' instead of 'finance' for the directory.

Use --select finance to choose the finance models and --quiet to show only errors.

5fill in blank

hard

Fill all three blanks to run tests on the 'sales' model, show verbose output, and use the 'fail-fast' option.

dbt

dbt test --select [1] --[2] --[3]

Drag options to blanks, or click blank then click option'

Asales

Bdebug

Cfail-fast

Dquiet

Attempts:

3 left

💡 Hint

Common Mistakes

Using --quiet instead of --debug.

Omitting the --fail-fast option.

Use --select sales to test the sales model, --debug for detailed output, and --fail-fast to stop on first failure.

Practice

1. What is the main purpose of running dbt test in a dbt project?

easy

A. To deploy the dbt project to production

B. To build new data models from raw data

C. To check data quality and find errors in your data models

D. To generate documentation for your data models

Solution

1. Step 1: Understand the role of dbt test

   dbt test runs tests defined in your project to check data quality and catch errors.

2. Step 2: Differentiate from other dbt commands

   Building models is done with dbt run, deployment is outside dbt test, and documentation is generated with dbt docs.

3. Final Answer:

   To check data quality and find errors in your data models -> Option C

4. Quick Check:

   dbt test = data quality checks [OK]

Hint: Remember: test = check data quality, run = build models [OK]

Common Mistakes:

• Confusing dbt test with dbt run
• Thinking dbt test deploys models
• Assuming dbt test generates docs

2. Which of the following is the correct command to run tests only on a specific model named customers?

easy

A. dbt test --select customers

B. dbt run --models customers

C. dbt test --models customers

D. dbt test --only customers

Solution

1. Step 1: Identify the correct flag for running tests on specific models

   The flag --select is used with dbt test to specify which models to test.

2. Step 2: Check other options for correctness

   dbt run builds models, not tests. --models is not a valid flag for dbt test. --only is not a valid flag.

3. Final Answer:

   dbt test --select customers -> Option A

4. Quick Check:

   Use --select to target tests [OK]

Hint: Use --select flag to run tests on specific models [OK]

Common Mistakes:

• Using dbt run instead of dbt test
• Using invalid flags like --models or --only
• Confusing --select with other flags

3. Given this schema.yml test definition:

models:
  - name: orders
    tests:
      - unique:
          column_name: order_id
      - not_null:
          column_name: order_date

What will dbt test check for the orders model?

medium

A. It checks that order_id is unique and order_date has no null values

B. It checks that order_id has no null values and order_date is unique

C. It checks that both order_id and order_date are unique

D. It checks that both order_id and order_date have no null values

Solution

1. Step 1: Read the test types for each column

   The test unique applies to order_id, ensuring no duplicates. The test not_null applies to order_date, ensuring no missing values.

2. Step 2: Match tests to their meaning

   unique means no duplicates; not_null means no nulls. So the checks are: order_id is unique and order_date has no null values.

3. Final Answer:

   It checks that order_id is unique and order_date has no null values -> Option A

4. Quick Check:

   unique = no duplicates, not_null = no nulls [OK]

Hint: unique = no duplicates, not_null = no nulls [OK]

Common Mistakes:

• Mixing up unique and not_null tests
• Assuming both columns have the same test
• Ignoring the column_name key in test definitions

4. You run dbt test but get an error: Compilation Error: Could not find test 'uniquee'. What is the likely cause?

medium

A. The test passed with no errors

B. The model name is incorrect

C. The database connection is missing

D. A typo in the test name in schema.yml

Solution

1. Step 1: Analyze the error message

   The error says it cannot find test 'uniquee', which looks like a misspelled test name.

2. Step 2: Identify common causes of compilation errors

   Typos in test names in schema.yml cause dbt to fail to find the test. Model name or connection errors produce different messages.

3. Final Answer:

   A typo in the test name in schema.yml -> Option D

4. Quick Check:

   Compilation errors often mean typos [OK]

Hint: Check spelling of test names in schema.yml [OK]

Common Mistakes:

• Ignoring typo errors and rerunning blindly
• Assuming connection issues cause compilation errors
• Confusing model name errors with test name errors

5. You want to ensure that the email column in your users model is unique and not null. You also want to run tests only on this model. Which schema.yml snippet and command combination is correct?

hard

A. models:
- name: users
tests:
- unique
- not_nullCommand: dbt test --models users

B. models:
- name: users
columns:
- name: email
tests:
- unique
- not_nullCommand: dbt test --select users

C. models:
- name: users
columns:
- name: email
tests:
- unique
- not_nullCommand: dbt run --models users

D. models:
- name: users
tests:
- unique
- not_nullCommand: dbt test --select users

Solution

1. Step 1: Identify correct test syntax in schema.yml

   Tests on columns are defined under columns with name and tests list.

   models:
     - name: users
       columns:
         - name: email
           tests:
             - unique
             - not_null

   
   Command: dbt test --select users shows the correct format.

2. Step 2: Choose the correct command to run tests on the users model

   dbt test --select users runs tests only on the users model.

   models:
     - name: users
       columns:
         - name: email
           tests:
             - unique
             - not_null

   
   Command: dbt test --select users uses this command correctly.

3. Final Answer:

   Option B with column-level tests and dbt test --select users -> Option B

4. Quick Check:

   Column tests + --select flag = correct [OK]

Hint: Define tests under columns, run with --select flag [OK]

Common Mistakes:

• Defining tests directly under model without column_name (invalid syntax)
• Using dbt run instead of dbt test
• Using incorrect flags like --models