dbt tests

Now leverage your tests, show their results on related dbt assets.

dbt tests integration must come on top of an already existing dbt integration in Catalog

dbt tests integration requires two types of files:

  • a manifest

  • run results

Fetching a manifest

dbt tests integration is Client managed so you should already fetch the manifest in your dbt Core integration. Only one manifest is needed.

Fetching run results

run_results.json are files generated at each run command and which contain the results of your tests.

They are located in the same /target directory as your manifest by default.

You can fetch several run results files and upload them (if your tests are run on different schedules, in different DAGs)

Catalog managed

Input your credentials directly in the App. We simply need:

  • a service token

This should be the same as the one provided for your dbt (Catalog managed) integration. We will store your credentials separately, for a security purpose.

The dbt Base URL of your account

By default, https://cloud.getdbt.com will be used but depending on your region, URL might change. See more in dbt documentation.

For your first sync, it will take up to 48h and we will let you know when it is complete ✅

If you are not comfortable giving us access to your credentials, please continue to Client managed 👇

Client managed

1. One Shot load

During your Catalog trial we offer a one-shot sync of your tests. Simply send both files to your Catalog sales representative via email or Slack.

2. Scheduled sync

The Catalog team will provide you with

  1. Catalog Identifier (an id for us to match your looker files with your Catalog instance)

  2. Catalog Token An API Token

You can then use the castor-upload command:

castor-upload [arguments]

Arguments

  • -k, --token: Token provided by Catalog

For security purposes, Catalog only provides write access. We are super careful with permissions because by providing read access, a mistake could create cross-client read access and put in peril data safety. So you only will be able to send files, but you won't actually see which files you have already sent

See:

⬆️Uploader

When pushing your dbt run_results with the Uploader, please use file_type :QUALITY

Scheduling the sync

  • You can schedule it using your classic Airflow workflow.

  • Or you can do it any way you deem better 😊

Last updated

Was this helpful?