Closed marcellovictorino closed 1 year ago
Forgot to tag you here for visibility: @mjirv
Thanks for the review @mjirv . I really appreciate it :) Been a busy week, but I will perform the required changes before the end of the week (2022-10-14)
Closing this in favor of splitting the different features into separate PRs: https://github.com/mjirv/dbt-datamocktool/pull/56
This is a:
Description & motivation
Addressing this issue, enables to define a test once, to be applied over multiple test cases.
Applicable when there are multiple test case scenarios, where the mocked input and expected output data (seed) represent a single case, having the seed file names identified by
test_case_1
,test_case_2
etc.Checklist
Additional comments
I am not sure what is the best way to adapt the proposed code change to the new dispatch pattern. I developed these changes against an old package version (
v 0.1.2
). I marked it with the comment{% FIXME: ...
Also, I have changed the
get_test
macro behavior to always store the mocked model output as a view, which provides better visibility on failing tests. As aview
, it is possible to inspect its definition, quickly debugging any issues