Forum: Ruby on Rails Differences between console [development] and console test?

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
753038ae16700c0fd9a5e1d2e80f68f6?d=identicon&s=25 Lee (Guest)
on 2009-05-09 06:37
(Received via mailing list)
One of my model code methods is throwing an error when run using
script/console in test but not in development.

I'd be grateful if someone can tell me the differences between the
two, beyond the database that they connect to.

5f94b9b346c2aa648a80bc259978e5bc?d=identicon&s=25 Colin Law (Guest)
on 2009-05-09 09:49
(Received via mailing list)
I think all the differences are the differences between the settings in
test.rb and development.rb in config/environment/ plus those in

2009/5/9 Lee <>
6883e5ef03484d4fcef507d7b4f1d243?d=identicon&s=25 Matt Jones (Guest)
on 2009-05-09 17:43
(Received via mailing list)
A stack trace for the error will help out quite a bit. The most
notable difference between the two environments is that the test
environment has cache_classes = true, which triggers preloading of the
application classes on startup. But again, without a stack trace, it's
hard to tell.

--Matt Jones
This topic is locked and can not be replied to.