We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug With current implement, when user set a wrong metric (type-missed or any reason), the test always succeed https://github.com/re-data/dbt-re-data/blob/main/macros/tests/test_metrics.sql#L6
Although it might be by-design feature but reporting the situation as a failure might be more intuitive.
Expected behavior Report the test as failure when wrong metric is set.
To Reproduce Run a test with not-existed. For example row_countx instead row_count
row_countx
row_count
Screenshots Logs and additional context
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
With current implement, when user set a wrong metric (type-missed or any reason), the test always succeed
https://github.com/re-data/dbt-re-data/blob/main/macros/tests/test_metrics.sql#L6
Although it might be by-design feature but reporting the situation as a failure might be more intuitive.
Expected behavior
Report the test as failure when wrong metric is set.
To Reproduce
Run a test with not-existed. For example
row_countx
insteadrow_count
Screenshots
Logs and additional context
The text was updated successfully, but these errors were encountered: