I'm running Merb 0.5.3 with Test::Unit. When I run 'rake test' it seems to be using the development environment as shown by the output here:
(in /home/farrel/Projects/blue_mars) /usr/lib/ruby/gems/1.8/gems/merb-0.5.3/lib/merb/version.rb:45: warning: already initialized constant RELEASE Sun, 10 Feb 2008 22:20:01 GMT: Connecting to the 'blue_mars_dev' database on 'localhost' using 'postgres' ... /usr/bin/ruby18 -Ilib:test "/usr/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake/rake_test_loader.rb" "test/unit/organisation_test.rb" "test/unit/user_test.rb" /usr/lib/ruby/gems/1.8/gems/merb-0.5.3/lib/merb/version.rb:45: warning: already initialized constant RELEASE Started merb_init.rb ... Sun, 10 Feb 2008 22:20:02 GMT: Connecting to the 'blue_mars_dev' database on 'localhost' using 'postgres' ... Loading Application... Compiling routes.. Loaded DEVELOPMENT Environment... Loaded suite /usr/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake/rake_test_loader Started ... Finished in 0.019958 seconds. I also noticed that the database is not wiped between test runs and old test data remains present in the database. I could not find anything in the Rake tasks which cleared the test databases. Am I running on old code that is causing these two issues or am I missing something else? Farrel _______________________________________________ Merb-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/merb-devel
