<?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>Nat On Testing &#187; RSpec</title>
	<atom:link href="http://www.natontesting.com/tag/rspec/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.natontesting.com</link>
	<description>nathaniel ritmeyer&#039;s thoughts on automated software testing</description>
	<lastBuildDate>Wed, 18 Jan 2012 21:15:06 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Precision Failure</title>
		<link>http://www.natontesting.com/2011/10/31/precision-failure/</link>
		<comments>http://www.natontesting.com/2011/10/31/precision-failure/#comments</comments>
		<pubDate>Mon, 31 Oct 2011 21:30:31 +0000</pubDate>
		<dc:creator>Nat</dc:creator>
				<category><![CDATA[Automated Testing]]></category>
		<category><![CDATA[cucumber]]></category>
		<category><![CDATA[Making Life Easier]]></category>
		<category><![CDATA[RSpec]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[Example Code]]></category>
		<category><![CDATA[Ruby]]></category>

		<guid isPermaLink="false">http://www.natontesting.com/?p=1426</guid>
		<description><![CDATA[When tests fail it&#8217;s nice to know why. The more precise a failure message is and the less time required to investigate why the test failed, the better. When trying to find out what broke the test, this&#8230; Failure/Error: search_field.should_not &#8230; <a href="http://www.natontesting.com/2011/10/31/precision-failure/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.natontesting.com/2011/10/31/precision-failure/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to get the RSpec test result in the after block</title>
		<link>http://www.natontesting.com/2011/06/25/how-to-get-the-rspec-test-result-in-the-after-block/</link>
		<comments>http://www.natontesting.com/2011/06/25/how-to-get-the-rspec-test-result-in-the-after-block/#comments</comments>
		<pubDate>Sat, 25 Jun 2011 15:55:08 +0000</pubDate>
		<dc:creator>Nat</dc:creator>
				<category><![CDATA[Automated Testing]]></category>
		<category><![CDATA[Example Code]]></category>
		<category><![CDATA[RSpec]]></category>
		<category><![CDATA[Ruby]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.natontesting.com/?p=1295</guid>
		<description><![CDATA[&#8212;UPDATE&#8212; The change I asked for made it into rspec so you can now call example.exception out of the box! &#8212;/UPDATE&#8212; RSpec allows you to run a block of code at the end of each test using the after(:each) method. &#8230; <a href="http://www.natontesting.com/2011/06/25/how-to-get-the-rspec-test-result-in-the-after-block/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.natontesting.com/2011/06/25/how-to-get-the-rspec-test-result-in-the-after-block/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Custom RSpec &#8216;progress-with-names&#8217; formatter</title>
		<link>http://www.natontesting.com/2011/04/20/custom-rspec-progress-with-names-formatter/</link>
		<comments>http://www.natontesting.com/2011/04/20/custom-rspec-progress-with-names-formatter/#comments</comments>
		<pubDate>Wed, 20 Apr 2011 17:47:39 +0000</pubDate>
		<dc:creator>Nat</dc:creator>
				<category><![CDATA[Automated Testing]]></category>
		<category><![CDATA[Example Code]]></category>
		<category><![CDATA[RSpec]]></category>
		<category><![CDATA[Ruby]]></category>
		<category><![CDATA[Tools]]></category>

		<guid isPermaLink="false">http://www.natontesting.com/?p=1265</guid>
		<description><![CDATA[RSpec&#8216;s progress formatter (the one that produces output like ......F..*...FF....) produces very concise output &#8211; which is usually all anybody wants. But there&#8217;s a problem with that: if your tests are being run from hudson/jenkins and you want to watch &#8230; <a href="http://www.natontesting.com/2011/04/20/custom-rspec-progress-with-names-formatter/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.natontesting.com/2011/04/20/custom-rspec-progress-with-names-formatter/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>RSpec and ci_reporter</title>
		<link>http://www.natontesting.com/2011/01/12/rspec-and-ci_reporter/</link>
		<comments>http://www.natontesting.com/2011/01/12/rspec-and-ci_reporter/#comments</comments>
		<pubDate>Wed, 12 Jan 2011 18:50:57 +0000</pubDate>
		<dc:creator>Nat</dc:creator>
				<category><![CDATA[Automated Testing]]></category>
		<category><![CDATA[Example Code]]></category>
		<category><![CDATA[Making Life Easier]]></category>
		<category><![CDATA[RSpec]]></category>
		<category><![CDATA[Ruby]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[agile]]></category>

		<guid isPermaLink="false">http://www.natontesting.com/?p=1191</guid>
		<description><![CDATA[In order to use rspec within hudson, you need to use the ci_reporter gem. The gem extends rspec&#8217;s behaviour to include the junit-style output required by hudson. Annoyingly, the documentation for creating a rspec rake task that uses ci_reporter is &#8230; <a href="http://www.natontesting.com/2011/01/12/rspec-and-ci_reporter/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.natontesting.com/2011/01/12/rspec-and-ci_reporter/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Upgrading from RSpec 1 to RSpec 2</title>
		<link>http://www.natontesting.com/2010/11/02/upgrading-from-rspec-1-to-rspec-2/</link>
		<comments>http://www.natontesting.com/2010/11/02/upgrading-from-rspec-1-to-rspec-2/#comments</comments>
		<pubDate>Tue, 02 Nov 2010 18:28:14 +0000</pubDate>
		<dc:creator>Nat</dc:creator>
				<category><![CDATA[RSpec]]></category>
		<category><![CDATA[Tools]]></category>

		<guid isPermaLink="false">http://www.natontesting.com/?p=1126</guid>
		<description><![CDATA[If you&#8217;re upgrading from rspec 1 to rspec 2, details of the differences are here: http://github.com/rspec/rspec-core/blob/master/Upgrade.markdown The specific changes you&#8217;ll need to make to your rake file can be found here: http://pivotallabs.com/users/alex/blog/articles/1451-upgrading-your-rakefile-from-rspec-1-3-to-rspec-2]]></description>
		<wfw:commentRss>http://www.natontesting.com/2010/11/02/upgrading-from-rspec-1-to-rspec-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Is Cucumber adding value to your project? The Chicken Test!</title>
		<link>http://www.natontesting.com/2010/10/19/is-cucumber-adding-value-to-your-project-the-chicken-test/</link>
		<comments>http://www.natontesting.com/2010/10/19/is-cucumber-adding-value-to-your-project-the-chicken-test/#comments</comments>
		<pubDate>Tue, 19 Oct 2010 22:01:21 +0000</pubDate>
		<dc:creator>Nat</dc:creator>
				<category><![CDATA[agile]]></category>
		<category><![CDATA[Automated Testing]]></category>
		<category><![CDATA[cucumber]]></category>
		<category><![CDATA[RSpec]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[agile testing]]></category>
		<category><![CDATA[Test Case Management]]></category>
		<category><![CDATA[Test::Unit]]></category>

		<guid isPermaLink="false">http://www.natontesting.com/?p=1098</guid>
		<description><![CDATA[Don&#8217;t get me wrong &#8211; I love cucumber. I&#8217;ve been on projects where it has been used successfully and I&#8217;d partly attribute the success of those projects to the use of cucumber. It is a fantastic tool for BDD. When used &#8230; <a href="http://www.natontesting.com/2010/10/19/is-cucumber-adding-value-to-your-project-the-chicken-test/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.natontesting.com/2010/10/19/is-cucumber-adding-value-to-your-project-the-chicken-test/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Get HTML output from Test::Unit by using RSpec !?</title>
		<link>http://www.natontesting.com/2009/09/18/get-html-output-from-testunit-by-using-rspec/</link>
		<comments>http://www.natontesting.com/2009/09/18/get-html-output-from-testunit-by-using-rspec/#comments</comments>
		<pubDate>Fri, 18 Sep 2009 19:37:25 +0000</pubDate>
		<dc:creator>Nat</dc:creator>
				<category><![CDATA[Example Code]]></category>
		<category><![CDATA[Making Life Easier]]></category>
		<category><![CDATA[RSpec]]></category>
		<category><![CDATA[Ruby]]></category>
		<category><![CDATA[Test::Unit]]></category>
		<category><![CDATA[Automated Testing]]></category>
		<category><![CDATA[Tools]]></category>

		<guid isPermaLink="false">http://www.natontesting.com/?p=422</guid>
		<description><![CDATA[Test::Unit&#8216;s lack of pretty xml/html output led me to look around to see what was available. Turns out that there&#8217;s a very simple way to get html output&#8230; run your Test::Unit tests with rspec! Here&#8217;s a contrived and simple example &#8230; <a href="http://www.natontesting.com/2009/09/18/get-html-output-from-testunit-by-using-rspec/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.natontesting.com/2009/09/18/get-html-output-from-testunit-by-using-rspec/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
	</channel>
</rss>

