<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule">

<channel>
	<title>Nat On Testing &#187; Test::Unit</title>
	<atom:link href="http://www.natontesting.com/tag/testunit/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.natontesting.com</link>
	<description>nathaniel ritmeyer&#039;s thoughts on automated UI testing</description>
	<lastBuildDate>Mon, 06 Sep 2010 23:08:55 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
<creativeCommons:license>http://creativecommons.org/licenses/by-nc/3.0/</creativeCommons:license>		<item>
		<title>TURN: test::unit reporting as it should have been&#8230;</title>
		<link>http://www.natontesting.com/2010/03/30/turn-testunit-reporting-as-it-should-have-been/</link>
		<comments>http://www.natontesting.com/2010/03/30/turn-testunit-reporting-as-it-should-have-been/#comments</comments>
		<pubDate>Tue, 30 Mar 2010 17:30:33 +0000</pubDate>
		<dc:creator>Nat</dc:creator>
				<category><![CDATA[Automated Testing]]></category>
		<category><![CDATA[Making Life Easier]]></category>
		<category><![CDATA[Ruby]]></category>
		<category><![CDATA[Test::Unit]]></category>
		<category><![CDATA[Tools]]></category>

		<guid isPermaLink="false">http://www.natontesting.com/?p=839</guid>
		<description><![CDATA[TURN (&#8220;Test::Unit Reporter (New)&#8221;) aims to fix test::unit&#8216;s default output. Instead of waiting until the end of a test run for failure details, Turn displays failures immediately. It looks promising&#8230; Bookmark to:]]></description>
		<wfw:commentRss>http://www.natontesting.com/2010/03/30/turn-testunit-reporting-as-it-should-have-been/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to test a WPF app using IronRuby and White</title>
		<link>http://www.natontesting.com/2010/02/17/how-to-test-a-wpf-app-using-ironruby-and-white/</link>
		<comments>http://www.natontesting.com/2010/02/17/how-to-test-a-wpf-app-using-ironruby-and-white/#comments</comments>
		<pubDate>Wed, 17 Feb 2010 23:17:11 +0000</pubDate>
		<dc:creator>Nat</dc:creator>
				<category><![CDATA[Automated Testing]]></category>
		<category><![CDATA[Example Code]]></category>
		<category><![CDATA[IronRuby]]></category>
		<category><![CDATA[Making Life Easier]]></category>
		<category><![CDATA[Ruby]]></category>
		<category><![CDATA[Test::Unit]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[bewildr]]></category>
		<category><![CDATA[white]]></category>
		<category><![CDATA[NetBeans]]></category>

		<guid isPermaLink="false">http://www.natontesting.com/?p=724</guid>
		<description><![CDATA[&#8212;UPDATE&#8212; Since I wrote this post, I have put together a ruby gem designed for testing WPF UIs called &#8216;bewildr&#8217;. I wrote up an introductory post about bewildr here. Bewildr removes the need for using White &#8211; it&#8217;s written in &#8230; <a href="http://www.natontesting.com/2010/02/17/how-to-test-a-wpf-app-using-ironruby-and-white/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.natontesting.com/2010/02/17/how-to-test-a-wpf-app-using-ironruby-and-white/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Lessons from a watir success story</title>
		<link>http://www.natontesting.com/2009/12/19/lessons-from-a-watir-success-story/</link>
		<comments>http://www.natontesting.com/2009/12/19/lessons-from-a-watir-success-story/#comments</comments>
		<pubDate>Sat, 19 Dec 2009 16:01:12 +0000</pubDate>
		<dc:creator>Nat</dc:creator>
				<category><![CDATA[Automated Testing]]></category>
		<category><![CDATA[Ruby]]></category>
		<category><![CDATA[Test Management]]></category>
		<category><![CDATA[Test::Unit]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[WATIR]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[FireBug]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[Firewatir]]></category>
		<category><![CDATA[NetBeans]]></category>

		<guid isPermaLink="false">http://www.natontesting.com/?p=623</guid>
		<description><![CDATA[There aren&#8217;t enough UI test automation success stories documented on the net, so here&#8217;s my contribution. This post is about  how we started with zero automated UI testing capability, and how a couple of months later we had the capability &#8230; <a href="http://www.natontesting.com/2009/12/19/lessons-from-a-watir-success-story/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.natontesting.com/2009/12/19/lessons-from-a-watir-success-story/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>Screencast: Beginning with Cucumber</title>
		<link>http://www.natontesting.com/2009/11/05/screencast-beginning-with-cucumber/</link>
		<comments>http://www.natontesting.com/2009/11/05/screencast-beginning-with-cucumber/#comments</comments>
		<pubDate>Thu, 05 Nov 2009 19:06:57 +0000</pubDate>
		<dc:creator>Nat</dc:creator>
				<category><![CDATA[Automated Testing]]></category>
		<category><![CDATA[Links]]></category>
		<category><![CDATA[Test::Unit]]></category>
		<category><![CDATA[WATIR]]></category>
		<category><![CDATA[cucumber]]></category>
		<category><![CDATA[Ruby]]></category>

		<guid isPermaLink="false">http://www.natontesting.com/?p=573</guid>
		<description><![CDATA[We have close to 1,000 watir tests that we&#8217;re beginning to migrate from test/unit to cucumber. The &#8220;Beginning with Cucumber&#8221; Railscast is a great introduction to how cucumber works &#8211; it&#8217;s quite rails-centric, but you&#8217;ll get the idea. Bookmark to:]]></description>
		<wfw:commentRss>http://www.natontesting.com/2009/11/05/screencast-beginning-with-cucumber/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Find duplicate test names in ruby test::unit files</title>
		<link>http://www.natontesting.com/2009/10/03/find-duplicate-test-names-in-ruby-testunit-files/</link>
		<comments>http://www.natontesting.com/2009/10/03/find-duplicate-test-names-in-ruby-testunit-files/#comments</comments>
		<pubDate>Sat, 03 Oct 2009 08:58:07 +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[Ruby]]></category>
		<category><![CDATA[Test Management]]></category>
		<category><![CDATA[Test::Unit]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[Test Case Management]]></category>

		<guid isPermaLink="false">http://www.natontesting.com/?p=558</guid>
		<description><![CDATA[I&#8217;ve recently found a couple of instances of tests with the same test name in the same test::unit TestCase class. This is a bad thing, because the when the ruby interpreter reads the file in, it will ignore all methods &#8230; <a href="http://www.natontesting.com/2009/10/03/find-duplicate-test-names-in-ruby-testunit-files/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.natontesting.com/2009/10/03/find-duplicate-test-names-in-ruby-testunit-files/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Quick and easy Watir test suites with Test::Unit</title>
		<link>http://www.natontesting.com/2009/09/24/quick-and-easy-watir-test-suites-with-testunit/</link>
		<comments>http://www.natontesting.com/2009/09/24/quick-and-easy-watir-test-suites-with-testunit/#comments</comments>
		<pubDate>Thu, 24 Sep 2009 22:20:59 +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[Ruby]]></category>
		<category><![CDATA[Test Management]]></category>
		<category><![CDATA[Test::Unit]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[WATIR]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[agile testing]]></category>
		<category><![CDATA[Firewatir]]></category>
		<category><![CDATA[Test Case Management]]></category>

		<guid isPermaLink="false">http://www.natontesting.com/?p=484</guid>
		<description><![CDATA[A test team usually has a need for a few fixed test suites, eg: a sanity suite or a suite which contains all tests for a full run. There&#8217;s usually also a need to be able to create suites with &#8230; <a href="http://www.natontesting.com/2009/09/24/quick-and-easy-watir-test-suites-with-testunit/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.natontesting.com/2009/09/24/quick-and-easy-watir-test-suites-with-testunit/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>6</slash:comments>
		</item>
	</channel>
</rss>
