What causes TestConfigError?

A generic test (e.g., `accepted_values`) is missing a required argument such as `values:` in the test config. A custom test macro is referenced in schema.yml but the macro does not exist in the project or installed packages. The `severity` key on a test config uses an unsupported value (must be `warn` or `error`). A column-level test references a column that was removed from or renamed in the model. A singular test (SQL file in tests/) references a model or source using ref() or source() that does not exist in the project

How do I fix TestConfigError?

Run `dbt compile` locally to get the full error message with file name and line number.. Verify that every test macro referenced in schema.yml is available — run `dbt ls --resource-type test` to confirm tests resolve correctly.. Check that all required arguments for generic tests are present (e.g., `values:` for `accepted_values`, `to:` and `field:` for `relationships`).. Confirm columns referenced in column-level tests still exist in the model's SELECT after any recent refactors.. For custom test macros from packages, verify the package is listed in packages.yml and `dbt deps` has been run.

Medium severityconfiguration

Power BI Refresh Error:
TestConfigError

What does this error mean?

dbt could not parse or compile a test definition due to an invalid test configuration. This prevents the test from running and, depending on job settings, can block the entire job. TestConfigError appears when a test's config block contains unrecognised properties, wrong value types, or references to columns or sources that do not exist.

Common causes

1A generic test (e.g., `accepted_values`) is missing a required argument such as `values:` in the test config
2A custom test macro is referenced in schema.yml but the macro does not exist in the project or installed packages
3The `severity` key on a test config uses an unsupported value (must be `warn` or `error`)
4A column-level test references a column that was removed from or renamed in the model
5A singular test (SQL file in tests/) references a model or source using ref() or source() that does not exist in the project

How to fix it

1Run `dbt compile` locally to get the full error message with file name and line number.
2Verify that every test macro referenced in schema.yml is available — run `dbt ls --resource-type test` to confirm tests resolve correctly.
3Check that all required arguments for generic tests are present (e.g., `values:` for `accepted_values`, `to:` and `field:` for `relationships`).
4Confirm columns referenced in column-level tests still exist in the model's SELECT after any recent refactors.
5For custom test macros from packages, verify the package is listed in packages.yml and `dbt deps` has been run.

Frequently asked questions

Does a TestConfigError mean my data quality check failed?

No — it means dbt could not compile the test definition. The test never executed, so no data quality verdict was produced. Fix the config error and re-run.

How do I make a failing test warn instead of error?

Add `config: severity: warn` to the test definition in schema.yml. The test still runs and reports the result, but the job exits with code 0 instead of 1.