<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: How to implement loops in FitNesse test fixtures</title>
	<atom:link href="http://gojko.net/2009/03/09/how-to-implement-loops-in-fitnesse-test-fixtures/feed/" rel="self" type="application/rss+xml" />
	<link>http://gojko.net/2009/03/09/how-to-implement-loops-in-fitnesse-test-fixtures/</link>
	<description>Building software that matters</description>
	<lastBuildDate>Sat, 31 Jul 2010 09:50:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Lisa Crispin</title>
		<link>http://gojko.net/2009/03/09/how-to-implement-loops-in-fitnesse-test-fixtures/comment-page-1/#comment-41904</link>
		<dc:creator>Lisa Crispin</dc:creator>
		<pubDate>Mon, 09 Mar 2009 19:58:21 +0000</pubDate>
		<guid isPermaLink="false">http://gojko.net/?p=722#comment-41904</guid>
		<description>Great post! Takes me back to my first agile project. I was so used to programming these robust, data-driven test scripts. It was the Canoo WebTest developers who first made the case to me that tests should be specified, not programmed. Shortly after that I realized the power of FitNesse as a collaborative tool to turn examples into executable, yet still readable, tests. Now we have many tools that allow this approach.

A side point: just because you could code complex logic into test scripts, doesn&#039;t mean you should. Our GUI regression test scripts have little logic other than the occasional &#039;if&#039;, and they have found regression bugs right away for years now. Our FitNesse tests find regression bugs less often, but their power is in coding the right thing to start with.</description>
		<content:encoded><![CDATA[<p>Great post! Takes me back to my first agile project. I was so used to programming these robust, data-driven test scripts. It was the Canoo WebTest developers who first made the case to me that tests should be specified, not programmed. Shortly after that I realized the power of FitNesse as a collaborative tool to turn examples into executable, yet still readable, tests. Now we have many tools that allow this approach.</p>
<p>A side point: just because you could code complex logic into test scripts, doesn&#8217;t mean you should. Our GUI regression test scripts have little logic other than the occasional &#8216;if&#8217;, and they have found regression bugs right away for years now. Our FitNesse tests find regression bugs less often, but their power is in coding the right thing to start with.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gilles</title>
		<link>http://gojko.net/2009/03/09/how-to-implement-loops-in-fitnesse-test-fixtures/comment-page-1/#comment-41876</link>
		<dc:creator>Gilles</dc:creator>
		<pubDate>Mon, 09 Mar 2009 12:24:01 +0000</pubDate>
		<guid isPermaLink="false">http://gojko.net/?p=722#comment-41876</guid>
		<description>So true! It&#039;s going to be a long trip to get people forget years of scripted test automation and go for tests that reveal user&#039;s intention and not procedural actions and detailed algorithms. Good post.</description>
		<content:encoded><![CDATA[<p>So true! It&#8217;s going to be a long trip to get people forget years of scripted test automation and go for tests that reveal user&#8217;s intention and not procedural actions and detailed algorithms. Good post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Markus Gärtner</title>
		<link>http://gojko.net/2009/03/09/how-to-implement-loops-in-fitnesse-test-fixtures/comment-page-1/#comment-41868</link>
		<dc:creator>Markus Gärtner</dc:creator>
		<pubDate>Mon, 09 Mar 2009 10:32:46 +0000</pubDate>
		<guid isPermaLink="false">http://gojko.net/?p=722#comment-41868</guid>
		<description>This one reminds me on a picture on the solid principles, I just saw lately: http://www.lostechies.com/cfs-filesystemfile.ashx/__key/CommunityServer.Blogs.Components.WeblogFiles/derickbailey/SingleResponsibilityPrinciple2_5F00_71060858.jpg

Just because you can use FitNesse for every stuff, doesn’t mean you should.</description>
		<content:encoded><![CDATA[<p>This one reminds me on a picture on the solid principles, I just saw lately: <a href="http://www.lostechies.com/cfs-filesystemfile.ashx/__key/CommunityServer.Blogs.Components.WeblogFiles/derickbailey/SingleResponsibilityPrinciple2_5F00_71060858.jpg" rel="nofollow">http://www.lostechies.com/cfs-filesystemfile.ashx/__key/CommunityServer.Blogs.Components.WeblogFiles/derickbailey/SingleResponsibilityPrinciple2_5F00_71060858.jpg</a></p>
<p>Just because you can use FitNesse for every stuff, doesn’t mean you should.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
