rails--rails/activerecord/RUNNING_UNIT_TESTS

== Configure databases

Copy test/config.example.yml to test/config.yml and edit as needed. Or just run the tests for
the first time, which will do the copy automatically and use the default (sqlite3).

You can build postgres and mysql databases using the postgresql:build_databases and mysql:build_databases rake tasks.

== Running the tests

You can run a particular test file from the command line, e.g.

  $ ruby -Itest test/cases/base_test.rb

To run a specific test:

  $ ruby -Itest test/cases/base_test.rb -n test_something_works

You can run with a database other than the default you set in test/config.yml, using the ARCONN
environment variable:

  $ ARCONN=postgresql ruby -Itest test/cases/base_test.rb

You can run all the tests for a given database via rake:

  $ rake test_mysql

The 'rake test' task will run all the tests for mysql, mysql2, sqlite3 and postgresql.

== Config file

By default, the config file is expected to be at the path test/config.yml. You can specify a
custom location with the ARCONFIG environment variable.
Refactor Active Record test connection setup. Please see the RUNNING_UNIT_TESTS file for details, but essentially you can now configure things in test/config.yml. You can also run tests directly via the command line, e.g. ruby path/to/test.rb (no rake needed, uses default db connection from test/config.yml). This will help us fix the CI by enabling us to isolate the different Rails versions to different databases. 2011-06-04 18:19:17 -04:00			`== Configure databases`
Initial git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@4 5ecf4fe2-1ee6-0310-87b1-e25e094e27de 2004-11-23 20:04:44 -05:00
Refactor Active Record test connection setup. Please see the RUNNING_UNIT_TESTS file for details, but essentially you can now configure things in test/config.yml. You can also run tests directly via the command line, e.g. ruby path/to/test.rb (no rake needed, uses default db connection from test/config.yml). This will help us fix the CI by enabling us to isolate the different Rails versions to different databases. 2011-06-04 18:19:17 -04:00			`Copy test/config.example.yml to test/config.yml and edit as needed. Or just run the tests for`
			`the first time, which will do the copy automatically and use the default (sqlite3).`
Initial git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@4 5ecf4fe2-1ee6-0310-87b1-e25e094e27de 2004-11-23 20:04:44 -05:00
Update with new task names for building mysql and postgresql databases 2012-02-23 09:49:48 -05:00			`You can build postgres and mysql databases using the postgresql:build_databases and mysql:build_databases rake tasks.`
Initial git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@4 5ecf4fe2-1ee6-0310-87b1-e25e094e27de 2004-11-23 20:04:44 -05:00
Refactor Active Record test connection setup. Please see the RUNNING_UNIT_TESTS file for details, but essentially you can now configure things in test/config.yml. You can also run tests directly via the command line, e.g. ruby path/to/test.rb (no rake needed, uses default db connection from test/config.yml). This will help us fix the CI by enabling us to isolate the different Rails versions to different databases. 2011-06-04 18:19:17 -04:00			`== Running the tests`
Initial git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@4 5ecf4fe2-1ee6-0310-87b1-e25e094e27de 2004-11-23 20:04:44 -05:00
Refactor Active Record test connection setup. Please see the RUNNING_UNIT_TESTS file for details, but essentially you can now configure things in test/config.yml. You can also run tests directly via the command line, e.g. ruby path/to/test.rb (no rake needed, uses default db connection from test/config.yml). This will help us fix the CI by enabling us to isolate the different Rails versions to different databases. 2011-06-04 18:19:17 -04:00			`You can run a particular test file from the command line, e.g.`
Initial git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@4 5ecf4fe2-1ee6-0310-87b1-e25e094e27de 2004-11-23 20:04:44 -05:00
Update the RUNNING_UNIT_TESTS file 2011-06-09 04:11:26 -04:00			`$ ruby -Itest test/cases/base_test.rb`
Initial git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@4 5ecf4fe2-1ee6-0310-87b1-e25e094e27de 2004-11-23 20:04:44 -05:00
Refactor Active Record test connection setup. Please see the RUNNING_UNIT_TESTS file for details, but essentially you can now configure things in test/config.yml. You can also run tests directly via the command line, e.g. ruby path/to/test.rb (no rake needed, uses default db connection from test/config.yml). This will help us fix the CI by enabling us to isolate the different Rails versions to different databases. 2011-06-04 18:19:17 -04:00			`To run a specific test:`
Initial git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@4 5ecf4fe2-1ee6-0310-87b1-e25e094e27de 2004-11-23 20:04:44 -05:00
Update the RUNNING_UNIT_TESTS file 2011-06-09 04:11:26 -04:00			`$ ruby -Itest test/cases/base_test.rb -n test_something_works`
Initial git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@4 5ecf4fe2-1ee6-0310-87b1-e25e094e27de 2004-11-23 20:04:44 -05:00
Refactor Active Record test connection setup. Please see the RUNNING_UNIT_TESTS file for details, but essentially you can now configure things in test/config.yml. You can also run tests directly via the command line, e.g. ruby path/to/test.rb (no rake needed, uses default db connection from test/config.yml). This will help us fix the CI by enabling us to isolate the different Rails versions to different databases. 2011-06-04 18:19:17 -04:00			`You can run with a database other than the default you set in test/config.yml, using the ARCONN`
			`environment variable:`
