Replies: 2 comments 1 reply
-
What version of dbt are you running? What adapter are you running? I copied your code and I experienced no issues, the unit test ran as desired: $ dbt build -s example
09:22:41 Running with dbt=1.8.5
09:22:41 Registered adapter: duckdb=1.8.3
09:22:41 Found 27 models, 58 data tests, 4 seeds, 10 sources, 1 exposure, 919 macros, 1 unit test
09:22:41
09:22:42 Concurrency: 8 threads (target='dev')
09:22:42
09:22:42 1 of 2 START unit_test example::test_is_valid_country .......................... [RUN]
09:22:42 1 of 2 PASS example::test_is_valid_country ..................................... [PASS in 0.18s]
09:22:42 2 of 2 START sql view model main.example ....................................... [RUN]
09:22:42 2 of 2 OK created sql view model main.example .................................. [OK in 0.10s]
09:22:42
09:22:42 Finished running 1 unit test, 1 view model in 0 hours 0 minutes and 0.56 seconds (0.56s).
09:22:42
09:22:42 Completed successfully
09:22:42
09:22:42 Done. PASS=2 WARN=0 ERROR=0 SKIP=0 TOTAL=2 |
Beta Was this translation helpful? Give feedback.
1 reply
-
I am facing similar issue with most recent version of dbt with Snowflake adapter
Plugins:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, I can’t run unit tests when the model has case-sensitive column names. Is this a known issue?
I’ve tried the unit tests using CSV and SQL formats without success. The only way it works is if I rename the model column names from CountryCode and CountryName to country_code and country_name.
Input reference country_codes table:
The model transformation:
The example model transformation output:
The unit test that doesn’t support case-sensitive column names:
The error I get:
Beta Was this translation helpful? Give feedback.
All reactions