Skip to content

Commit

Permalink
Add caveat about including all necessary given input fixtures for uni…
Browse files Browse the repository at this point in the history
…t tests (#6603)
  • Loading branch information
mirnawong1 authored Dec 6, 2024
2 parents ff74e59 + 80041dc commit 4638902
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions website/docs/docs/build/unit-tests.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,7 @@ Starting in dbt Core v1.8, we have introduced an additional type of test to dbt
- If your model has multiple versions, by default the unit test will run on *all* versions of your model. Read [unit testing versioned models](/reference/resource-properties/unit-testing-versions) for more information.
- Unit tests must be defined in a YML file in your `models/` directory.
- Table names must be [aliased](/docs/build/custom-aliases) in order to unit test `join` logic.
- Include all [`ref`](/reference/dbt-jinja-functions/ref) or [`source`](/reference/dbt-jinja-functions/source) model references in the unit test configuration as `input`s to avoid "node not found" errors during compilation.
- Redshift customers need to be aware of a [limitation when building unit tests](/reference/resource-configs/redshift-configs#unit-test-limitations) that requires a workaround.

Read the [reference doc](/reference/resource-properties/unit-tests) for more details about formatting your unit tests.
Expand Down

0 comments on commit 4638902

Please sign in to comment.