<?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: Anatomy of a good acceptance test</title>
	<atom:link href="http://gojko.net/2010/06/16/anatomy-of-a-good-acceptance-test/feed/" rel="self" type="application/rss+xml" />
	<link>http://gojko.net/2010/06/16/anatomy-of-a-good-acceptance-test/</link>
	<description>Building software that matters</description>
	<lastBuildDate>Thu, 02 Feb 2012 07:12:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Iterative Development, Manual Testing and Frustrations &#171; Managing Software Development</title>
		<link>http://gojko.net/2010/06/16/anatomy-of-a-good-acceptance-test/comment-page-1/#comment-105807</link>
		<dc:creator>Iterative Development, Manual Testing and Frustrations &#171; Managing Software Development</dc:creator>
		<pubDate>Sun, 07 Nov 2010 12:31:30 +0000</pubDate>
		<guid isPermaLink="false">http://gojko.net/?p=1891#comment-105807</guid>
		<description>[...] Adzic, in his post Anatomy of good acceptance test says, in order to be effective as live specification, acceptance tests have to be written in a way [...]</description>
		<content:encoded><![CDATA[<p>[...] Adzic, in his post Anatomy of good acceptance test says, in order to be effective as live specification, acceptance tests have to be written in a way [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: blog.codecentric.de</title>
		<link>http://gojko.net/2010/06/16/anatomy-of-a-good-acceptance-test/comment-page-1/#comment-95927</link>
		<dc:creator>blog.codecentric.de</dc:creator>
		<pubDate>Wed, 28 Jul 2010 21:11:52 +0000</pubDate>
		<guid isPermaLink="false">http://gojko.net/?p=1891#comment-95927</guid>
		<description>&lt;strong&gt;How to Structure a Scalable And Maintainable Acceptance Test Suite...&lt;/strong&gt;

You started to write automated acceptance tests, so that you don&#8217;t need to retest all the results from earlier sprints at the end of every sprint. Greate, we too. After a while of successful test automation, tests start to look like a big ball of...</description>
		<content:encoded><![CDATA[<p><strong>How to Structure a Scalable And Maintainable Acceptance Test Suite&#8230;</strong></p>
<p>You started to write automated acceptance tests, so that you don&#8217;t need to retest all the results from earlier sprints at the end of every sprint. Greate, we too. After a while of successful test automation, tests start to look like a big ball of&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ParkCalc automation – Refactoring a data-driven test : Clevertester</title>
		<link>http://gojko.net/2010/06/16/anatomy-of-a-good-acceptance-test/comment-page-1/#comment-92381</link>
		<dc:creator>ParkCalc automation – Refactoring a data-driven test : Clevertester</dc:creator>
		<pubDate>Tue, 29 Jun 2010 20:01:12 +0000</pubDate>
		<guid isPermaLink="false">http://gojko.net/?p=1891#comment-92381</guid>
		<description>[...] he describes a layered approach to software test automation in a very well manner. Together with Gojko’s anatomy of a good acceptance test this gives us some picture where we should be [...]</description>
		<content:encoded><![CDATA[<p>[...] he describes a layered approach to software test automation in a very well manner. Together with Gojko’s anatomy of a good acceptance test this gives us some picture where we should be [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Andersen</title>
		<link>http://gojko.net/2010/06/16/anatomy-of-a-good-acceptance-test/comment-page-1/#comment-91407</link>
		<dc:creator>Tim Andersen</dc:creator>
		<pubDate>Mon, 21 Jun 2010 20:12:28 +0000</pubDate>
		<guid isPermaLink="false">http://gojko.net/?p=1891#comment-91407</guid>
		<description>Great post Gojko!  I really like how you described the pitfalls of the original test and demonstrated a better way.

I find the given/when/then language adds clarity by making obvious what is an input and what is an expectation.  This might be the current fad, but here is a semantic alternative.

&#124;Given&#124;Employees&#124;
&#124;name&#124;address&#124;salary&#124;
&#124;Jeff Languid&#124;10 Adamant St; Laurel, MD 20707&#124;1005.00&#124;
&#124;Kelp Holland&#124;12B Baker St; Cottonmouth, IL 60066&#124;2000.00&#124;

&#124;When&#124;Payroll Runs&#124;
&#124;on&#124;10/15/2010&#124;
&#124;with next check number&#124;1000&#124;

&#124;Then&#124;Printed Cheques&#124;
&#124;cheque number&#124;cheque date&#124;payee&#124;address&#124;amount&#124;
&#124;1000&#124;10/15/2010&#124;Jeff Languid&#124;10 Adamant St; Laurel, MD 20707&#124;1005.00&#124;
&#124;1001&#124;10/15/2010&#124;Kelp Holland&#124;12B Baker St; Cottonmouth, IL 60066&#124;2000.00&#124;</description>
		<content:encoded><![CDATA[<p>Great post Gojko!  I really like how you described the pitfalls of the original test and demonstrated a better way.</p>
<p>I find the given/when/then language adds clarity by making obvious what is an input and what is an expectation.  This might be the current fad, but here is a semantic alternative.</p>
<p>|Given|Employees|<br />
|name|address|salary|<br />
|Jeff Languid|10 Adamant St; Laurel, MD 20707|1005.00|<br />
|Kelp Holland|12B Baker St; Cottonmouth, IL 60066|2000.00|</p>
<p>|When|Payroll Runs|<br />
|on|10/15/2010|<br />
|with next check number|1000|</p>
<p>|Then|Printed Cheques|<br />
|cheque number|cheque date|payee|address|amount|<br />
|1000|10/15/2010|Jeff Languid|10 Adamant St; Laurel, MD 20707|1005.00|<br />
|1001|10/15/2010|Kelp Holland|12B Baker St; Cottonmouth, IL 60066|2000.00|</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://gojko.net/2010/06/16/anatomy-of-a-good-acceptance-test/comment-page-1/#comment-91262</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Mon, 21 Jun 2010 18:49:30 +0000</pubDate>
		<guid isPermaLink="false">http://gojko.net/?p=1891#comment-91262</guid>
		<description>[...] week Gojko Adzic wrote about the anatomy of a good acceptance test. After having read his elaboration, I remembered how I came up with the preparation for the EWT19 [...]</description>
		<content:encoded><![CDATA[<p>[...] week Gojko Adzic wrote about the anatomy of a good acceptance test. After having read his elaboration, I remembered how I came up with the preparation for the EWT19 [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

