Skip to content

Commit 040b0cc

Browse files
authored
Update introduction.mdx
1 parent 2c11c19 commit 040b0cc

1 file changed

Lines changed: 7 additions & 0 deletions

File tree

docs/data-tests/introduction.mdx

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -110,3 +110,10 @@ Tests to detect anomalies in data quality metrics such as volume, freshness, nul
110110
<Card title="Python tests" href="/data-tests/python-tests">
111111
Write your own custom tests using Python scripts.
112112
</Card>
113+
114+
## Understanding Errors, Failures, and Warnings in dbt Tests
115+
116+
In dbt, there are three possible outcomes when running models or tests: errors, failures, and warnings.
117+
- An **error** means dbt could not run the SQL at all (e.g., syntax mistake, missing table, broken macro). This stops execution (on `dbt build`).
118+
- A **failure** happens when a test runs successfully but its condition isn’t met, and if the test’s severity is set to error, it will fail the pipeline.
119+
- A **warning** is the same as a failure in terms of data quality, but with severity: warn, dbt exits successfully and does not break pipelines.

0 commit comments

Comments
 (0)