thank you for this comment.
This seems like a good idea, but I can't imagine having time to set up these tests.
When a development team starts to follow the agile development pattern, source control, build and test are the "must" artifacts. Speaking about evolutionary development on databases, covering you biz logic with tests allows you to prevent regressions and to refactor your database schemas in a reliable way. I think that evolutionary database should include test suites, always.
Do many companies really run these types of test on their database schema?
My italian customers didn't even hear about database unit testing. But some company switched from a waterfall approach to an agile one (like scrum) and then they started to implement test BEFORE the real biz logic (TDD manner).
My experience has been that we don't even have time for documentation, which would have to come before unit testing.
Actually, when we started to write tests, we tried to create them self-documented. I think that a test can describe in the best way certain features. The biz logic, for sure, should be small (ligthweight code) in order to be "testable".
That said, good article explaining how to do this and I love that it included an easy to understand example.
Thank you so much David.