Deletes trailing whitespaces (over text files only find * -type f -exec sed 's/[ \t]*$//' -i {} \;) 2010-08-14 01:13:00 -04:00
Update the RUNNING_UNIT_TESTS file 2011-06-09 04:11:26 -04:00			`$ ARCONN=postgresql ruby -Itest test/cases/base_test.rb`
Added change_table for migrations (Jeff Dean) [#71 state:resolved] 2008-05-03 12:29:47 -04:00
Refactor Active Record test connection setup. Please see the RUNNING_UNIT_TESTS file for details, but essentially you can now configure things in test/config.yml. You can also run tests directly via the command line, e.g. ruby path/to/test.rb (no rake needed, uses default db connection from test/config.yml). This will help us fix the CI by enabling us to isolate the different Rails versions to different databases. 2011-06-04 18:19:17 -04:00			`You can run all the tests for a given database via rake:`
Fixed a few Oracle issues: Allows Oracle's odd date handling to still work consistently within #to_xml, Passes test that hardcode insert statement by dropping the :id column, Updated RUNNING_UNIT_TESTS with Oracle instructions, Corrects method signature for #exec #5294 [schoenm@earthlink.net] git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@4552 5ecf4fe2-1ee6-0310-87b1-e25e094e27de 2006-07-04 22:54:19 -04:00
Update the RUNNING_UNIT_TESTS file 2011-06-09 04:11:26 -04:00			`$ rake test_mysql`
Fixed a few Oracle issues: Allows Oracle's odd date handling to still work consistently within #to_xml, Passes test that hardcode insert statement by dropping the :id column, Updated RUNNING_UNIT_TESTS with Oracle instructions, Corrects method signature for #exec #5294 [schoenm@earthlink.net] git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@4552 5ecf4fe2-1ee6-0310-87b1-e25e094e27de 2006-07-04 22:54:19 -04:00
Update the RUNNING_UNIT_TESTS file 2011-06-09 04:11:26 -04:00			`The 'rake test' task will run all the tests for mysql, mysql2, sqlite3 and postgresql.`
Print out information about whether the identity map is on or off when running unit tests 2011-06-09 15:15:34 -04:00
Add support for using an ARCONFIG environment variable to specify the location of the config.yml file for running the tests 2011-06-12 14:08:16 -04:00			`== Config file`

			`By default, the config file is expected to be at the path test/config.yml. You can specify a`
			`custom location with the ARCONFIG environment variable.`