Comments on: Five Steps to Making Fellow Developers Miserable http://DontForgetYourTODOs.com/2009/08/miserable-developers-2/ Sun, 13 Sep 2009 23:37:31 +0000 hourly 1 http://wordpress.org/?v=3.0 By: josh.tucholski http://DontForgetYourTODOs.com/2009/08/miserable-developers-2/comment-page-1/#comment-19 josh.tucholski Fri, 14 Aug 2009 00:32:14 +0000 http://DontForgetYourTODOs.com/?p=320#comment-19 The area that I have run into this the most is with data access components. With Entity Framework, the continuous headache of not being to have an in memory provider or Xml provider has plagued me. Not only am I now bound to requiring database connectivity run unit tests (not true unit testing), but I have to put in the extra effort to initialize and tear down that data for every single test. But yes, I have seen similar implementations to what you discuss, unfortunately for some testing is an afterthought and for others testing correctly gets no thought. The area that I have run into this the most is with data access components. With Entity Framework, the continuous headache of not being to have an in memory provider or Xml provider has plagued me. Not only am I now bound to requiring database connectivity run unit tests (not true unit testing), but I have to put in the extra effort to initialize and tear down that data for every single test.

But yes, I have seen similar implementations to what you discuss, unfortunately for some testing is an afterthought and for others testing correctly gets no thought.

]]> By: John Rzeszotarski http://DontForgetYourTODOs.com/2009/08/miserable-developers-2/comment-page-1/#comment-18 John Rzeszotarski Thu, 13 Aug 2009 18:33:14 +0000 http://DontForgetYourTODOs.com/?p=320#comment-18 Josh, good post. I would be curious to what design pattern you are using to come up with this list as the design patterns themselves should help with minimizing these issues as well. For instance, for using a loosely coupled application with the composite application block, interfaces pass in the data sources to avoid stale data. Great post though. Josh, good post. I would be curious to what design pattern you are using to come up with this list as the design patterns themselves should help with minimizing these issues as well. For instance, for using a loosely coupled application with the composite application block, interfaces pass in the data sources to avoid stale data. Great post though.

]]>