[Rails] Re: testing and migrations
I also don't use Test::Unit. I use Rspec, and I assumed, correctly it
would seem, that the behavior was the same.
Rake db:test:clone just clones from the development, no?
On Jun 27, 7:27 am, Marnen Laibow-Koser <li...@ruby-forum.com> wrote:
> Hassan Schroeder wrote:
> > On Sun, Jun 27, 2010 at 6:47 AM, Marnen Laibow-Koser
> > <li...@ruby-forum.com> wrote:
> >> anywho wrote:
> >>> does rails always need to update the development database before
> >>> running the
> >>> tests? It seems to insisit on running db:migrate before.
>
> >> Your production DB is not the dev DB, so you needn't migrate it before
> >> tests pass You can also just migrate the test DB itself
>
> > Which ignores the original question, rephrased:
>
> > 1) generate a migration
> > 2) migrate your test db
> > 3) run `rake test:units`
>
> > You'll get a prompt to run migrations, which only goes away if you
> > migrate your *development* db.
>
> > I also find that behavior strange.
>
> I've never done it in that order, so didn't realize that part. I also
> don't use Test::Unit; not sure if that's significant. Thanks for the
> clarification.
>
>
>
> > --
> > Hassan Schroeder ------------------------ hassan.schroe...@gmail.com
> > twitter: @hassan
>
> --
> Posted viahttp://www.ruby-forum.com/.
--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
0 Comments:
Post a Comment
Subscribe to Post Comments [Atom]
<< Home