Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Possible Duplicate:
Using IoC for Unit Testing
I am refactoring some tests and the solution uses Ninject for DI via the MS ServiceLocator. There is a separate Ninject module for the tests but in using it the testing code becomes quite difficult to follow.
Do you use DI within your tests or should each test be focussed on creating objects it knows exist? i.e. being more explicit.
Well, while highly subjective, I personally dont use a dependency injection framework when unit testing. Since I use Moq, I typically create
Mock<Whatever>classes and then manually inject the dependencies myself. That way, I can actually mock the results and behavior quickly and easily without worrying what the framework is injecting.