<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blog.alecl.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Assigning Responsibilities</title><link>http://blog.alecl.com/archive/2008/01/14/assigning-responsibilities.aspx</link><description>It’s All about Assigning Responsibilities This example really hit home for me. I am faced with a very similar legacy code design where some processing takes place and an e-mail is sent out. My current tests consist of integration tests that outright send</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.2)</generator><item><title>Testing Theories Part 4 - TypeMock Isolator - The Dark Horse of Unit Testing?</title><link>http://blog.alecl.com/archive/2008/01/14/assigning-responsibilities.aspx#13</link><pubDate>Tue, 19 Feb 2008 05:13:13 GMT</pubDate><guid isPermaLink="false">022ae8cf-15ca-4180-8062-b150ad1660bf:13</guid><dc:creator>Alec Lazarescu's Blog</dc:creator><description>&lt;p&gt;A lot has been discussed on the pro's/con's of IoC for the purposes of unit testing and in general it&lt;/p&gt;
</description></item></channel></rss>