> be careful though with the transaction roll back approach, it can hide > some subtle bugs, which may only be found by committing to a db. I > seen a project where they had a all their repositories tested by > executing queries and then rolling back the transaction, but when they > went to production there were quite a few bugs. In the end they had to > write integration tests to flush these out. > IMO at some point you still need to test the integration/functional > parts, to ensure things are working, and there is little benefit in > testing the queries alone
I second this - I have found that you must actually commit and go to another session to ensure that your code is correct. Rollback hides bugs. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. 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/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
