Bird
Raised Fist0
dbtdata~5 mins

Running tests with dbt test - Time & Space Complexity

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Time Complexity: Running tests with dbt test
O(n)
Understanding Time Complexity

When running tests with dbt test, we want to know how the time it takes grows as the number of tests or data size increases.

We ask: How does running more tests or bigger data affect the total time?

Scenario Under Consideration

Analyze the time complexity of the following dbt test command snippet.


-- Run all tests defined in the project
dbt test

-- Example of a simple test definition
select * from {{ ref('my_model') }} where id is null

This runs all tests defined in the dbt project, checking data quality rules like null values.

Identify Repeating Operations

Look for repeated actions that take time.

  • Primary operation: Running each test query against the database.
  • How many times: Once per test defined in the project.
How Execution Grows With Input

As the number of tests grows, the total time grows roughly in direct proportion.

Input Size (number of tests)Approx. Operations (test queries run)
1010
100100
10001000

Pattern observation: Doubling the number of tests roughly doubles the total time.

Final Time Complexity

Time Complexity: O(n)

This means the total time grows linearly with the number of tests run.

Common Mistake

[X] Wrong: "Running more tests will take the same time because they run in parallel."

[OK] Correct: While some parallelism may happen, each test still requires database work, so total time grows with test count.

Interview Connect

Understanding how test execution time grows helps you plan and optimize data quality checks in real projects.

Self-Check

"What if we only run tests on changed models instead of all models? How would the time complexity change?"

Practice

(1/5)
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_null

Command: dbt test --models users
B. 
models:
  - name: users
    columns:
      - name: email
        tests:
          - unique
          - not_null

Command: dbt test --select users
C. 
models:
  - name: users
    columns:
      - name: email
        tests:
          - unique
          - not_null

Command: dbt run --models users
D. 
models:
  - name: users
    tests:
      - unique
      - not_null

Command: 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