public
Description: Ruby on Rails
Homepage: http://rubyonrails.org
Clone URL: git://github.com/rails/rails.git
Search Repo:
commit  4d594cffcfc93b37fad4e423ec8593299e50133c
tree    59643ee7a1eec4e3208f81f6e344a66207f648ec
parent  0ff7a2d89fc95dcb0a32ed92aab7156b0778a7ea
rails / activerecord / RUNNING_UNIT_TESTS
100644 30 lines (21 sloc) 1.23 kb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
== Creating the test database
 
The default names for the test databases are "activerecord_unittest" and
"activerecord_unittest2". If you want to use another database name then be sure
to update the connection adapter setups you want to test with in
test/connections/<your database>/connection.rb.
When you have the database online, you can import the fixture tables with
the test/schema/*.sql files.
 
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, 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
 
== Running by hand
 
Unit tests are located in test/cases directory. If you only want to run a single test suite,
you can do so with:
 
   rake test_mysql TEST=test/cases/base_test.rb
   
That'll run the base suite using the MySQL-Ruby adapter.