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
On Fri, Jul 18, 2008 at 3:00 AM, Siemen Baader <[EMAIL PROTECTED]> wrote:
> 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 & r
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
