<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>No One Is Perfect &#187; integration</title>
	<atom:link href="http://watchitlater.com/blog/tag/integration/feed/" rel="self" type="application/rss+xml" />
	<link>http://watchitlater.com/blog</link>
	<description>A reluctant foray into the world of blogging.</description>
	<lastBuildDate>Tue, 08 Nov 2011 12:32:55 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Test definitions for developers</title>
		<link>http://watchitlater.com/blog/2010/03/test-definitions-for-developers/</link>
		<comments>http://watchitlater.com/blog/2010/03/test-definitions-for-developers/#comments</comments>
		<pubDate>Fri, 19 Mar 2010 03:53:02 +0000</pubDate>
		<dc:creator>Tom</dc:creator>
				<category><![CDATA[Soap Box]]></category>
		<category><![CDATA[Software Development]]></category>
		<category><![CDATA[acceptance]]></category>
		<category><![CDATA[definition]]></category>
		<category><![CDATA[integration]]></category>
		<category><![CDATA[testing]]></category>
		<category><![CDATA[unit]]></category>

		<guid isPermaLink="false">http://watchitlater.com/blog/?p=201</guid>
		<description><![CDATA[One of the best descriptions of the hierarchy of tests that I have seen comes from &#8220;Growing Object-Oriented Software, Guided by Tests&#8221; by Steve Freeman and Nat Price. 1. Acceptance Tests: Does the whole system work? 2. Integration Tests: Does our code work against code we can&#8217;t change? 3. Unit Tests: Do our objects do [...]]]></description>
			<content:encoded><![CDATA[<p>One of the best descriptions of the hierarchy of tests that I have seen comes from &#8220;<a href="http://amzn.com/0321503627">Growing Object-Oriented Software, Guided by Tests</a>&#8221; by Steve Freeman and Nat Price.</p>
<p>1. <strong>Acceptance Tests</strong>: Does the whole system work?<br />
2. <strong>Integration Tests</strong>: Does our code work against code we can&#8217;t change?<br />
3. <strong>Unit Tests</strong>: Do our objects do the right thing, are they convenient to work with?</p>
<p>Can we now get on with some work, rather than discussing definitions ad nauseam?</p>
]]></content:encoded>
			<wfw:commentRss>http://watchitlater.com/blog/2010/03/test-definitions-for-developers/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

