Jeremy Hageman wrote:
As someone relatively new to rspec, I am interested in hearing the
wisdom of the group in the area of using a fixture replacement gem
(such as machinist or factory girl) instead of mocking the model. To
me it seems that using a fixture replacement, instead of a mock, would
c
On Tue, Sep 1, 2009 at 4:11 PM, Jeremy Hageman wrote:
> As someone relatively new to rspec, I am interested in hearing the
> wisdom of the group in the area of using a fixture replacement gem
> (such as machinist or factory girl) instead of mocking the model.
For what kind of test?
--
Have Fun
On 1 Sep 2009, at 21:11, Jeremy Hageman wrote:
As someone relatively new to rspec, I am interested in hearing the
wisdom of the group in the area of using a fixture replacement gem
(such as machinist or factory girl) instead of mocking the model. To
me it seems that using a fixture replacement,
As someone relatively new to rspec, I am interested in hearing the
wisdom of the group in the area of using a fixture replacement gem
(such as machinist or factory girl) instead of mocking the model. To
me it seems that using a fixture replacement, instead of a mock, would
circumvent some of rspec'
> Wow you seem to have already been down this path and this is excellent
> advice - thanks!!!
:-)
http://github.com/alexch/vegas
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
Alex Chaffee wrote:
I often create integration programs in Ruby that utilize ActiveRecord without
the full Rails stack. So I wonder what the best way would be to fully utilize
Cucumber and RSpec for BDD in this context.
1. Should I still include rspec-rails so hopefully at least the Model supp
Matt Wynne wrote:
On 1 Sep 2009, at 19:44, Rick DeNatale wrote:
On Tue, Sep 1, 2009 at 1:51 PM, Carl Graff wrote:
Of less importance:
Actually I have considered creating/converting these integration
applications as full blown Rails applications since they definitely
have a
model and cont
> I often create integration programs in Ruby that utilize ActiveRecord without
> the full Rails stack. So I wonder what the best way would be to fully utilize
> Cucumber and RSpec for BDD in this context.
>
> 1. Should I still include rspec-rails so hopefully at least the Model support
> is ava
On 1 Sep 2009, at 19:44, Rick DeNatale wrote:
On Tue, Sep 1, 2009 at 1:51 PM, Carl Graff wrote:
Of less importance:
Actually I have considered creating/converting these integration
applications as full blown Rails applications since they definitely
have a
model and controller aspect and
On Tue, Sep 1, 2009 at 1:51 PM, Carl Graff wrote:
> Of less importance:
>
> Actually I have considered creating/converting these integration
> applications as full blown Rails applications since they definitely have a
> model and controller aspect and the Rails framework provides so many
> built-
Hi,
I often create integration programs in Ruby that utilize ActiveRecord
without the full Rails stack. So I wonder what the best way would be to
fully utilize Cucumber and RSpec for BDD in this context.
1. Should I still include rspec-rails so hopefully at least the Model
support is availab
11 matches
Mail list logo
