<?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; Automated Testing</title>
	<atom:link href="http://www.natontesting.com/tag/automated-testing/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>Bewildr 0.1.14</title>
		<link>http://www.natontesting.com/2011/11/06/bewildr-0-1-14/</link>
		<comments>http://www.natontesting.com/2011/11/06/bewildr-0-1-14/#comments</comments>
		<pubDate>Sun, 06 Nov 2011 14:09:47 +0000</pubDate>
		<dc:creator>Nat</dc:creator>
				<category><![CDATA[Automated Testing]]></category>
		<category><![CDATA[bewildr]]></category>
		<category><![CDATA[IronRuby]]></category>
		<category><![CDATA[Tools]]></category>

		<guid isPermaLink="false">http://www.natontesting.com/?p=1447</guid>
		<description><![CDATA[Bewildr 0.1.14 is out &#8211; not a massive change: Added a #drag method to Bewildr::Element that works in the same way as the old Bewildr::Mouse#drag_to method &#8211; see here for an example Removed the dependency on ActiveSupport Tidied up the &#8230; <a href="http://www.natontesting.com/2011/11/06/bewildr-0-1-14/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.natontesting.com/2011/11/06/bewildr-0-1-14/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>CSS Locator Reference/Cheat Sheet for XPath people</title>
		<link>http://www.natontesting.com/2011/09/24/css-locator-referencecheat-sheet-for-xpath-people/</link>
		<comments>http://www.natontesting.com/2011/09/24/css-locator-referencecheat-sheet-for-xpath-people/#comments</comments>
		<pubDate>Sat, 24 Sep 2011 14:44:04 +0000</pubDate>
		<dc:creator>Nat</dc:creator>
				<category><![CDATA[Automated Testing]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[css]]></category>
		<category><![CDATA[xpath]]></category>

		<guid isPermaLink="false">http://www.natontesting.com/?p=1398</guid>
		<description><![CDATA[One of the main factors in maintainable web testing is how good your element locators are. I&#8217;ve always used xpath since I&#8217;ve found it reliable and requiring very little maintenance (see this comment thread). But after playing with css locators &#8230; <a href="http://www.natontesting.com/2011/09/24/css-locator-referencecheat-sheet-for-xpath-people/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.natontesting.com/2011/09/24/css-locator-referencecheat-sheet-for-xpath-people/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Bewildr 0.1.13</title>
		<link>http://www.natontesting.com/2011/07/05/bewildr-0-1-13/</link>
		<comments>http://www.natontesting.com/2011/07/05/bewildr-0-1-13/#comments</comments>
		<pubDate>Tue, 05 Jul 2011 20:44:30 +0000</pubDate>
		<dc:creator>Nat</dc:creator>
				<category><![CDATA[bewildr]]></category>
		<category><![CDATA[Example Code]]></category>
		<category><![CDATA[IronRuby]]></category>
		<category><![CDATA[Ruby]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[Automated Testing]]></category>

		<guid isPermaLink="false">http://www.natontesting.com/?p=1307</guid>
		<description><![CDATA[[So much for the hope of doing "more frequent releases"...] It&#8217;s update time again. A few additions to the API, and a couple of changes. First, the additions: Added a &#8216;wait_for&#8217; alias to &#8216;wait_for_existence_of&#8217; &#8211; much nicer Added Bewildr::Application#process to &#8230; <a href="http://www.natontesting.com/2011/07/05/bewildr-0-1-13/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.natontesting.com/2011/07/05/bewildr-0-1-13/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>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>
	</channel>
</rss>

