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.

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

exit codes for unit tests #5301

Closed
1 task done
graciegoheen opened this issue Apr 17, 2024 · 0 comments · Fixed by #5376
Closed
1 task done

exit codes for unit tests #5301

graciegoheen opened this issue Apr 17, 2024 · 0 comments · Fixed by #5376
Assignees
Labels
content Improvements or additions to content dbt-core v1.8 improvement Use this when an area of the docs needs improvement as it's currently unclear unit testing docs for 1.8 unit testing

Comments

@graciegoheen
Copy link
Collaborator

Contributions

  • I have read the contribution docs, and understand what's expected of me.

Link to the page on docs.getdbt.com requiring updates

Slack thread for context

Not sure which page should be updated!

  • exit codes
  • testing documentation
  • somewhere else?

What part(s) of the page would you like to see updated?

Add explanation for why exit codes vary for data tests & unit tests

something something "Data tests are queries that return one row per failed test case, i.e. the number of values with duplicates for the unique test. dbt will report the number of failing records as failures. Whereas each unit test represents one 'test case' — so failures is always 0 (pass) or 1 (fail) for that test case."

Additional information

No response

@graciegoheen graciegoheen added content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear labels Apr 17, 2024
@graciegoheen graciegoheen added dbt-core v1.8 unit testing docs for 1.8 unit testing labels Apr 17, 2024
@matthewshaver matthewshaver self-assigned this Apr 19, 2024
matthewshaver added a commit that referenced this issue May 9, 2024
## What are you changing in this pull request and why?

Closes #5301

## Checklist
<!--
Uncomment when publishing docs for a prerelease version of dbt:
- [ ] Add versioning components, as described in [Versioning
Docs](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-entire-pages)
- [ ] Add a note to the prerelease version [Migration
Guide](https://github.com/dbt-labs/docs.getdbt.com/tree/current/website/docs/docs/dbt-versions/core-upgrade)
-->
- [ ] Review the [Content style
guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md)
so my content adheres to these guidelines.
- [ ] For [docs
versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#about-versioning),
review how to [version a whole
page](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version)
and [version a block of
content](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-blocks-of-content).
- [ ] Add a checklist item for anything that needs to happen before this
PR is merged, such as "needs technical review" or "change base branch."
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Improvements or additions to content dbt-core v1.8 improvement Use this when an area of the docs needs improvement as it's currently unclear unit testing docs for 1.8 unit testing
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants