Question

I’ve got NHibernate-based (constructor ISessionFactory injection) generic repository implementation which is stored inside DAL. It implements contract which is stored in `Domain Layer’.

Should I test real repository behavior using SQl CE or should I refactor my application to support agnostic-like (like in Tim Maccharty’s book http://www.wrox.com/WileyCDA/WroxTitle/productCd-0470147563,descCd-authorInfo.html) Unit of Work and then give my fake implementation of IUnitOfWorkRepository?

Is it a valid approach to run tests on a local database exposing real repository implementation?

Thanks!

Answer 1

The issue is what your are testing and why. That will answer the question.

If:

I want to test a third party tool

That is, are you testing if NHibernate is working (not a kind of test
I do). Then do whatever it requires, so refactoring not required. Loose yourself.

I want to test how my code interacts with a thrid party tool

Then you are talking about what I like to call a interaction test. Refactoring is required as your more interested in how your using NHiberate than if it works.

I want to test my code

The abstract NHibernate entirely. Do whatever is necessary … wrapper? Your now back into unit testing.

I want to test my application from a user point of view

I think this is above the scope your talking. But you can use this scope talking about components. So … hmmm … worthwhile but not easy. Not a unit test, so you want to instantiate the component/app and run the whole thing as its ‘user’ does. I call these ‘UATs’ and usually implement as ‘Coded UATs’.