Yes, NHibernate current tests are more integration tests than unit tests, strictly speaking.
A benefit of having "true" unit test would be to have them normally more lightweight. The builds are already taking 15 minutes each per database at minimum. So this could help reducing the ever increasing build time. So why not. Le lundi 16 octobre 2017 23:26:55 UTC+2, Gunnar Liljas a écrit : > > Hi guys! > > What do you think about adding a mocking library to the test projects. The > ones I've used extensively are Moq and NSubstitute, and I like them both. > > Why? Well, some tests call for a bit more decoupling, and if for example > you want to count how many times a method has been called, it's sometimes a > bit much work to have to implement your own mocks. Also, to some extent, > using mocks and more slim lined unit tests serves to highlight > architectural issues. Using full blown database tests is good, and it's > mostly a benefit to the project, but not always. > > /G > -- --- You received this message because you are subscribed to the Google Groups "nhibernate-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to nhibernate-development+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
