-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow testing of test names, rather than just test type #23
Comments
@ciejer Sorry for the long delay, life has been busy! Yes I really like this idea! I think we'll need to implement another category of meta assertion though: I can look into this in early Feb and get back to you with my thought on implementation, unless you've already forked and got something working :) In which case, I am happy to accept contributions! |
Thanks for the reply @tnightengale! - I've been swamped myself, so no worries about the delay. Thanks again -Chris |
Just looking over the issues list here... One possibility for this might be to piggyback on dbt-expectations? There are some tests already like this: https:/calogica/dbt-expectations#expect_column_to_exist and https:/calogica/dbt-expectations#expect_table_columns_to_contain_set |
This project is awesome!
I'm looking for something that can validate that specific fields have specific tests (every model in a folder must have a not_null test on their load_date_time column).
A proposed implementation might be a prefix:
+required_tests: {"testname!not_null.*load_date_time": 1}
This would require returning an object array rather than string array from tests_per_model (
[{name: not_null_tablename_load_date_time, type: not_null}, ...]
, and adding a case statement to get_regex_match_count to split off and truncate thetestname!
- but would allow far more flexibility in future.I'm happy to contribute with my mediocre python skills if you like the implementation.
The text was updated successfully, but these errors were encountered: