Wow, was busy and missed the whole discussion. :)
My general feeling is that full test suites like this are:
* Easier to write (saving precious time)
* Complete (at least within the bounds of what they're testing)
* Time consuming to run
Obviously the first two are desirable properties and having complete
testing is at times very useful to ensure the correct operation of
code when working with it as a black box.
The time consumed to run these automated tests is problematic though,
hence I would suggest that splitting the tests into a set of "instant
tests" and then a separate set of "full coverage" tests. The full
coverage tests would be handled by the build server (if long enough,
even potentially just once per day). The "instant tests" would be run
all the time as usual.
My general feeling is that NHibernate is under-tested and that it
would be a good idea to allow for larger test suites as things
continue to evolve.
Patrick Earl
