On Oct 21, 2007, at 3:35 PM, Bryan Helmkamp wrote:
> On 10/18/07, Keith McDonnell <[EMAIL PROTECTED]> wrote:
>> rake spec:models seems to clone the test database from
>> development. If
>> your dev db is empty, the models task fails mysteriously.
>>
>> Anyway, to make sure your dev db is at the
On 10/18/07, Keith McDonnell <[EMAIL PROTECTED]> wrote:
> rake spec:models seems to clone the test database from development. If
> your dev db is empty, the models task fails mysteriously.
>
> Anyway, to make sure your dev db is at the current migration version, I
> added this dependency in lib/tas
Hi David,
If you give me some direction I'll try & submit a patch.
Keith
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
On Thu, 18 Oct 2007 11:30:03 -0500, David Chelimsky wrote:
>> Yeah, I was just about to post about this. This seems like incorrect
>> behavior. Especially if you're really doing behavior driven design. You're
>> going to be writing your tests and using the test environment first before
>> you actu
On 10/18/07, Steve <[EMAIL PROTECTED]> wrote:
> On Thu, 18 Oct 2007 15:51:37 +0100, Keith McDonnell wrote:
>
> > For those interested
> >
> > rake spec:models seems to clone the test database from development. If
> > your dev db is empty, the models task fails mysteriously.
> >
> > Anyway, to
On Thu, 18 Oct 2007 15:51:37 +0100, Keith McDonnell wrote:
> For those interested
>
> rake spec:models seems to clone the test database from development. If
> your dev db is empty, the models task fails mysteriously.
>
> Anyway, to make sure your dev db is at the current migration version,
For those interested
rake spec:models seems to clone the test database from development. If
your dev db is empty, the models task fails mysteriously.
Anyway, to make sure your dev db is at the current migration version, I
added this dependency in lib/tasks
task 'spec:models' => 'db:migrat
