I've recently done my first implementation of dbt and though its fundamental Jinja+yaml nature does show through a bit, I was really pleasantly charmed by the d

I've recently done my first implementation of dbt and though its fundamental Jinja+yaml nature does show through a bit, I was really pleasantly charmed by the data testing. The catalog of data assertions (dbt-utils and dbt-expectations really fill out the bare bones default tests) is generic across data sources, intermediate tables, or output tables, and is typically 3-5 lines of yaml for any given test. Hits all the basics: nullness, uniqueness, freshness, value cardinality, value distribution, row count, foreign key validity, etc. I still don't like the yaml completely, but it makes adding data assertions so easy there is no excuse not to. This project is pretty black and white, but I'm glad dbt supports test failure severity to lower on call load (error vs warning) when I have the need. Just wanted to add a positive review for dbt, that it made it fun to do better data testing!