Re: [rspec-users] [Cucumber:4066] Cucumber vs, RSpec

2010-04-20 Thread Lucas Prim
For me, cukes acts more as an acceptance test that tells me when to stop the development and release a feature as rspec goes down to the internals of the app in order to make sure everything works ok. In this context, I think there is no magic recipe that tells you how much cucumber code you should

Re: [rspec-users] [Cucumber:4066] Cucumber vs, RSpec

2010-04-20 Thread Joseph Wilk
On Tue, Apr 20, 2010 at 9:12 PM, John Goodsen wrote: > Watch Ben Mabey's slides and talk at Ruby Conf on outside in development > with Cucumber.  It positions rspec and cucumber properly I used an analogy at Scotland on Rails that might be helpful. I was thinking about Rspec and Cucumber in terms

Re: [rspec-users] Anyone used RSpec to write specs for rake tasks?

2010-04-20 Thread Joseph Wilk
On 19/04/2010 22:13, Pat Maddox wrote: Put the interesting bits in a basic Ruby class and test that, then make the Rake tasks a very thin layer over the class. On Apr 19, 2010, at 8:46 AM, Rick DeNatale wrote: I released a new gem this past weekend which adds a new rake task for Jeweler

Re: [rspec-users] [Cucumber:4066] Cucumber vs, RSpec

2010-04-20 Thread John Goodsen
Watch Ben Mabey's slides and talk at Ruby Conf on outside in development with Cucumber. It positions rspec and cucumber properly On Tue, Apr 20, 2010 at 3:58 PM, Joseph Wilk wrote: > On Tue, Apr 20, 2010 at 8:05 PM, David Chelimsky > wrote: > > > > On Apr 20, 2010, at 1:57 PM, Mike Sassak wrot

Re: [rspec-users] [Cucumber:4066] Cucumber vs, RSpec

2010-04-20 Thread Joseph Wilk
On Tue, Apr 20, 2010 at 8:05 PM, David Chelimsky wrote: > > On Apr 20, 2010, at 1:57 PM, Mike Sassak wrote: > >> On Tue, Apr 20, 2010 at 2:33 PM, Ed Howland wrote: >>> Please forgive the x-post. >>> >>> I just got back from the Great Lakes Ruby Bash. They had several good >>> presentations, two s

Re: [rspec-users] [Cucumber:4066] Cucumber vs, RSpec

2010-04-20 Thread David Chelimsky
On Tue, Apr 20, 2010 at 2:05 PM, David Chelimsky wrote: > > On Apr 20, 2010, at 1:57 PM, Mike Sassak wrote: > >> On Tue, Apr 20, 2010 at 2:33 PM, Ed Howland wrote: >>> Please forgive the x-post. >>> >>> I just got back from the Great Lakes Ruby Bash. They had several good >>> presentations, two s

Re: [rspec-users] [Cucumber:4066] Cucumber vs, RSpec

2010-04-20 Thread Robert Hanson
With Cucumber, you can't possibly specify tests for all the corner cases. That's what your rspecs (unit tests) are for. -Original Message- From: cu...@googlegroups.com [mailto:cu...@googlegroups.com] On Behalf Of Ed Howland Sent: Tuesday, April 20, 2010 1:33 PM To: rspec-users; cu...@g

Re: [rspec-users] [Cucumber:4066] Cucumber vs, RSpec

2010-04-20 Thread David Chelimsky
On Apr 20, 2010, at 1:57 PM, Mike Sassak wrote: > On Tue, Apr 20, 2010 at 2:33 PM, Ed Howland wrote: >> Please forgive the x-post. >> >> I just got back from the Great Lakes Ruby Bash. They had several good >> presentations, two specific to BDD and Cucumber. I also talked to >> several CEOs and

Re: [rspec-users] [Cucumber:4066] Cucumber vs, RSpec

2010-04-20 Thread Mike Sassak
On Tue, Apr 20, 2010 at 2:33 PM, Ed Howland wrote: > Please forgive the x-post. > > I just got back from the Great Lakes Ruby Bash. They had several good > presentations, two specific to BDD and Cucumber. I also talked to > several CEOs and devs afterwards, and the overall takeaway I gathered > wa

[rspec-users] Cucumber vs, RSpec

2010-04-20 Thread Ed Howland
Please forgive the x-post. I just got back from the Great Lakes Ruby Bash. They had several good presentations, two specific to BDD and Cucumber. I also talked to several CEOs and devs afterwards, and the overall takeaway I gathered was a shift to less RSpec and more Cucumber. Some people even cla

[rspec-users] Speccing the creation of a singleton resource

2010-04-20 Thread Nick Hoffman
Hey guys. I'm writing a Rails gem that's used by controllers. The gem creates a singleton resource at run-time, along the lines of: controller_name = ...dynamically generated... ActionController::Routing::Routes.draw do |map| map.resource controller_name, :only => :show end I'm trying to f