From 54e86cccd5c69322eb1df7a38e19baaadf8733d4 Mon Sep 17 00:00:00 2001 From: Jeremy Kemper Date: Thu, 5 Oct 2006 18:19:24 +0000 Subject: Update RUNNING_UNIT_TESTS for current Rake tasks. Closes #6349. git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@5228 5ecf4fe2-1ee6-0310-87b1-e25e094e27de --- activerecord/RUNNING_UNIT_TESTS | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'activerecord/RUNNING_UNIT_TESTS') diff --git a/activerecord/RUNNING_UNIT_TESTS b/activerecord/RUNNING_UNIT_TESTS index 17d9b1aa26..80cfd8a6e3 100644 --- a/activerecord/RUNNING_UNIT_TESTS +++ b/activerecord/RUNNING_UNIT_TESTS @@ -7,15 +7,16 @@ test/connections//connection.rb. When you have the database online, you can import the fixture tables with the test/fixtures/db_definitions/*.sql files. -Make sure that you create database objects with the same user that you specified in i +Make sure that you create database objects with the same user that you specified in connection.rb otherwise (on Postgres, at least) tests for default values will fail. == Running with Rake The easiest way to run the unit tests is through Rake. The default task runs the entire test suite for all the adapters. You can also run the suite on just -one adapter by using the tasks test_mysql_ruby, test_ruby_mysql, test_sqlite, -or test_postgresql. For more information, checkout the full array of rake tasks with "rake -T" +one adapter by using the tasks test_mysql, test_sqlite, test_postgresql or any +of the other test_ tasks. For more information, checkout the full array of rake +tasks with "rake -T" Rake can be found at http://rake.rubyforge.org -- cgit v1.2.3