<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Data that won&#8217;t hold still</title>
	<atom:link href="http://www.sheysrebellion.net/blog/2006/11/07/data-that-wont-hold-still/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sheysrebellion.net/blog/2006/11/07/data-that-wont-hold-still/</link>
	<description>I sleep with pillows on my head.</description>
	<lastBuildDate>Mon, 19 Jul 2010 09:00:04 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ben Scheirman</title>
		<link>http://www.sheysrebellion.net/blog/2006/11/07/data-that-wont-hold-still/comment-page-1/#comment-58</link>
		<dc:creator>Ben Scheirman</dc:creator>
		<pubDate>Tue, 07 Nov 2006 20:09:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.sheysrebellion.net/blog/?p=30#comment-58</guid>
		<description>This is precisely the case where you need to use mock objects for testing.

You  need to be able to write your app given your assumptions (whether they are right or wrong).  Your app talks to the sockets, so you have to introduce a facade that hides that fact.  During testing you mock it out to provide data that you think is realistic.  You will likely have to adapt this as the data changes, but it allows you to move forward.

This is also a good opportunity to put in some effective logging to notify you if data comes in that is not recognized.

NMock2 is a cool mock objects framework, as is RhinoCommons.  They approach syntax a bit differently, so it&#039;s a matter of preference really.</description>
		<content:encoded><![CDATA[<p>This is precisely the case where you need to use mock objects for testing.</p>
<p>You  need to be able to write your app given your assumptions (whether they are right or wrong).  Your app talks to the sockets, so you have to introduce a facade that hides that fact.  During testing you mock it out to provide data that you think is realistic.  You will likely have to adapt this as the data changes, but it allows you to move forward.</p>
<p>This is also a good opportunity to put in some effective logging to notify you if data comes in that is not recognized.</p>
<p>NMock2 is a cool mock objects framework, as is RhinoCommons.  They approach syntax a bit differently, so it&#8217;s a matter of preference really.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
