And another note now that I've been thinking about your "issue" ...
You are absolutely right to be breaking the SQL db dependency. Your *UNIT TESTS* should never go near a database, the database should only really come into the picture at the Integration Test level, I have been using Bob Martin's FitNesse for a while now, and in fact we are rolling it out as the Integration Test Framework across the entire development department here. I don't particularly like the tool itself, but I really do like what the tool represents and enables and in the absence of anything better, it is fit for purpose (if you'll excuse the pun). It enables us to capture all domain information and our user stories within the Wiki, and then to hook those stories up to acceptance tests by using the FITRunner. This means that the Product Owners can use the same tool as the developers to write out their requirements in plain English, which ultimately results in our domain specific language, and ALL of it is captured within our tests. This of course has the added benefit that any developer can join any project and get up to speed in a matter of hours simply by reading and running the test suite :) -- You received this message because you are subscribed to the Google Groups "Rhino.Mocks" group. To view this discussion on the web visit https://groups.google.com/d/msg/rhinomocks/-/x4qNh7uZv0gJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhinomocks?hl=en.
