tag:blogger.com,1999:blog-9099513356252812992.post5680771847651001971..comments2015-05-18T10:50:27.375+12:00Comments on Software Hero Worship: Tests For Your DataJohn Hursthttp://www.blogger.com/profile/12700400206114898455noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-9099513356252812992.post-26975018746302487492008-07-28T21:12:00.000+12:002008-07-28T21:12:00.000+12:00Nigel,Those are great questions. I wanted to addr...Nigel,<BR/><BR/>Those are great questions. I wanted to address some of them in the post,<BR/>but didn't want it to be too long. (It's already too long.)<BR/><BR/>Since I can't answer the questions effectively in a short comment, I've<BR/>written a new post!<BR/><BR/>JHJohn Hursthttps://www.blogger.com/profile/14094789833446238837noreply@blogger.comtag:blogger.com,1999:blog-9099513356252812992.post-64480188549072514982008-07-27T11:41:00.000+12:002008-07-27T11:41:00.000+12:00Hi JohnInteresting article. I've got a few questi...Hi John<BR/><BR/>Interesting article. I've got a few questions to help me understand the circumstances in which you would recommend this approach.<BR/><BR/>Are there any types of data that have you found this approach to be particularly good or bad for? <BR/><BR/>Do you always have matching constraints in your application, so this is really being used as a double check? Or is this used in cases where there aren't application checks (eg. manual load)?<BR/><BR/>Do you run this in all your environments? In which environment do you find the most failures? Do you get production failures for these tests?<BR/><BR/>Considering the Continuous Integration analogy, this approach is at the "nightly build" end of the CI spectrum. Are these views used in a more continual manner during development? These views could be useful as assertions in your integration and system tests, rapidly identifying any code that is violating the constraints.<BR/><BR/>Cheers<BR/>NigelNigelhttps://www.blogger.com/profile/14935723589029857874noreply@blogger.com