On Thu, Feb 28, 2008 at 2:22 PM, Glenn Ford <[EMAIL PROTECTED]> wrote:
I agree with David - you are certainly on the right track. I also think you
are doing the right thing when you write specs even if they seem not perfect
to you at first attempt - once you have written the code you can evaluate
Hi list!
I get some not-so-nice output from rspec-rails when using the -f specdoc
option. It happens both with the spec command and the rake task and on a
prestine, newly generated rails app.
I'm using rspec & rspec-rails 1.1.4 and rails 2.0.1.
Is this a bug? Do you get the same output?
-- Siem
Thanks for you reply!
I had tried the newest checkouts of rsepc and rspec-rails from git as well,
but my locally installed rspec gem was 1.1.4 and apparently rake did use
that instead!
-- Siemen
___
rspec-users mailing list
rspec-users@rubyforge.org
htt