> For the complete documentation index, see [llms.txt](https://docs.selectstar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.selectstar.com/integrations/dbt/dbt-tests-beta.md).
# dbt Tests
Find out the latest news that dbt tests are now going to be ingested into Select Star, and how this will benefit your data projects.
dbt Tests are now going to be ingested into Select Star!
{% hint style="info" %}
To add dbt tests into your existing SelectStar organization, you will need to either update permissions (dbt Cloud) or add a `run_results.json` (dbt Core)
{% endhint %}
To see how to update your config:
{% content-ref url="/pages/MQoeDOVEP4yrkHgXgTM1" %}
[dbt Cloud](/integrations/dbt/dbt-cloud.md)
{% endcontent-ref %}
{% content-ref url="/pages/6HDe0KrWKWcvNOENCtHe" %}
[dbt Core (open source)](/integrations/dbt/dbt-core-open-source.md)
{% endcontent-ref %}
Once updates, to find dbt tests, go to the dbt tests page from the hierarchy
dbt tests in hierarchy
All tests that have run in the dbt data source should be available in the dbt tests page.
Full dbt Tests Page
To filter for failed tests, click on one of the tabs on top:
Failed dbt tests
To view dbt tests that have run for a particular model or table, we can go to the newly added tests tab in each table/model page:
Test that have run for view model.
Click on any of the tests to drill down even further to see information such as all test runs and errors from the latest test run and the last run date.
Failed test ingested from dbt
You can each see the source of each test and copy this information really quickly:
Source of test not_null
dbt tests are also searchable like any other asset type in Select Star
Search by the name of the dbt test
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.selectstar.com/integrations/dbt/dbt-tests-beta.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
