<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://weblogs.asp.net/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>Strict Mocks</title><link>http://weblogs.asp.net/sfeldman/archive/2008/10/22/strict-mocks.aspx</link><description>I am extremely excited to be a part of a team that has deliberately decided to follow the Agile path and TDD way of producing results. Along with that I am learning myself tones. As a team, the decision was made to use strict mocks to understand better</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP1 (Build: 20510.895)</generator><item><title>re: Strict Mocks</title><link>http://weblogs.asp.net/sfeldman/archive/2008/10/22/strict-mocks.aspx#6700172</link><pubDate>Thu, 23 Oct 2008 17:43:31 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:6700172</guid><dc:creator>Darrell Mozingo</dc:creator><author>Darrell Mozingo</author><description>&lt;p&gt;The only time we use strict mocks is when the procedure for calling a 3rd party API is *very* regulated (i.e., if calls are made out of order, the external system produces incorrect results). This doesn&amp;#39;t happen very often, therefore we don&amp;#39;t use strict mocks that often. We mostly stick to stubs unless we actually care about an interaction, in which case we use dynamic mocks.&lt;/p&gt;
&lt;p&gt;Good luck!&lt;/p&gt;
&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=6700172" width="1" height="1"&gt;</description></item></channel></rss>