http://jameskovacs.com/2006/09/10/a-tale-of-two-epiphanies-tdd-and-mocking/ Wed, 21 Mar 2012 14:32:22 +0000 hourly 1 http://wordpress.org/?v=3.1 http://jameskovacs.com/2006/09/10/a-tale-of-two-epiphanies-tdd-and-mocking/comment-page-1/#comment-730 James Tue, 25 May 2010 03:51:06 +0000 http://jameskovacs.com/2006/09/10/A+Tale+Of+Two+Epiphanies+TDD+And+Mocking#comment-730 @csokun - Since writing this post, I have reconsidered using interfaces for domain classes. So I don't have IDepartment, ICustomer, IOrder, etc. In my tests, I use concrete classes and simplify creation using an ObjectMother. If I need to stub domain behaviour, I'll mark methods as virtual. (Typically I'm using NHibernate, which requires virtuals for proxying.) I still use interfaces heavily for domain and infrastructure services, such as IDepartmentTask, IDepartmentRepository, IValidator<Department>, etc. @csokun – Since writing this post, I have reconsidered using interfaces for domain classes. So I don’t have IDepartment, ICustomer, IOrder, etc. In my tests, I use concrete classes and simplify creation using an ObjectMother. If I need to stub domain behaviour, I’ll mark methods as virtual. (Typically I’m using NHibernate, which requires virtuals for proxying.) I still use interfaces heavily for domain and infrastructure services, such as IDepartmentTask, IDepartmentRepository, IValidator, etc.

]]> http://jameskovacs.com/2006/09/10/a-tale-of-two-epiphanies-tdd-and-mocking/comment-page-1/#comment-711 csokun Sat, 22 May 2010 11:29:40 +0000 http://jameskovacs.com/2006/09/10/A+Tale+Of+Two+Epiphanies+TDD+And+Mocking#comment-711 thanks for the post it is exactly the situation I am in right now and this help me a lot only one doubt IDepartment interface look like we had to create a lot of interface for each POCO class aren't we? thanks for the post it is exactly the situation I am in right now and this help me a lot only one doubt IDepartment interface look like we had to create a lot of interface for each POCO class aren’t we?

]]>