Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add unit testing callout to upgrade guide #4997

Merged
merged 3 commits into from
Feb 27, 2024
Merged

add unit testing callout to upgrade guide #4997

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
4596f87
add unit testing callout to updgrade guide
graciegoheen Feb 27, 2024
10a2e0c
add data_tests rename callout to upgrade guide
graciegoheen Feb 27, 2024
2df4703
Merge branch 'mirgration-1-8' into add_unit_testing_to_upgrade_guide
matthewshaver Feb 27, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,6 +53,14 @@ dbt test --select "test_type:data" # run all data tests

Unit tests are defined in YML files in your `models/` directory and are currently only supported on SQL models. To distinguish between the two, the `tests:` config has been renamed to `data_tests:`. Both are currently supported for backward compatibility.

### Unit testing

Historically, dbt's test coverage was confined to [“data” tests](/docs/build/data-tests), assessing the quality of input data or resulting datasets' structure.

In `1.8`, we're introducing native support for [unit testing](/docs/build/unit-tests). Unit tests validate your SQL modeling logic on a small set of static inputs __before__ you materialize your full model in production. They support a test-driven development approach, improving both the efficiency of developers and reliability of code.

To distinguish between unit test and data test configurations, the `tests:` config has been renamed to `data_tests:` - both will currently be supported for backwards compatability.

### The `--empty` flag

The [`run`](/reference/commands/run#the-`--empty`-flag) and [`build`](/reference/commands/build#the---empty-flag) commands now support the `--empty` flag for building schema-only dry runs. The `--empty` flag limits the refs and sources to zero rows. dbt will still execute the model SQL against the target data warehouse but will avoid expensive reads of input data. This validates dependencies and ensures your models will build properly.
Expand Down
Loading