I agree, running queries against real DB and check what does it really find is more reasonable. I've looked through NDbUnit and it seems that the idea is similar to that we've been using (with the exception of not using Xml DB schema configuration :o) ). Our current project uses ActiveRecord, Windsor Container and AR facility, and for managing DB schema changes we're using Migrator Dot NET . So before each test runs db schema is recreated, and to run queries against DB our base test provides reference to Container, and actual test resolves necessary repository, or service. This approach works, but it is quite heavy and while the number of database dependent tests and migrations increases it may become very slow to run all the tests. To make it faster it is possible to recreate db schema on Fixture Setup, and on Test Setup just truncate all data from all tables. Also i played with SQL Lite some time ago, but haven't used it in the real projects yet. For most scenarios it seems to be useful, but if some features of MS SQL Server are used, it becomes not appliable.
Thank you all for your replies! Generally I was wondering if there are any other approaches that can be applied easier, because current scenario is not easy to support, but seems Silver Bullet is not invented yet. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
