<?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>Rails Coach by Charles Max Wood &#187; Testing</title>
	<atom:link href="http://charlesmaxwood.com/category/testing-ruby/feed/" rel="self" type="application/rss+xml" />
	<link>http://charlesmaxwood.com</link>
	<description>Building Careers by Building Skills</description>
	<lastBuildDate>Fri, 16 Apr 2010 04:12:45 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Correcting Testing Mistakes: Taking Test Suite Runtime From 3 Hours to 14 Seconds</title>
		<link>http://charlesmaxwood.com/correcting-testing-mistakes-taking-test-suite-runtime-from-3-hours-to-14-seconds/</link>
		<comments>http://charlesmaxwood.com/correcting-testing-mistakes-taking-test-suite-runtime-from-3-hours-to-14-seconds/#comments</comments>
		<pubDate>Sat, 26 Sep 2009 14:35:59 +0000</pubDate>
		<dc:creator>Chuck</dc:creator>
				<category><![CDATA[Blog Posts]]></category>
		<category><![CDATA[Testing]]></category>
		<category><![CDATA[create]]></category>
		<category><![CDATA[data]]></category>
		<category><![CDATA[datasets]]></category>
		<category><![CDATA[isolation]]></category>
		<category><![CDATA[mock]]></category>
		<category><![CDATA[mocking]]></category>
		<category><![CDATA[object]]></category>
		<category><![CDATA[test]]></category>
		<category><![CDATA[testing]]></category>
		<category><![CDATA[unit tests]]></category>

		<guid isPermaLink="false">http://charlesmaxwood.com/?p=428</guid>
		<description><![CDATA[Last week, my development team and I ran across a problem with a library we had written several months before that parsed spreadsheets given to us by one of our clients and inserted the data provided into the database. At the time we weren&#8217;t sure what the problem was. We decided to run the tests [...]]]></description>
		<wfw:commentRss>http://charlesmaxwood.com/correcting-testing-mistakes-taking-test-suite-runtime-from-3-hours-to-14-seconds/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>An Easy 5 Step Process for Test Driven Development</title>
		<link>http://charlesmaxwood.com/an-easy-5-step-process-for-test-driven-development/</link>
		<comments>http://charlesmaxwood.com/an-easy-5-step-process-for-test-driven-development/#comments</comments>
		<pubDate>Tue, 21 Jul 2009 02:53:57 +0000</pubDate>
		<dc:creator>Chuck</dc:creator>
				<category><![CDATA[Testing]]></category>
		<category><![CDATA[Developers]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[rspec]]></category>
		<category><![CDATA[test driven development]]></category>
		<category><![CDATA[testing]]></category>
		<category><![CDATA[tests]]></category>

		<guid isPermaLink="false">http://charlesmaxwood.com/?p=317</guid>
		<description><![CDATA[A lot of people try Test Driven Development by writing the test, writing the code, and then wondering what the big deal is. Here&#8217;s the process I follow along with an explanation of why each step helps. As a quick note, all tests are written with the RSpec framework. 1. Write the test Let&#8217;s say [...]]]></description>
		<wfw:commentRss>http://charlesmaxwood.com/an-easy-5-step-process-for-test-driven-development/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>5 Reasons to do Test Driven or Behavior Driven Development</title>
		<link>http://charlesmaxwood.com/5-reasons-to-do-test-driven-or-behavior-driven-development/</link>
		<comments>http://charlesmaxwood.com/5-reasons-to-do-test-driven-or-behavior-driven-development/#comments</comments>
		<pubDate>Mon, 13 Jul 2009 21:10:07 +0000</pubDate>
		<dc:creator>Chuck</dc:creator>
				<category><![CDATA[Testing]]></category>
		<category><![CDATA[BDD]]></category>
		<category><![CDATA[debugging]]></category>
		<category><![CDATA[Developers]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[TDD]]></category>
		<category><![CDATA[Test First]]></category>
		<category><![CDATA[testers]]></category>
		<category><![CDATA[testing]]></category>
		<category><![CDATA[tests]]></category>

		<guid isPermaLink="false">http://charlesmaxwood.com/?p=314</guid>
		<description><![CDATA[I&#8217;ve had a few discussions with people under various circumstances regarding Test First or Test Driven Development (TDD). Some people swear by TDD, while other don&#8217;t see how it could possibly work because &#8220;I don&#8217;t know how my code works until I write it.&#8221; My answer to this is &#8220;That&#8217;s why you need to write [...]]]></description>
		<wfw:commentRss>http://charlesmaxwood.com/5-reasons-to-do-test-driven-or-behavior-driven-development/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>RSpec vs Test::Unit</title>
		<link>http://charlesmaxwood.com/rspec-vs-testunit/</link>
		<comments>http://charlesmaxwood.com/rspec-vs-testunit/#comments</comments>
		<pubDate>Fri, 10 Jul 2009 06:28:37 +0000</pubDate>
		<dc:creator>Chuck</dc:creator>
				<category><![CDATA[Testing]]></category>
		<category><![CDATA[cucumber]]></category>
		<category><![CDATA[rspec]]></category>
		<category><![CDATA[Ruby]]></category>
		<category><![CDATA[Ruby on Rails]]></category>
		<category><![CDATA[specification]]></category>
		<category><![CDATA[test]]></category>
		<category><![CDATA[test/unit]]></category>
		<category><![CDATA[testing]]></category>
		<category><![CDATA[unit tests]]></category>

		<guid isPermaLink="false">http://charlesmaxwood.com/?p=304</guid>
		<description><![CDATA[Having used both Test::Unit and RSpec, I have to agree with Jim Weirich: the difference between the two is primarily semantics. It seems to me that functionally, they are both equally capable of verifying and specifying code. However, the way in which you write the tests&#8212;the semantics&#8212;is the primary difference between the two. That being [...]]]></description>
		<wfw:commentRss>http://charlesmaxwood.com/rspec-vs-testunit/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
