You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/integrations/dbt.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -287,9 +287,12 @@ If set to `False`, then the snapshot will be skipped and a warning will be logge
287
287
Support for this will be added soon.
288
288
289
289
## Tests
290
-
SQLMesh uses dbt tests to perform SQLMesh [audits](../concepts/audits.md) (coming soon).
291
290
292
-
Add SQLMesh [unit tests](../concepts/tests.md) to a dbt project by placing them in the "tests" directory.
291
+
dbt and SQLMesh use the word "test" differently. See [Workflow differences](#workflow-differences-between-sqlmesh-and-dbt) above for an overview.
292
+
293
+
SQLMesh converts dbt tests (singular and generic `.sql` files in the `tests/` directory) into SQLMesh [audits](../concepts/audits.md). These run against data that already exists in your tables, just like dbt tests.
294
+
295
+
Add SQLMesh [unit tests](../concepts/tests.md) to a dbt project by placing YAML files named `test*.yaml` or `test*.yml` in the `tests/` directory. Unit tests validate model query logic with predefined inputs and expected outputs; they are separate from dbt's SQL test files.
0 commit comments