You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues, and I could not find an existing issue for this feature
I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion
Describe the feature
When testing models with a lot of tests (dozens), it becomes very difficult to target one single generic test (especially when the parameters change during development, which also changes the name of the test).
It would be good to be able to override how the test names are generated so that we can give them more static names. We already have generate_database_name, generate_schema_name, and generate_alias_name which we can use in order to override their respective counterpart.
All we would need is the ability to specify an override for test names with a macro named generate_test_name.
It would also allow us to give generic tests cleaner names than how they are currently generated.
Describe alternatives you've considered
Run all of the tests every single time, but this slows down the development cycle.
We can hardcode a custom name for each test, but this adds a lot of overhead.
Who will this benefit?
People who use a lot of generic tests.
The text was updated successfully, but these errors were encountered:
Is this your first time submitting a feature request?
Describe the feature
When testing models with a lot of tests (dozens), it becomes very difficult to target one single generic test (especially when the parameters change during development, which also changes the name of the test).
It would be good to be able to override how the test names are generated so that we can give them more static names. We already have
generate_database_name
,generate_schema_name
, andgenerate_alias_name
which we can use in order to override their respective counterpart.All we would need is the ability to specify an override for test names with a macro named
generate_test_name
.It would also allow us to give generic tests cleaner names than how they are currently generated.
Describe alternatives you've considered
Who will this benefit?
People who use a lot of generic tests.
The text was updated successfully, but these errors were encountered: