<?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; cucumber</title>
	<atom:link href="http://www.natontesting.com/tag/cucumber/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>Tag based logic in Cucumber</title>
		<link>http://www.natontesting.com/2011/12/12/tag-based-logic-in-cucumber/</link>
		<comments>http://www.natontesting.com/2011/12/12/tag-based-logic-in-cucumber/#comments</comments>
		<pubDate>Mon, 12 Dec 2011 18:39:36 +0000</pubDate>
		<dc:creator>Nat</dc:creator>
				<category><![CDATA[Automated Testing]]></category>
		<category><![CDATA[BDD]]></category>
		<category><![CDATA[cucumber]]></category>
		<category><![CDATA[Example Code]]></category>
		<category><![CDATA[Making Life Easier]]></category>
		<category><![CDATA[Ruby]]></category>
		<category><![CDATA[Test Management]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Test Case Management]]></category>
		<category><![CDATA[Test Data]]></category>

		<guid isPermaLink="false">http://www.natontesting.com/?p=1456</guid>
		<description><![CDATA[Sometimes cucumber&#8217;s Before hook just doesn&#8217;t cut it. Here&#8217;s a nice hack that allows you to perform some logic during execution of cucumber scenarios when a tag is first come across: It&#8217;s a cucumber formatter that detects when a tag &#8230; <a href="http://www.natontesting.com/2011/12/12/tag-based-logic-in-cucumber/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.natontesting.com/2011/12/12/tag-based-logic-in-cucumber/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<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>Cucumber formatter for unused steps</title>
		<link>http://www.natontesting.com/2011/04/05/cucumber-formatter-for-unused-steps/</link>
		<comments>http://www.natontesting.com/2011/04/05/cucumber-formatter-for-unused-steps/#comments</comments>
		<pubDate>Tue, 05 Apr 2011 20:18:32 +0000</pubDate>
		<dc:creator>Nat</dc:creator>
				<category><![CDATA[cucumber]]></category>
		<category><![CDATA[Ruby]]></category>
		<category><![CDATA[Automated Testing]]></category>

		<guid isPermaLink="false">http://www.natontesting.com/?p=1244</guid>
		<description><![CDATA[As time goes on in a project using cucumber you&#8217;ll end up with some steps which no longer get called, and you probably want to delete them. Annoyingly, there isn&#8217;t a built-in formatter you can use to find out where &#8230; <a href="http://www.natontesting.com/2011/04/05/cucumber-formatter-for-unused-steps/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.natontesting.com/2011/04/05/cucumber-formatter-for-unused-steps/feed/</wfw:commentRss>
		<slash:comments>1</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>IronRuby vs. Gherkin &#8211; a temporary fix</title>
		<link>http://www.natontesting.com/2010/08/13/ironruby-vs-gherkin-a-temporary-fix/</link>
		<comments>http://www.natontesting.com/2010/08/13/ironruby-vs-gherkin-a-temporary-fix/#comments</comments>
		<pubDate>Fri, 13 Aug 2010 17:32:14 +0000</pubDate>
		<dc:creator>Nat</dc:creator>
				<category><![CDATA[cucumber]]></category>
		<category><![CDATA[IronRuby]]></category>
		<category><![CDATA[Making Life Easier]]></category>
		<category><![CDATA[Ruby]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[Automated Testing]]></category>

		<guid isPermaLink="false">http://www.natontesting.com/?p=1039</guid>
		<description><![CDATA[IronRuby doesn&#8217;t currently work with the latest versions of cucumber. This is a known bug and is a real pain. There is a work around, and it&#8217;s kinda rubbish: don&#8217;t use any versions of cucumber &#62; 0.6.3. After that version, &#8230; <a href="http://www.natontesting.com/2010/08/13/ironruby-vs-gherkin-a-temporary-fix/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.natontesting.com/2010/08/13/ironruby-vs-gherkin-a-temporary-fix/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Netbeans &#8216;Cucumber Features&#8217; plugin in Beta!</title>
		<link>http://www.natontesting.com/2010/06/07/netbeans-cucumber-features-plugin-in-beta/</link>
		<comments>http://www.natontesting.com/2010/06/07/netbeans-cucumber-features-plugin-in-beta/#comments</comments>
		<pubDate>Mon, 07 Jun 2010 16:41:07 +0000</pubDate>
		<dc:creator>Nat</dc:creator>
				<category><![CDATA[cucumber]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[NetBeans]]></category>

		<guid isPermaLink="false">http://www.natontesting.com/?p=950</guid>
		<description><![CDATA[The best ruby IDE, Netbeans, now has a Cucumber plugin in beta! It&#8217;s the old &#8220;QuBiT&#8221; plugin that I&#8217;ve been using for a while though it looks like it&#8217;s been rebranded as the &#8220;Cucumber Features&#8221; plugin. Here it is: As &#8230; <a href="http://www.natontesting.com/2010/06/07/netbeans-cucumber-features-plugin-in-beta/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.natontesting.com/2010/06/07/netbeans-cucumber-features-plugin-in-beta/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Remove junk from IronRuby cucumber output</title>
		<link>http://www.natontesting.com/2010/04/06/remove-junk-from-ironruby-cucumber-output/</link>
		<comments>http://www.natontesting.com/2010/04/06/remove-junk-from-ironruby-cucumber-output/#comments</comments>
		<pubDate>Tue, 06 Apr 2010 17:36:19 +0000</pubDate>
		<dc:creator>Nat</dc:creator>
				<category><![CDATA[Automated Testing]]></category>
		<category><![CDATA[cucumber]]></category>
		<category><![CDATA[IronRuby]]></category>
		<category><![CDATA[Ruby]]></category>
		<category><![CDATA[Tools]]></category>

		<guid isPermaLink="false">http://www.natontesting.com/?p=847</guid>
		<description><![CDATA[When running cucumber tests under IronRuby, your output will be full of junk like the following: Feature: example feature Scenario: a scenario←[90m     # features\testoutput.feature:3←[0m ←[32mGiven some test setup←[90m  # features/step_definitions/output_steps.rb:1←[0m←[0m ←[32mWhen I do something←[90m    # features/step_definitions/output_steps.rb:5←[0m←[0m ←[32mThen something happens←[90m # &#8230; <a href="http://www.natontesting.com/2010/04/06/remove-junk-from-ironruby-cucumber-output/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.natontesting.com/2010/04/06/remove-junk-from-ironruby-cucumber-output/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Updated script to list all cucumber step definitions</title>
		<link>http://www.natontesting.com/2010/01/11/updated-script-to-list-all-cucumber-step-definitions/</link>
		<comments>http://www.natontesting.com/2010/01/11/updated-script-to-list-all-cucumber-step-definitions/#comments</comments>
		<pubDate>Mon, 11 Jan 2010 17:57:05 +0000</pubDate>
		<dc:creator>Nat</dc:creator>
				<category><![CDATA[Automated Testing]]></category>
		<category><![CDATA[cucumber]]></category>
		<category><![CDATA[Example Code]]></category>
		<category><![CDATA[Making Life Easier]]></category>
		<category><![CDATA[Ruby]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[Regular Expressions]]></category>

		<guid isPermaLink="false">http://www.natontesting.com/?p=703</guid>
		<description><![CDATA[In a previous post I put up a small script that would dump out all step definitions available in a cucumber project. Here&#8217;s an updated version&#8230; it hasn&#8217;t changed much apart from the output is now a html table that &#8230; <a href="http://www.natontesting.com/2010/01/11/updated-script-to-list-all-cucumber-step-definitions/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.natontesting.com/2010/01/11/updated-script-to-list-all-cucumber-step-definitions/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

