As the project lead for NDbUnit for the past several years, I think that's a great idea :)
Seriously though, since NDbUnit supports both SQLite and SQLServer (as well as other targets like MySQL, etc.) it would be a useful strategy to help manage DB state during the test-runs. Although oracle support is still a work-in-progress, NDbUnit is in fact tailor-made to address just this challenge (pre-loading of data into the DB during integration tests that need DB state managed simply). For the record, I'm uncertain if it will result in speed increase over your present approach, however but I'd be interested in your results should you attempt this approach. Steve Bohlen [email protected] http://blog.unhandled-exceptions.com http://twitter.com/sbohlen On Wed, Dec 16, 2009 at 4:24 PM, Steve Strong <[email protected]> wrote: > Any objections to us using NDbUnit for database population in some of the > NH tests? In the Linq tests, I've got a fairly large dataset which, to keep > it independent from the database, I'm inserting it by creating instances and > adding them to the session. I'm guessing the NDbUnit will achieve the same > goal (database independence) but may well run quicker. Thoughts= > > Cheers, > > Steve
