haha -- love it!
--
Posted via http://www.ruby-forum.com/.
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
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
> Any chance you have an rspec gem installed too? If so and you don't
> need it, get rid of it. If so and you do need it, grab the latest
> rspec/rspec-rails plugins and cd into the rspec directory and do this:
Yes, that was it. Getting rid of my rspec gem did the trick.
Many thanks
David
__
On Fri, Jul 18, 2008 at 5:56 AM, David Salgado <[EMAIL PROTECTED]> wrote:
> Hi All
>
> I'm using test/unit on a project, at the client's insistence, but I'm
> also using rspec stories for integration testing. I notice that as
> soon as I install rspec and rspec-rails plugins, autotest no longer
> f
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 All
I'm using test/unit on a project, at the client's insistence, but I'm
also using rspec stories for integration testing. I notice that as
soon as I install rspec and rspec-rails plugins, autotest no longer
finds my test/unit tests - it just runs specs. Is there a way to make
autotest run *bo
Hi all,
I wrote an ActiveRecord extension to emulate a db cursor:
http://pastie.org/236367
As you can see, the spec doesn't really ensure that the records are
fetched in chunks. I'd like to mock the call to AR find and ensure that
it's called with an incrementing offset.
Any advice?
Keith
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