<?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 Management</title>
	<atom:link href="http://www.natontesting.com/category/management/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>Programmatically take screenshot in IronRuby</title>
		<link>http://www.natontesting.com/2010/06/02/programmatically-take-screenshot-in-ironruby/</link>
		<comments>http://www.natontesting.com/2010/06/02/programmatically-take-screenshot-in-ironruby/#comments</comments>
		<pubDate>Wed, 02 Jun 2010 22:53:41 +0000</pubDate>
		<dc:creator>Nat</dc:creator>
				<category><![CDATA[Example Code]]></category>
		<category><![CDATA[IronRuby]]></category>
		<category><![CDATA[Test Management]]></category>
		<category><![CDATA[Ruby]]></category>
		<category><![CDATA[Test Case Management]]></category>
		<category><![CDATA[Tools]]></category>

		<guid isPermaLink="false">http://www.natontesting.com/?p=941</guid>
		<description><![CDATA[After figuring out how to take a screenshot using .Net, I translated the C# I came up with to IronRuby. Now, when any of my IronRuby-powered tests fail, I take a screenshot &#8211; saves loads of time when trying to &#8230; <a href="http://www.natontesting.com/2010/06/02/programmatically-take-screenshot-in-ironruby/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.natontesting.com/2010/06/02/programmatically-take-screenshot-in-ironruby/feed/</wfw:commentRss>
		<slash:comments>2</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>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>Finding the balance between hacky and over-engineered UI test automation frameworks</title>
		<link>http://www.natontesting.com/2009/09/04/finding-the-balance-between-hacky-and-over-engineered-ui-test-automation-frameworks/</link>
		<comments>http://www.natontesting.com/2009/09/04/finding-the-balance-between-hacky-and-over-engineered-ui-test-automation-frameworks/#comments</comments>
		<pubDate>Sat, 05 Sep 2009 00:18:54 +0000</pubDate>
		<dc:creator>Nat</dc:creator>
				<category><![CDATA[Automated Testing]]></category>
		<category><![CDATA[General Testing Stuff]]></category>
		<category><![CDATA[Mistakes]]></category>
		<category><![CDATA[Test Management]]></category>
		<category><![CDATA[Testing Theory]]></category>
		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false">http://www.natontesting.com/?p=395</guid>
		<description><![CDATA[There are very few real requirements for a UI test automation framework: It should provide accurate test results It should provide accurate test results every time you ask it for results It should make it easy to write tests It &#8230; <a href="http://www.natontesting.com/2009/09/04/finding-the-balance-between-hacky-and-over-engineered-ui-test-automation-frameworks/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.natontesting.com/2009/09/04/finding-the-balance-between-hacky-and-over-engineered-ui-test-automation-frameworks/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>How to print test names when executing Ruby Test::Unit tests</title>
		<link>http://www.natontesting.com/2009/08/05/how-to-print-test-names-when-executing-ruby-testunit-tests/</link>
		<comments>http://www.natontesting.com/2009/08/05/how-to-print-test-names-when-executing-ruby-testunit-tests/#comments</comments>
		<pubDate>Wed, 05 Aug 2009 19:37:12 +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 Management]]></category>
		<category><![CDATA[Test::Unit]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[QA]]></category>
		<category><![CDATA[Test Case Management]]></category>

		<guid isPermaLink="false">http://www.natontesting.com/?p=237</guid>
		<description><![CDATA[When I run my test_all.rb from the command line, I get &#8216;.&#8217; when a test passes, but I don&#8217;t know which test it was that passed. I only get the names of tests that fail or error. Quite sensible &#8211; &#8230; <a href="http://www.natontesting.com/2009/08/05/how-to-print-test-names-when-executing-ruby-testunit-tests/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.natontesting.com/2009/08/05/how-to-print-test-names-when-executing-ruby-testunit-tests/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Test Case Interdependency</title>
		<link>http://www.natontesting.com/2007/07/12/test-case-interdependency/</link>
		<comments>http://www.natontesting.com/2007/07/12/test-case-interdependency/#comments</comments>
		<pubDate>Thu, 12 Jul 2007 10:43:22 +0000</pubDate>
		<dc:creator>Nat</dc:creator>
				<category><![CDATA[Automated Testing]]></category>
		<category><![CDATA[Manual Testing]]></category>
		<category><![CDATA[Mistakes]]></category>
		<category><![CDATA[Test Management]]></category>
		<category><![CDATA[Testing Theory]]></category>
		<category><![CDATA[Test Case Management]]></category>

		<guid isPermaLink="false">http://www.natontesting.com/2007/07/12/test-case-interdependency/</guid>
		<description><![CDATA[One of the most common ways of structuring a series of test cases is to make one test case dependent on the outcome of another. For example, Test Case &#8216;A&#8217; verifies the functionality surrounding the ability to create an account. &#8230; <a href="http://www.natontesting.com/2007/07/12/test-case-interdependency/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.natontesting.com/2007/07/12/test-case-interdependency/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
