<?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/"
	>

<channel>
	<title>Brent Sordyl's blog &#187; tdd</title>
	<atom:link href="http://www.sordyl.info/tag/tdd/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sordyl.info</link>
	<description>Daily links to e-Learning and Web Technology resources</description>
	<lastBuildDate>Thu, 09 Sep 2010 17:00:02 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>(My) RSpec best practices and tips &#124; EggsOnBread</title>
		<link>http://www.sordyl.info/2010/03/29/links4/</link>
		<comments>http://www.sordyl.info/2010/03/29/links4/#comments</comments>
		<pubDate>Mon, 29 Mar 2010 14:00:02 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[rspec]]></category>
		<category><![CDATA[ruby]]></category>
		<category><![CDATA[tdd]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[
After a year using RSpec, I’m happy to share “(My) RSpec Best Practices and Tips”. Let’s make your specs easier to maintain, less verbose, more structured and covering more cases!
Use shortcuts specify {}, it {} and subject {}
(Link: (My) RSpec best practices and tips &#124; EggsOnBread)
]]></description>
			<content:encoded><![CDATA[<p>
After a year using RSpec, I’m happy to share “(My) RSpec Best Practices and Tips”. Let’s make your specs easier to maintain, less verbose, more structured and covering more cases!</p>
<p>Use shortcuts specify {}, it {} and subject {}<br />
(Link: <a class="deliciouslink" href="http://eggsonbread.com/2010/03/28/my-rspec-best-practices-and-tips/" title="(My) RSpec best practices and tips | EggsOnBread" target="_blank">(My) RSpec best practices and tips | EggsOnBread</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2010/03/29/links4/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Concordion is an open source tool for writing automated acceptance tests in Java*</title>
		<link>http://www.sordyl.info/2010/03/24/links1/</link>
		<comments>http://www.sordyl.info/2010/03/24/links1/#comments</comments>
		<pubDate>Wed, 24 Mar 2010 22:00:02 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[agile]]></category>
		<category><![CDATA[tdd]]></category>
		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[
*
      Powerful, yet simple to use Concordion integrates directly with JUnit.
    *
      Highly readable tests Concordion acceptance tests are so readable they can double up as system documentation. And, since the tests are linked to the system, you know the documentation is [...]]]></description>
			<content:encoded><![CDATA[<p>
*</p>
<p>      Powerful, yet simple to use Concordion integrates directly with JUnit.<br />
    *</p>
<p>      Highly readable tests Concordion acceptance tests are so readable they can double up as system documentation. And, since the tests are linked to the system, you know the documentation is always up-to-date.<br />
    *</p>
<p>      Separates tests from implementation Tests that include a lot of implementation detail lock you into that implementation. Concordion helps you to document the logic and behaviour of your system in a way that does not lock you in.<br />
(Link: <a class="deliciouslink" href="http://www.concordion.org/" title="Concordion is an open source tool for writing automated acceptance tests in Java*" target="_blank">Concordion is an open source tool for writing automated acceptance tests in Java*</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2010/03/24/links1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>My top 7 RSpec best practices &#124; Dmytro Shteflyuk&#8217;s Home</title>
		<link>http://www.sordyl.info/2009/11/29/links1/</link>
		<comments>http://www.sordyl.info/2009/11/29/links1/#comments</comments>
		<pubDate>Sun, 29 Nov 2009 21:00:03 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[bdd]]></category>
		<category><![CDATA[rspec]]></category>
		<category><![CDATA[tdd]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[
I use RSpec in all my projects. It’s really hard to overemphasize how helpful it is and how much easier becomes your life if you have good specs coverage. But its outstanding flexibility enables many ways to make your specs awful: horribly slow, over-bloated, even non-readable sometimes. I do not want to teach you BDD [...]]]></description>
			<content:encoded><![CDATA[<p>
I use RSpec in all my projects. It’s really hard to overemphasize how helpful it is and how much easier becomes your life if you have good specs coverage. But its outstanding flexibility enables many ways to make your specs awful: horribly slow, over-bloated, even non-readable sometimes. I do not want to teach you BDD and RSpec here, but instead I will give you some ideas how to improve your specs quality and increase efficiency of your BDD workflow.<br />
(Link: <a class="deliciouslink" href="http://kpumuk.info/ruby-on-rails/my-top-7-rspec-best-practices/" title="My top 7 RSpec best practices | Dmytro Shteflyuk's Home" target="_blank">My top 7 RSpec best practices | Dmytro Shteflyuk&#8217;s Home</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2009/11/29/links1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SD Ruby &#8211; Episode 066: Unit Testing: The Easy Way</title>
		<link>http://www.sordyl.info/2009/11/22/links4/</link>
		<comments>http://www.sordyl.info/2009/11/22/links4/#comments</comments>
		<pubDate>Sun, 22 Nov 2009 23:00:04 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[ruby]]></category>
		<category><![CDATA[tdd]]></category>
		<category><![CDATA[unittesting]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[
With Rspec and Cucumber, Ruby has brought testing to a whole new level, but tests still require a lot of work.
But things just got better. Llewellyn Falco will show you new patterns and practices to dramatically decrease the amount of effort needed to test.
(Link: SD Ruby &#8211; Episode 066: Unit Testing: The Easy Way)
]]></description>
			<content:encoded><![CDATA[<p>
With Rspec and Cucumber, Ruby has brought testing to a whole new level, but tests still require a lot of work.</p>
<p>But things just got better. Llewellyn Falco will show you new patterns and practices to dramatically decrease the amount of effort needed to test.<br />
(Link: <a class="deliciouslink" href="http://sdruby.org/podcast/66?utm_source=feedburner&#038;utm_medium=feed&#038;utm_campaign=Feed%3A+rubytube+%28RubyTu.be+-+Recently+Added%29&#038;utm_content=Google+Reader" title="SD Ruby - Episode 066: Unit Testing: The Easy Way" target="_blank">SD Ruby &#8211; Episode 066: Unit Testing: The Easy Way</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2009/11/22/links4/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Textmate Bundle for Webrat</title>
		<link>http://www.sordyl.info/2009/09/16/links2/</link>
		<comments>http://www.sordyl.info/2009/09/16/links2/#comments</comments>
		<pubDate>Wed, 16 Sep 2009 15:00:03 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[rubyonrails]]></category>
		<category><![CDATA[tdd]]></category>
		<category><![CDATA[webrat]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[
Textmate Bundle for Webrat Just a simple collection of snippets. The snippets are intended to be used by people using the RSPec Story bundle and/or the Cucumber bundle.
(Link: Textmate Bundle for Webrat)
]]></description>
			<content:encoded><![CDATA[<p>
Textmate Bundle for Webrat Just a simple collection of snippets. The snippets are intended to be used by people using the RSPec Story bundle and/or the Cucumber bundle.<br />
(Link: <a class="deliciouslink" href="http://github.com/bmabey/webrat-tmbundle/" title="Textmate Bundle for Webrat" target="_blank">Textmate Bundle for Webrat</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2009/09/16/links2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Textmate Bundle for Cucumber</title>
		<link>http://www.sordyl.info/2009/09/16/links4/</link>
		<comments>http://www.sordyl.info/2009/09/16/links4/#comments</comments>
		<pubDate>Wed, 16 Sep 2009 15:00:03 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[cucumber]]></category>
		<category><![CDATA[tdd]]></category>
		<category><![CDATA[textmate]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[
This is a fork of the rspec-story-tmbundle.
The goal is to keep the same functionality that the original bundle had but make it compatible with Cucumber and also take advantage of the benefits that Cucumber offers.
So far the basic file switching and syntax highlighting is working. You can also run a feature. (See below.)
File creation and [...]]]></description>
			<content:encoded><![CDATA[<p>
This is a fork of the rspec-story-tmbundle.<br />
The goal is to keep the same functionality that the original bundle had but make it compatible with Cucumber and also take advantage of the benefits that Cucumber offers.</p>
<p>So far the basic file switching and syntax highlighting is working. You can also run a feature. (See below.)<br />
File creation and more advanced step generation commands have not yet been ported fully. Feel free to help out. :)</p>
<p>If you are doing ruby development with webrat you may also want the webrat bundle.<br />
(Link: <a class="deliciouslink" href="http://github.com/bmabey/cucumber-tmbundle" title="Textmate Bundle for Cucumber" target="_blank">Textmate Bundle for Cucumber</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2009/09/16/links4/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Setting up Rspec, Autotest and Growl on Mac OS X</title>
		<link>http://www.sordyl.info/2009/09/12/links2/</link>
		<comments>http://www.sordyl.info/2009/09/12/links2/#comments</comments>
		<pubDate>Sat, 12 Sep 2009 19:00:04 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[bdd]]></category>
		<category><![CDATA[growl]]></category>
		<category><![CDATA[rspec]]></category>
		<category><![CDATA[tdd]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[
p> We have recently decided to use BDD for our upcoming projects. To make testing more fun and efficient I have hook up Growl with ZenTest’s autotest to display test results from Rspec. Some of the following instructions is taken from http://wincent.com/knowledge-base/Setting_up_autotest_to_use_Growl
What follows are the instructions to install the software to setup your own if [...]]]></description>
			<content:encoded><![CDATA[<p>
p> We have recently decided to use BDD for our upcoming projects. To make testing more fun and efficient I have hook up Growl with ZenTest’s autotest to display test results from Rspec. Some of the following instructions is taken from http://wincent.com/knowledge-base/Setting_up_autotest_to_use_Growl</p>
<p>What follows are the instructions to install the software to setup your own if you like to try out.<br />
(Link: <a class="deliciouslink" href="http://spiragram.com/2007/7/22/setting-up-rspec-autotest-and-growl-on-mac-os-x" title="Setting up Rspec, Autotest and Growl on Mac OS X" target="_blank">Setting up Rspec, Autotest and Growl on Mac OS X</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2009/09/12/links2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>BDD Intro &#8211; Powered by Google Docs</title>
		<link>http://www.sordyl.info/2009/09/12/links3/</link>
		<comments>http://www.sordyl.info/2009/09/12/links3/#comments</comments>
		<pubDate>Sat, 12 Sep 2009 19:00:04 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[bdd]]></category>
		<category><![CDATA[tdd]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[
Dave Astels &#8211; A New Look at Test-Driven Development
(Link: BDD Intro &#8211; Powered by Google Docs)
]]></description>
			<content:encoded><![CDATA[<p>
Dave Astels &#8211; A New Look at Test-Driven Development<br />
(Link: <a class="deliciouslink" href="http://docs.google.com/gview?a=v&#038;q=cache:9WomWMVax7kJ:blog.daveastels.com/files/BDD_Intro.pdf+a+new+look+at+test+driven+development+dave+astels&#038;hl=en&#038;gl=us" title="BDD Intro - Powered by Google Docs" target="_blank">BDD Intro &#8211; Powered by Google Docs</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2009/09/12/links3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>15 Expert Tips for Using Cucumber &#124; Engine Yard Blog</title>
		<link>http://www.sordyl.info/2009/08/19/links4/</link>
		<comments>http://www.sordyl.info/2009/08/19/links4/#comments</comments>
		<pubDate>Wed, 19 Aug 2009 12:00:04 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[cucumber]]></category>
		<category><![CDATA[rubyonrails]]></category>
		<category><![CDATA[tdd]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[
I put out calls for ‘Cucumber Best Practices’ and received an assortment of responses—thanks to everyone who contributed! After collecting and reviewing all the responses, I’ve come up with a list of 15 expert tips you want to keep in mind when working with Cucumber.
(Link: 15 Expert Tips for Using Cucumber &#124; Engine Yard Blog)
]]></description>
			<content:encoded><![CDATA[<p>
I put out calls for ‘Cucumber Best Practices’ and received an assortment of responses—thanks to everyone who contributed! After collecting and reviewing all the responses, I’ve come up with a list of 15 expert tips you want to keep in mind when working with Cucumber.<br />
(Link: <a class="deliciouslink" href="http://www.engineyard.com/blog/2009/15-expert-tips-for-using-cucumber/" title="15 Expert Tips for Using Cucumber | Engine Yard Blog" target="_blank">15 Expert Tips for Using Cucumber | Engine Yard Blog</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2009/08/19/links4/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Test-Driven Heresy &#8211; lapses from the TDD are more forgivable the closer you are to the beginning of a project &#8211; Tim Bray</title>
		<link>http://www.sordyl.info/2009/06/24/links2/</link>
		<comments>http://www.sordyl.info/2009/06/24/links2/#comments</comments>
		<pubDate>Wed, 24 Jun 2009 13:00:05 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[programming]]></category>
		<category><![CDATA[tdd]]></category>
		<category><![CDATA[tweet]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[
Sin and Penitence · People introducing TDD do this thing where they start from scratch saying “We’re going to write a class to do X and it’ll need a method to do Y, so let’s write a test for Y”. The problem is, when I’m getting started, I never know what X and Y are. [...]]]></description>
			<content:encoded><![CDATA[<p>
Sin and Penitence · People introducing TDD do this thing where they start from scratch saying “We’re going to write a class to do X and it’ll need a method to do Y, so let’s write a test for Y”. The problem is, when I’m getting started, I never know what X and Y are. I always end up sketching in a few classes and then tearing them up and re-sketching, and after a few iterations I’m starting to have a feeling for X and Y. ¶</p>
<p>And maybe the sketch-and-tear process would be better and more productive if I had the patience to write the tests for each successive hypothesis about X and Y, but I don’t think I ever will. This is partly because the first few tests for the kind of classes I write tend to be expensive; where you have to face the dependency-injection and big-fat-mock problems. I lack the patience to make that investment if I’m unsure the class is basically pointing in the right direction.<br />
(Link: <a class="deliciouslink" href="http://www.tbray.org/ongoing/When/200x/2009/06/23/TDD-Heresy" title="Test-Driven Heresy - lapses from the TDD are more forgivable the closer you are to the beginning of a project - Tim Bray" target="_blank">Test-Driven Heresy &#8211; lapses from the TDD are more forgivable the closer you are to the beginning of a project &#8211; Tim Bray</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2009/06/24/links2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>InfoQ: Recommended TDD Tutorials</title>
		<link>http://www.sordyl.info/2009/05/19/links7/</link>
		<comments>http://www.sordyl.info/2009/05/19/links7/#comments</comments>
		<pubDate>Tue, 19 May 2009 22:00:04 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[bdd]]></category>
		<category><![CDATA[tdd]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[
Recently, Dave Nicolette consolidated a list of recommended TDD tutorials from a discussion on the Extreme Programming group. Here is a sneak peak at the consolidated list with categorization for quickly getting started with Test Driven Development.
(Link: InfoQ: Recommended TDD Tutorials)
]]></description>
			<content:encoded><![CDATA[<p>
Recently, Dave Nicolette consolidated a list of recommended TDD tutorials from a discussion on the Extreme Programming group. Here is a sneak peak at the consolidated list with categorization for quickly getting started with Test Driven Development.<br />
(Link: <a class="deliciouslink" href="http://www.infoq.com/news/2009/05/recommended-tdd-tutorials" title="InfoQ: Recommended TDD Tutorials" target="_blank">InfoQ: Recommended TDD Tutorials</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2009/05/19/links7/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Robby on Rails : 20 articles on Cucumber and a free beverage recipe!</title>
		<link>http://www.sordyl.info/2009/05/03/links2/</link>
		<comments>http://www.sordyl.info/2009/05/03/links2/#comments</comments>
		<pubDate>Sun, 03 May 2009 20:00:04 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[cucumber]]></category>
		<category><![CDATA[ruby]]></category>
		<category><![CDATA[tdd]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[
The Cucumber project describes itself as a suite that, “lets software development teams describe how software should behave in plain text. The text is written in a business-readable domain-specific language and serves as documentation, automated tests and development-aid – all rolled into one format.“
(Link: Robby on Rails : 20 articles on Cucumber and a free [...]]]></description>
			<content:encoded><![CDATA[<p>
The Cucumber project describes itself as a suite that, “lets software development teams describe how software should behave in plain text. The text is written in a business-readable domain-specific language and serves as documentation, automated tests and development-aid – all rolled into one format.“<br />
(Link: <a class="deliciouslink" href="http://www.robbyonrails.com/articles/2009/04/09/20-articles-on-cucumber-and-a-free-beverage-recipe" title="Robby on Rails : 20 articles on Cucumber and a free beverage recipe!" target="_blank">Robby on Rails : 20 articles on Cucumber and a free beverage recipe!</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2009/05/03/links2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Shoulda for RSpec is Remarkable!</title>
		<link>http://www.sordyl.info/2009/05/03/links4/</link>
		<comments>http://www.sordyl.info/2009/05/03/links4/#comments</comments>
		<pubDate>Sun, 03 May 2009 20:00:04 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[remarkable]]></category>
		<category><![CDATA[rspec]]></category>
		<category><![CDATA[ruby]]></category>
		<category><![CDATA[tdd]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[
This project has already reached the first goal, which was to port all Shoulda macros to RSpec. This has been done with great care and attention to detail, and I have tried to write lots of tests. But there is no substitute for using it in real life and finding areas that could use improvement.
(Link: [...]]]></description>
			<content:encoded><![CDATA[<p>
This project has already reached the first goal, which was to port all Shoulda macros to RSpec. This has been done with great care and attention to detail, and I have tried to write lots of tests. But there is no substitute for using it in real life and finding areas that could use improvement.<br />
(Link: <a class="deliciouslink" href="http://www.nomedojogo.com/2008/11/18/shoulda-for-rspec-is-remarkable/" title="Shoulda for RSpec is Remarkable!" target="_blank">Shoulda for RSpec is Remarkable!</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2009/05/03/links4/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using Cucumber to Integrate Distributed Systems and Test Messaging</title>
		<link>http://www.sordyl.info/2009/04/16/links3/</link>
		<comments>http://www.sordyl.info/2009/04/16/links3/#comments</comments>
		<pubDate>Thu, 16 Apr 2009 14:00:05 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[activemq]]></category>
		<category><![CDATA[bdd]]></category>
		<category><![CDATA[cucumber]]></category>
		<category><![CDATA[messaging]]></category>
		<category><![CDATA[rspec]]></category>
		<category><![CDATA[ruby]]></category>
		<category><![CDATA[tdd]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[
One interesting use of Cucumber is to facilitate integration and communication between different systems. At my last job we had several distributed systems that communicated via a messaging broker. It was very important that the messages sent between the different systems be kept in sync and handled appropriately. For example, System A needed to know [...]]]></description>
			<content:encoded><![CDATA[<p>
One interesting use of Cucumber is to facilitate integration and communication between different systems. At my last job we had several distributed systems that communicated via a messaging broker. It was very important that the messages sent between the different systems be kept in sync and handled appropriately. For example, System A needed to know the exact message format and queue that System B was going to be using, and vice versa. This type of integration between systems is very error prone and when something goes awry the problems can be very hard to track down. In order to ensure both systems were on the same page we used the exact same Cucumber feature in both systems but had the step definitions verify different things on the respective systems. In this post I’ll walk through a quick example illustrating the tools and techniques we used to do this.<br />
(Link: <a class="deliciouslink" href="http://www.benmabey.com/2009/02/17/using-cucumber-to-integrate-distributed-systems-and-test-messaging/" title="Using Cucumber to Integrate Distributed Systems and Test Messaging" target="_blank">Using Cucumber to Integrate Distributed Systems and Test Messaging</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2009/04/16/links3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How To Setup RSpec, Cucumber, Webrat, RCov and Autotest on Leopard</title>
		<link>http://www.sordyl.info/2009/04/07/links1/</link>
		<comments>http://www.sordyl.info/2009/04/07/links1/#comments</comments>
		<pubDate>Tue, 07 Apr 2009 14:00:05 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[cucumber]]></category>
		<category><![CDATA[osx]]></category>
		<category><![CDATA[rspec]]></category>
		<category><![CDATA[rubyonrails]]></category>
		<category><![CDATA[tdd]]></category>
		<category><![CDATA[webrat]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[
RSpec, Cucumber, Webrat, RCov and Autotest are a powerful combination of tools for testing your Rails app. Unfortunately getting them to all work nicely together can be a bit of challenge. I recently configured a development environment from scratch on OS X 10.5 Leopard and kept track of all of the little details. (via claytonlz.com)
(Link: [...]]]></description>
			<content:encoded><![CDATA[<p>
RSpec, Cucumber, Webrat, RCov and Autotest are a powerful combination of tools for testing your Rails app. Unfortunately getting them to all work nicely together can be a bit of challenge. I recently configured a development environment from scratch on OS X 10.5 Leopard and kept track of all of the little details. (via claytonlz.com)<br />
(Link: <a class="deliciouslink" href="http://www.claytonlz.com/index.php/2009/04/how-to-setup-rspec-cucumber-webrat-rcov-and-autotest-on-leopard/" title="How To Setup RSpec, Cucumber, Webrat, RCov and Autotest on Leopard" target="_blank">How To Setup RSpec, Cucumber, Webrat, RCov and Autotest on Leopard</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2009/04/07/links1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
