<?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"
	>
<channel>
	<title>Comments on: Article: Introducing Behaviour-Driven Development</title>
	<atom:link href="http://dannorth.net/2006/10/article-introducing-behaviour-driven-development/feed" rel="self" type="application/rss+xml" />
	<link>http://dannorth.net/2006/10/article-introducing-behaviour-driven-development</link>
	<description>It's all behaviour</description>
	<pubDate>Sat, 11 Oct 2008 19:08:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Kerry Buckley - Random musings on life, work and software development. &#187; Testing java code using rspec and jruby</title>
		<link>http://dannorth.net/2006/10/article-introducing-behaviour-driven-development#comment-1734</link>
		<dc:creator>Kerry Buckley - Random musings on life, work and software development. &#187; Testing java code using rspec and jruby</dc:creator>
		<pubDate>Thu, 21 Dec 2006 13:45:12 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/archives/31#comment-1734</guid>
		<description>[...] A couple of months ago, Dan North made this comment on the subject of rspec: I’m a big fan of Ruby, and I like some of the ideas behind rspec. However I’ve been working with Niclas Nilsson on a Ruby port of JBehave called RBehave, which we think conveys the intent of BDD more clearly. [...]</description>
		<content:encoded><![CDATA[<p>[...] A couple of months ago, Dan North made this comment on the subject of rspec: I’m a big fan of Ruby, and I like some of the ideas behind rspec. However I’ve been working with Niclas Nilsson on a Ruby port of JBehave called RBehave, which we think conveys the intent of BDD more clearly. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: When Done means Done - Acceptance Testing using Behaviour Driven Development. at Al Power</title>
		<link>http://dannorth.net/2006/10/article-introducing-behaviour-driven-development#comment-1100</link>
		<dc:creator>When Done means Done - Acceptance Testing using Behaviour Driven Development. at Al Power</dc:creator>
		<pubDate>Tue, 05 Dec 2006 03:59:52 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/archives/31#comment-1100</guid>
		<description>[...] Dan showed an example of writing an acceptance test using JBehave (his replacement for JUnit which removed any reference to testing and replaced it with a vocabulary built around verifying behaviour - Behaviour Driven Development). This was something like (roughly from memory - pretty much made up so any errors are mine!): [...]</description>
		<content:encoded><![CDATA[<p>[...] Dan showed an example of writing an acceptance test using JBehave (his replacement for JUnit which removed any reference to testing and replaced it with a vocabulary built around verifying behaviour &#8211; Behaviour Driven Development). This was something like (roughly from memory &#8211; pretty much made up so any errors are mine!): [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AI3 - Adaptive Information:::</title>
		<link>http://dannorth.net/2006/10/article-introducing-behaviour-driven-development#comment-827</link>
		<dc:creator>AI3 - Adaptive Information:::</dc:creator>
		<pubDate>Fri, 17 Nov 2006 16:41:24 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/archives/31#comment-827</guid>
		<description>Behavior-driven Development (BDD)...

Getting the Words Right
There has been some laudable progress in test-driven development (TDD), leading to what is now being touted as &#8220;behaviour-driven development&#8221; (note the English spelling).  Two key proponents of this approach have bee...</description>
		<content:encoded><![CDATA[<p>Behavior-driven Development (BDD)...</p>
<p>Getting the Words Right<br />
There has been some laudable progress in test-driven development (TDD), leading to what is now being touted as &#8220;behaviour-driven development&#8221; (note the English spelling).  Two key proponents of this approach have bee&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan North</title>
		<link>http://dannorth.net/2006/10/article-introducing-behaviour-driven-development#comment-426</link>
		<dc:creator>Dan North</dc:creator>
		<pubDate>Sat, 21 Oct 2006 12:15:23 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/archives/31#comment-426</guid>
		<description>JBehave is back under active development, with a small team of committers (rather than just me). You can expect to see some point releases in the next few weeks.

I'm a big fan of Ruby, and I like some of the ideas behind rspec. However I've been working with "Niclas Nilsson":http://niclasnilsson.se on a Ruby port of JBehave called RBehave, which we think conveys the intent of BDD more clearly.</description>
		<content:encoded><![CDATA[<p>JBehave is back under active development, with a small team of committers (rather than just me). You can expect to see some point releases in the next few weeks.</p>
<p>I&#8217;m a big fan of Ruby, and I like some of the ideas behind rspec. However I&#8217;ve been working with <a href="http://niclasnilsson.se">Niclas Nilsson</a> on a Ruby port of JBehave called RBehave, which we think conveys the intent of BDD more clearly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kerry Buckley</title>
		<link>http://dannorth.net/2006/10/article-introducing-behaviour-driven-development#comment-416</link>
		<dc:creator>Kerry Buckley</dc:creator>
		<pubDate>Fri, 20 Oct 2006 18:48:35 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/archives/31#comment-416</guid>
		<description>Thanks for making the article available - it appeared in the issue of Better Software just before I subscribed, and I'd been looking for it online. Is JBehave still under active development, or have the cool kids all jumped ship to Ruby and the excellent rspec?

Incidentally, I came up with an alternative approach to AgileDox which (IMO) produces more usable output if you have a large class hierarchy:

http://www.kerrybuckley.com/2006/09/25/an-alternative-approach-to-creating-specs-from-junit-tests/</description>
		<content:encoded><![CDATA[<p>Thanks for making the article available &#8211; it appeared in the issue of Better Software just before I subscribed, and I&#8217;d been looking for it online. Is JBehave still under active development, or have the cool kids all jumped ship to Ruby and the excellent rspec?</p>
<p>Incidentally, I came up with an alternative approach to AgileDox which (IMO) produces more usable output if you have a large class hierarchy:</p>
<p><a href="http://www.kerrybuckley.com/2006/09/25/an-alternative-approach-to-creating-specs-from-junit-tests/" rel="nofollow">http://www.kerrybuckley.com/2006/09/25/an-alternative-approach-to-creating-specs-from-junit-tests/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
