<?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: Automating Story Tests</title>
	<atom:link href="http://xprogramming.com/blog/automating-story-tests/feed/" rel="self" type="application/rss+xml" />
	<link>http://xprogramming.com/blog/automating-story-tests/</link>
	<description>an agile software development resource</description>
	<lastBuildDate>Tue, 11 Oct 2011 17:33:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Ron Jeffries</title>
		<link>http://xprogramming.com/blog/automating-story-tests/#comment-99</link>
		<dc:creator>Ron Jeffries</dc:creator>
		<pubDate>Thu, 28 May 2009 09:46:04 +0000</pubDate>
		<guid isPermaLink="false">http://xprogramming.com/?p=1010#comment-99</guid>
		<description>GeePawHill: Certainly if there are no storytests, the rule &quot;all storytests must be automated&quot; is not broken. I wonder, though, how one knows that the whole system works using only microtests. I hope you&#039;ll write about that real soon now.

fkchang: Yes. If storytests are inexpensive enough, they&#039;ll be automated more often. (My point exactly. :) ) Since essentially every storytest will need to be run at least twice, the only excuse we have is that they are too expensive, i.e. we&#039;re not good enough at it yet. Tools like Cucumber can help with that.</description>
		<content:encoded><![CDATA[<p>GeePawHill: Certainly if there are no storytests, the rule &#8220;all storytests must be automated&#8221; is not broken. I wonder, though, how one knows that the whole system works using only microtests. I hope you&#8217;ll write about that real soon now.</p>
<p>fkchang: Yes. If storytests are inexpensive enough, they&#8217;ll be automated more often. (My point exactly. :) ) Since essentially every storytest will need to be run at least twice, the only excuse we have is that they are too expensive, i.e. we&#8217;re not good enough at it yet. Tools like Cucumber can help with that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fkchang</title>
		<link>http://xprogramming.com/blog/automating-story-tests/#comment-98</link>
		<dc:creator>fkchang</dc:creator>
		<pubDate>Thu, 28 May 2009 06:39:06 +0000</pubDate>
		<guid isPermaLink="false">http://xprogramming.com/?p=1010#comment-98</guid>
		<description>On the other hand, if it were easier to write story tests, there might be less resistance.  I&#039;ve had good success with Cucumber, to the point where the COO declared all requirements would be written in Gherkin (the cucumber language, basically executable given when thens and in our case, mostly As as, I would, So that&#039;s for context, some feature injection templates in that case).  Long story short, the requirements as stories come down as ready to be automated w/some work from the team.</description>
		<content:encoded><![CDATA[<p>On the other hand, if it were easier to write story tests, there might be less resistance.  I&#8217;ve had good success with Cucumber, to the point where the COO declared all requirements would be written in Gherkin (the cucumber language, basically executable given when thens and in our case, mostly As as, I would, So that&#8217;s for context, some feature injection templates in that case).  Long story short, the requirements as stories come down as ready to be automated w/some work from the team.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GeePawHill</title>
		<link>http://xprogramming.com/blog/automating-story-tests/#comment-97</link>
		<dc:creator>GeePawHill</dc:creator>
		<pubDate>Thu, 28 May 2009 05:10:49 +0000</pubDate>
		<guid isPermaLink="false">http://xprogramming.com/?p=1010#comment-97</guid>
		<description>I&#039;ve had systems ship in a pleasing manner that had only microtests, no storytests at all.  Essentially, the team served almost entirely as its own customer, and they could write faster and better tests using JUnit.  I&#039;m not sure what this means, if anything, in the light of your post.  Bash me at will.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve had systems ship in a pleasing manner that had only microtests, no storytests at all.  Essentially, the team served almost entirely as its own customer, and they could write faster and better tests using JUnit.  I&#8217;m not sure what this means, if anything, in the light of your post.  Bash me at will.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: brettschuchert</title>
		<link>http://xprogramming.com/blog/automating-story-tests/#comment-96</link>
		<dc:creator>brettschuchert</dc:creator>
		<pubDate>Thu, 28 May 2009 03:11:03 +0000</pubDate>
		<guid isPermaLink="false">http://xprogramming.com/?p=1010#comment-96</guid>
		<description>Well I&#039;ll just chime in here and agree.

I can think of another reason automation is hard. The &quot;story&quot; is too big and so figuring out an example is difficult. If this is a problem, then the solution is to break it down until you can describe a part of what it is you&#039;re trying to do. I&#039;d still want a story to &quot;slice the cake&quot; but if the choice is between a large story hard to describe but one that &quot;slices the cake&quot; or a series of smaller stories that don&#039;t &quot;slice the cake&quot; but can be described, I suppose that&#039;s OK. It should be the exception, however, and not the rule.</description>
		<content:encoded><![CDATA[<p>Well I&#8217;ll just chime in here and agree.</p>
<p>I can think of another reason automation is hard. The &#8220;story&#8221; is too big and so figuring out an example is difficult. If this is a problem, then the solution is to break it down until you can describe a part of what it is you&#8217;re trying to do. I&#8217;d still want a story to &#8220;slice the cake&#8221; but if the choice is between a large story hard to describe but one that &#8220;slices the cake&#8221; or a series of smaller stories that don&#8217;t &#8220;slice the cake&#8221; but can be described, I suppose that&#8217;s OK. It should be the exception, however, and not the rule.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

