Add docs on best practice to only run unit tests in dev and CI and exclude them from prod

[graciegoheen]

Contributions

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

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

when should I actually be executing these unit tests?

Best practice to only run unit tests in dev and CI, exclude them in prod (mock data is static, won’t change - waste to run in prod)

• our best practice is to only run your unit tests when you're in development, so that you can have this test-driven development approach, and also in CI to make sure that your changes don't break pre-existing unit tests.

Since my unit tests are only defined on these static inputs, there's actually no reason for me to run these unit tests in production.

DBT_EXCLUDE_RESOURCE_TYPES

• DBT_EXCLUDE_RESOURCE_TYPES a special type of variable that will automatically feed into the right place, so this is all I have to do to exclude unit tests whenever I run dbt build in production, so I don't waste compute running these when I don't need to since my static inputs won't be changing.

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

one of the unit test pages

Additional information

No response