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

Jump to bottom

Add details of where to store fixtures for unit tests #5570

Merged
merged 3 commits into from
May 31, 2024
Merged

Add details of where to store fixtures for unit tests #5570

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2bf462d
Add details of where to store fixtures
joellabes May 28, 2024
7e3e62b
Merge branch 'current' into joellabes-unit-test-fixtures
mirnawong1 May 31, 2024
e33cb28
Update website/docs/docs/build/unit-tests.md
mirnawong1 May 31, 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
2 changes: 1 addition & 1 deletion website/docs/docs/build/unit-tests.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,7 +125,7 @@ unit_tests:
```
</file>

The previous example defines the mock data using the inline `dict` format, but you can also use `csv` or `sql` either inline or in a separate fixture file.
The previous example defines the mock data using the inline `dict` format, but you can also use `csv` or `sql` either inline or in a separate fixture file. Store your fixture files in a `fixtures` subdirectory in any of your [test paths](/reference/project-configs/test-paths). For example, `tests/fixtures/my_unit_test_fixture.sql`.

When using the `dict` or `csv` format, you only have to define the mock data for the columns relevant to you. This enables you to write succinct and _specific_ unit tests.

Expand Down
Loading