No problem.
btw have a look to this NUnit 2.5 feature
http://www.nunit.org/index.php?p=setupFixture&r=2.5.3

<http://www.nunit.org/index.php?p=setupFixture&r=2.5.3>In my integration
tests I have some read-only tests to test queries and performance (using our
Statistics because I don't like "tests by eyes" so much).
I'm using the SetUpFixtureAttribute to set the WellKnownDb state before run
all tests in the ReadOnly and Performance integration-test-suite (the db is
populated before run-tests and destroyed after tests).

P.S. I'll upgrade NUnit and Castle-DynProxy soon.

2009/12/16 Steve Strong <[email protected]>

> 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




-- 
Fabio Maulo

Reply via email to