[rspec-users] Cucumber: Why rake features needs to call db:test:prepare?

2008-11-04 Thread Fernando Perez
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. 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

Re: [rspec-users] Cucumber: Why rake features needs to call db:test:prepare?

2008-11-04 Thread aslak hellesoy
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

Re: [rspec-users] Cucumber: Why rake features needs to call db:test:prepare?

2008-11-04 Thread Ben Mabey
Fernando Perez 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. When I use debug(@some_instance) I see its id gets increased, so there is definitely some data already

Re: [rspec-users] Cucumber: Why rake features needs to call db:test:prepare?

2008-11-04 Thread Mark Wilden
On Tue, Nov 4, 2008 at 3:25 PM, aslak hellesoy [EMAIL PROTECTED]wrote: db:test:prepare is a shortcut for running all the migrations from the first to the last. Not quite. db:test:prepare just copies the schema from the development database to the test database. It aborts if there are any