On Wed, Nov 5, 2008 at 12:16 AM, Fernando Perez <[EMAIL PROTECTED]> wrote: > I am missing something here. Using PostgreSQL, when I remove this line > from the rake task, I don't see the DB being populated although I do > invoke create! on some models. >
Vanilla Rails test:* tasks do the same, as do the rspec:* tasks. db:test:prepare is a shortcut for running all the migrations from the first to the last. If you write a functional Test::Unit test and run rake test:functionals - do you still have problems? If so - this is likely not related to Cucumber. > When I use debug(@some_instance) I see its id gets increased, so there > is definitely some data already in the DB. > > Why can't I see anything in the DB? Is it possible to mock models so > that the rake features doesn't have to recreate the test DB each time to > speed things up? > > I am interested in replacing controller specs by webrat features. I > prefer the webrat's black box approach more for testing controllers and > views. > > Would it be possible to have autotest trigger "rake features"? > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > rspec-users mailing list > rspec-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users > _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
