mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
0d0fd2142b
git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@7902 5ecf4fe2-1ee6-0310-87b1-e25e094e27de
44 lines
1.5 KiB
Text
44 lines
1.5 KiB
Text
== 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/fixtures/db_definitions/*.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 directory. If you only want to run a single test suite,
|
|
you can do so with:
|
|
|
|
rake test_mysql TEST=base_test.rb
|
|
|
|
That'll run the base suite using the MySQL-Ruby adapter.
|
|
|
|
== Faster tests
|
|
|
|
If you are using a database that supports transactions, you can set the
|
|
"AR_TX_FIXTURES" environment variable to "yes" to use transactional fixtures.
|
|
This gives a very large speed boost. With rake:
|
|
|
|
rake AR_TX_FIXTURES=yes
|
|
|
|
Or, by hand:
|
|
|
|
AR_TX_FIXTURES=yes ruby -I connections/native_sqlite3 base_test.rb
|
|
|
|
|