New test: accepted_range

[joellabes]

This is a:

• bug fix PR with no breaking changes (please change the base branch to main)
• new functionality
• a breaking change

Description & motivation

This adds an accepted_range test, allowing users to ensure things like that a percentage is between 0 and 100, or that all accounts were created in the past. Technically, if you made a test with a min_value of 'A' and max_value of '[', I guess you could also check that all names started with a capital letter, but you shouldn't.

I'm open to discussion on the min_value and max_value arguments. I'm tempted to call them greater_than and less_than because I feel like that might make more sense when you're not comparing a scalar number, but I think it's friendlier for the most common case right now.

Checklist

• I have verified that these changes work locally on the following warehouses (Note: it's okay if you do not have access to all warehouses, this helps us understand what has been covered)
  • BigQuery
  • Postgres
  • Redshift
  • Snowflake
• I have updated the README.md (if applicable)
• I have added tests & descriptions to my models (and macros if applicable)
• I have added an entry to the changelog

[clrcrl]

This looks :chefs_kiss:. Lol.

I will test it out later this week :)

[joellabes]

@clrcrl README mistakes are fixed, thanks for catching them! I can see the CI tests failed but can't log into CircleCI to see why - are they mine?

[clrcrl]

We're missing a columns: entry, which is causing the tests to fail

[clrcrl]

Kickin' off those tests now!

[yu-iskw]

Thank you for the great new feeature. I look forward to using it.
BTW, @clrcrl do you have a timeline to release dbt-utils==0.7.0?

[clrcrl]

We'll be doing utils 0.7.0 in line with dbt-core 0.19.0, which I think is coming up in mid-December.

In the meantime, you can either:
(a) install 0.7.0 by including this in your packages.yml:

packages:
- git: https://github.com/fishtown-analytics/dbt-utils.git
  revision: dev/0.7.0

(b) copying this macro into your own project (in the macros directory). Note, you won't need to prefix the test name with dbt_utils in that case.

FWIW, I'd go with (b), just in case we introduce a breaking change into this branch

[yu-iskw]

Thank you for sharing the knowledge. I will try it out.

[yu-iskw]

@clrcrl Please let me know when 0.7.0 is out, if you know. If there is any blocker and anything I can contribute to, please let me know as well. Thanks.