Feeding the framework?

Testing RSpec
1

Hi there,

Is it just me or do many other rspec / rpsec_on_rails users spend more
time than they would like feeding the framework ?

Don’t get me wrong, I love rpsec, but I seem to spend about 2/3 hours
per week hunting down rspec problems.

For example, today rake spec:models is broken. When I migrate, load
fixtures and run spec -cfs all is well. When I run rake spec:models,
there are no tables loaded.

RuntimeError: ERROR C42P01 Mrelation “table_name” does not exist

Any tips or checklists when problems arise ?

Keith

2

On 10/18/07, Keith McDonnell [email protected] wrote:

there are no tables loaded.

RuntimeError: ERROR C42P01 Mrelation “table_name” does not exist

Any tips or checklists when problems arise ?

I feel your pain (see the goofy error described in this thread:
http://www.nabble.com/Strange-mock_model-behaviour-with-ActiveResource-model-tf4615538.html),
but given I’m running edge/trunk I kind of figure I’m asking for it.:wink:
One tip that seems to come up a lot is re-bootstrap with the
‘script/generate rspec’ command. You don’t say if you’re getting these
errors after updating or if it’s a gem issue, so not sure if that
would help you.

James

3

On 10/18/07, Keith McDonnell [email protected] wrote:

there are no tables loaded.

RuntimeError: ERROR C42P01 Mrelation “table_name” does not exist

Any tips or checklists when problems arise ?

How about raising the issue in the tracker?

http://rubyforge.org/tracker/?group_id=797

4

On 10/18/07, David C. [email protected] wrote:

fixtures and run spec -cfs all is well. When I run rake spec:models,
there are no tables loaded.

RuntimeError: ERROR C42P01 Mrelation “table_name” does not exist

Also - I don’t experience this. I keep the latest trunk in my projects
and have never seen this.

5

Thanks for the tip & sympathy.

I reinstalled rspec from scratch with a fresh project to investigate the
error.

Turns out that the rake spec:models clones the test db from the dev
environment! I incorrectly assumed that the test db was migrated up &
down independently. I mailed a work around here:

http://rubyforge.org/pipermail/rspec-users/2007-October/003904.html

Keith