Re: [rspec-users] Return code for running stories

Kero wrote: Hi all! Just wrote a few stories and committed code to a project of mine, then realized I made a mistake (with the commit, not the code or tests). It would be nice to put the script that runs the stories as a pre-commit hook, preventing the commit from succeeding if the stories fail.

[rspec-users] spec'ing calls to super (or other Ruby keywords)

Hi there, How does one spec an invocation of a Ruby keyword, such as super in this case? class User < ActiveResource::Base # faking the ActiveRecord before/after_save observers def save super UserMailer.deliver_activation(self) if recently_activated? end end Does the solution look

[rspec-users] Return code for running stories

Hi all! Just wrote a few stories and committed code to a project of mine, then realized I made a mistake (with the commit, not the code or tests). It would be nice to put the script that runs the stories as a pre-commit hook, preventing the commit from succeeding if the stories fail. For that, I

Re: [rspec-users] BDD/Rails/Shoulda

On 2 May 2008, at 06:13, Tero Tilus wrote: I can well imagine how you may end up not getting all the advantages of BDD thru uncommenting process when you compare to clean BDD. But uncommenting is definitely better than writing spec on top of existing code, which in turn is _way_ better than no