<?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: 15 Expert Tips for Using Cucumber</title>
	<atom:link href="http://www.engineyard.com/blog/2009/15-expert-tips-for-using-cucumber/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.engineyard.com/blog/2009/15-expert-tips-for-using-cucumber/</link>
	<description></description>
	<lastBuildDate>Wed, 08 Feb 2012 12:12:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Karthik</title>
		<link>http://www.engineyard.com/blog/2009/15-expert-tips-for-using-cucumber/comment-page-1/#comment-50530</link>
		<dc:creator>Karthik</dc:creator>
		<pubDate>Sun, 19 Dec 2010 20:41:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.engineyard.com/blog/?p=1460#comment-50530</guid>
		<description>Treat them as if you were reading book. Create meaningful sub-directories based on functionality and club them together.  </description>
		<content:encoded><![CDATA[<p>Treat them as if you were reading book. Create meaningful sub-directories based on functionality and club them together.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: raveendran</title>
		<link>http://www.engineyard.com/blog/2009/15-expert-tips-for-using-cucumber/comment-page-1/#comment-46284</link>
		<dc:creator>raveendran</dc:creator>
		<pubDate>Wed, 29 Sep 2010 09:09:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.engineyard.com/blog/?p=1460#comment-46284</guid>
		<description>Can we able to run 2 different feature files at a time ? -- (Note -- most of the scenario&#039;s common for 2 feature files.) </description>
		<content:encoded><![CDATA[<p>Can we able to run 2 different feature files at a time ? &#8212; (Note &#8212; most of the scenario&#039;s common for 2 feature files.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.engineyard.com/blog/2009/15-expert-tips-for-using-cucumber/comment-page-1/#comment-45235</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Thu, 09 Sep 2010 21:02:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.engineyard.com/blog/?p=1460#comment-45235</guid>
		<description>Anyone have good examples of how to manage a large number of cucumber features?  It seems like once you get 50+ feature files it gets a bit unmanageable... </description>
		<content:encoded><![CDATA[<p>Anyone have good examples of how to manage a large number of cucumber features?  It seems like once you get 50+ feature files it gets a bit unmanageable&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Abhishek Shukla</title>
		<link>http://www.engineyard.com/blog/2009/15-expert-tips-for-using-cucumber/comment-page-1/#comment-40132</link>
		<dc:creator>Abhishek Shukla</dc:creator>
		<pubDate>Thu, 28 Jan 2010 07:29:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.engineyard.com/blog/?p=1460#comment-40132</guid>
		<description>Very useful tips thanks for sharing this really helped me to generate a better scenario. And also I am looking  if you can tell us something on action mailer,  like a scenario where a user will sending a multiple mail along with a body containing a activate link.  
 
 </description>
		<content:encoded><![CDATA[<p>Very useful tips thanks for sharing this really helped me to generate a better scenario. And also I am looking  if you can tell us something on action mailer,  like a scenario where a user will sending a multiple mail along with a body containing a activate link.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Premdas</title>
		<link>http://www.engineyard.com/blog/2009/15-expert-tips-for-using-cucumber/comment-page-1/#comment-30930</link>
		<dc:creator>Andrew Premdas</dc:creator>
		<pubDate>Wed, 21 Oct 2009 11:00:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.engineyard.com/blog/?p=1460#comment-30930</guid>
		<description>Useful tips, have to disagree with #13 though, I think if you do this a bit you will inevitably get carried away! I would say now never call a step from a step, instead extract a method and put it in a step helper. So to use your example 
 
module UserStepHelper 
  def user_creater(name) ... 
  def user_login_in(name) ... 
end 
World(UserStepHelper) 
  
Given /^the user (.*) exists$/ do &#124;name&#124; 
  user_create(name) 
  # ...  perhaps something here to confirm user creation 
end 
 
Given /^I log in as (.*)$/ do &#124;name&#124; 
  user_login_in(name)  
end 
 
Given /^(.*) is logged in$/ do &#124;name&#124; 
  user_create(name) 
  user_login_in(name) 
end 
 
This will save you much time in future when your &quot;do complex operation&quot; feature that requires and admin user and a customer and ... fails. </description>
		<content:encoded><![CDATA[<p>Useful tips, have to disagree with #13 though, I think if you do this a bit you will inevitably get carried away! I would say now never call a step from a step, instead extract a method and put it in a step helper. So to use your example</p>
<p>module UserStepHelper</p>
<p>  def user_creater(name) &#8230;</p>
<p>  def user_login_in(name) &#8230;</p>
<p>end</p>
<p>World(UserStepHelper)</p>
<p>Given /^the user (.*) exists$/ do |name|</p>
<p>  user_create(name)</p>
<p>  # &#8230;  perhaps something here to confirm user creation</p>
<p>end</p>
<p>Given /^I log in as (.*)$/ do |name|</p>
<p>  user_login_in(name) </p>
<p>end</p>
<p>Given /^(.*) is logged in$/ do |name|</p>
<p>  user_create(name)</p>
<p>  user_login_in(name)</p>
<p>end</p>
<p>This will save you much time in future when your &quot;do complex operation&quot; feature that requires and admin user and a customer and &#8230; fails.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cire</title>
		<link>http://www.engineyard.com/blog/2009/15-expert-tips-for-using-cucumber/comment-page-1/#comment-16168</link>
		<dc:creator>cire</dc:creator>
		<pubDate>Mon, 31 Aug 2009 14:20:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.engineyard.com/blog/?p=1460#comment-16168</guid>
		<description>I wonder if this might limit the thoroughness of the testing.  What if the application works great on Fridays, but has a bug when using it on Mondays?  I wonder if Chronic addresses weekends directly. </description>
		<content:encoded><![CDATA[<p>I wonder if this might limit the thoroughness of the testing.  What if the application works great on Fridays, but has a bug when using it on Mondays?  I wonder if Chronic addresses weekends directly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jazzezravi</title>
		<link>http://www.engineyard.com/blog/2009/15-expert-tips-for-using-cucumber/comment-page-1/#comment-15935</link>
		<dc:creator>jazzezravi</dc:creator>
		<pubDate>Sat, 29 Aug 2009 11:04:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.engineyard.com/blog/?p=1460#comment-15935</guid>
		<description>Awesome tips! </description>
		<content:encoded><![CDATA[<p>Awesome tips!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aslak Hellesoy</title>
		<link>http://www.engineyard.com/blog/2009/15-expert-tips-for-using-cucumber/comment-page-1/#comment-13632</link>
		<dc:creator>Aslak Hellesoy</dc:creator>
		<pubDate>Mon, 17 Aug 2009 21:03:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.engineyard.com/blog/?p=1460#comment-13632</guid>
		<description>Excellent tips Dave! For more blog links - check out &lt;a href=&quot;http://wiki.github.com/aslakhellesoy/cucumber/tutorials-and-related-blog-posts&quot; target=&quot;_blank&quot;&gt;http://wiki.github.com/aslakhellesoy/cucumber/tut...&lt;/a&gt; </description>
		<content:encoded><![CDATA[<p>Excellent tips Dave! For more blog links &#8211; check out <a href="http://wiki.github.com/aslakhellesoy/cucumber/tutorials-and-related-blog-posts" target="_blank">http://wiki.github.com/aslakhellesoy/cucumber/tut&#8230;</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Abe</title>
		<link>http://www.engineyard.com/blog/2009/15-expert-tips-for-using-cucumber/comment-page-1/#comment-12624</link>
		<dc:creator>Abe</dc:creator>
		<pubDate>Wed, 12 Aug 2009 15:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.engineyard.com/blog/?p=1460#comment-12624</guid>
		<description>Can i also recomend that you explore using something prebuilt for saing a lot of time and work like 
 Reuse Step Definitions = Start with Pickle 
&lt;a href=&quot;http://github.com/ianwhite/pickle/tree/master&quot; target=&quot;_blank&quot;&gt;http://github.com/ianwhite/pickle/tree/master&lt;/a&gt; </description>
		<content:encoded><![CDATA[<p>Can i also recomend that you explore using something prebuilt for saing a lot of time and work like<br />
 Reuse Step Definitions = Start with Pickle<br />
<a href="http://github.com/ianwhite/pickle/tree/master" target="_blank">http://github.com/ianwhite/pickle/tree/master</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: danieroux</title>
		<link>http://www.engineyard.com/blog/2009/15-expert-tips-for-using-cucumber/comment-page-1/#comment-12212</link>
		<dc:creator>danieroux</dc:creator>
		<pubDate>Sun, 09 Aug 2009 18:26:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.engineyard.com/blog/?p=1460#comment-12212</guid>
		<description>As to step 10 (parsing time): 
 
Another thing to consider is to always reset time to some know start time before every scenario (I prefer 13 August 2005 - Friday the 13th). 
 
This is important once you start adding features that act differently over weekends/holidays. 
 
e.g. if you have a known start time, &quot;interest for the next week, compounding on work days&quot; will always give a predictable answer. </description>
		<content:encoded><![CDATA[<p>As to step 10 (parsing time):</p>
<p>Another thing to consider is to always reset time to some know start time before every scenario (I prefer 13 August 2005 &#8211; Friday the 13th).</p>
<p>This is important once you start adding features that act differently over weekends/holidays.</p>
<p>e.g. if you have a known start time, &quot;interest for the next week, compounding on work days&quot; will always give a predictable answer.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

