public
Description: Ruby on Rails
Homepage: http://rubyonrails.org
Clone URL: git://github.com/rails/rails.git
Search Repo:
jweiss (author)
Thu Apr 17 10:58:31 -0700 2008
josh (committer)
Thu Apr 17 10:58:31 -0700 2008
commit  9e1d506a8cfedef2fdd605e4cbf4bf53651ad214
tree    bb68f6da2b3425008fdab9905555dd813d42756a
parent  9e53b63601ce12fb7e4c8fdb16d5706ea8609d2f
rails / activerecord / RUNNING_UNIT_TESTS
100644 34 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
31
32
33
34
== 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.