[rspec-users] Spec Naming (was: Rspec Brown Bag)

Nick Sieger nicksieger at gmail.com
Tue Nov 21 17:32:23 EST 2006

On 11/21/06, Luke Redpath <contact at lukeredpath.co.uk> wrote:
> I'm not sure if that would really work with RSpec - the way I see it, when
> you say a behaviour is *optional*, what you really  mean is that that
> behaviour only happens under certain circumstances (i.e. a particular
> context). Of course this is already handled by setting specifications under
> certain contexts. Within a particular context a behaviour either happens or
> it doesn't, I don't think there should be any middle ground. Ultimately we
> are only concerned with what WILL happen under certain contexts, not things
> that may or may not happen (which is an observation at a level higher than
> we are working on).

Agree, which is why I think this type of feature doesn't make sense for BDD,
where you're using the specs to drive the implementation.  You are writing
the specs and the code, so you know exactly how the code "should" behave.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/rspec-users/attachments/20061121/1721b43a/attachment.html 

More information about the rspec-users mailing list