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
dbt-unit-testing is great for unit-testing models.
This is a proposal to extend dbt-unit-testing so it can become great for unit-testing macros as well.
Concrete examples (and a few alternatives) are presented in #122 (currently in draft). Looking for some feedback:
Do you think this belongs within the scope of dbt-unit-testing, or should it be a separate package?
Do you see a way where we could have a single test() macro that supports both model tests and macro tests, or should we keep two separate macros test() and macro_test()?
What are your opinions between macro_test() and macro_test_with_t()? Do you find t useful? is the syntax too confusing?
Do you know of a way that we can test and expect an exception to be raised (like python unittest's assertRaises)?
Naming is hard. If you can think of better names for the macros, please let me know.
Thanks!
The text was updated successfully, but these errors were encountered:
dbt-unit-testing is great for unit-testing models.
This is a proposal to extend dbt-unit-testing so it can become great for unit-testing macros as well.
Concrete examples (and a few alternatives) are presented in #122 (currently in draft). Looking for some feedback:
test()
macro that supports both model tests and macro tests, or should we keep two separate macrostest()
andmacro_test()
?macro_test()
andmacro_test_with_t()
? Do you findt
useful? is the syntax too confusing?assertRaises
)?Thanks!
The text was updated successfully, but these errors were encountered: