Brian Ledsworth wrote in post #987662:
> Mohnish
>
> Hard to tell without looking at the state if your rails app or the
> specs. But, it looks like it might be your Model. Try loading the
> rails console in test ("rails console test"), and see if you can create
> and save the model. Also, I assume "rake db:migrate" ran without issue
> as well?
>
> If that's all good, please post your spec.
>
> Brian
Hi Brian,
I made a fundamental mistake, I realized that I always made use of rake
db:create, and rake db:migrate. This would set things for me with
Development Environment. For the test enviroment, I had to use rake
db:test:prepare or rake db:migrate with appropriate syntax to reflect
the migrations in the Test Environment.
Thank you for your response and attempt to help..
Its appreciated..:)
--
Posted via http://www.ruby-forum.com/.
_______________________________________________
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
