diff options
| author | Sammy Larbi <sam@codeodor.com> | 2014-12-21 10:13:54 -0600 |
|---|---|---|
| committer | Sammy Larbi <sam@codeodor.com> | 2014-12-21 10:18:46 -0600 |
| commit | f5489f9ab4eddeb5d4ee57b5b4d1f2967073194d (patch) | |
| tree | 19dd948ff3e0d7dcd09f4d5069203e76bdddbc9e | |
| parent | ef529c637130918d8cb225bd7083e44ef4887899 (diff) | |
| download | rails-f5489f9ab4eddeb5d4ee57b5b4d1f2967073194d.tar.gz rails-f5489f9ab4eddeb5d4ee57b5b4d1f2967073194d.tar.bz2 rails-f5489f9ab4eddeb5d4ee57b5b4d1f2967073194d.zip | |
Clarify ActiveRecord testing guidelines [ci skip]
1. Specify that you need to create the test databases, and that no special
Rails command needs to be run to do that.
2. Although the underscore style of `rake test_mysql` works, make the
documentation of running the tests in RUNNING_UNIT_TESTS.rdoc
consistent with the "Contributing..." guide.
3. Promote "Testing Active Record" to not be a subsection of
"Running a Single Test," since it doesn't make sense as a subsection
of that.
| -rw-r--r-- | activerecord/RUNNING_UNIT_TESTS.rdoc | 10 | ||||
| -rw-r--r-- | guides/source/contributing_to_ruby_on_rails.md | 7 |
2 files changed, 11 insertions, 6 deletions
diff --git a/activerecord/RUNNING_UNIT_TESTS.rdoc b/activerecord/RUNNING_UNIT_TESTS.rdoc index 569685bd45..7e3460365b 100644 --- a/activerecord/RUNNING_UNIT_TESTS.rdoc +++ b/activerecord/RUNNING_UNIT_TESTS.rdoc @@ -20,11 +20,11 @@ example: Simply executing <tt>bundle exec rake test</tt> is equivalent to the following: - $ bundle exec rake test_mysql - $ bundle exec rake test_mysql2 - $ bundle exec rake test_postgresql - $ bundle exec rake test_sqlite3 - $ bundle exec rake test_sqlite3_mem + $ bundle exec rake test:mysql + $ bundle exec rake test:mysql2 + $ bundle exec rake test:postgresql + $ bundle exec rake test:sqlite3 + $ bundle exec rake test:sqlite3_mem There should be tests available for each database backend listed in the {Config File}[rdoc-label:label-Config+File]. (the exact set of available tests is diff --git a/guides/source/contributing_to_ruby_on_rails.md b/guides/source/contributing_to_ruby_on_rails.md index 17afd07820..ef3ebb1412 100644 --- a/guides/source/contributing_to_ruby_on_rails.md +++ b/guides/source/contributing_to_ruby_on_rails.md @@ -287,7 +287,12 @@ $ ruby -w -Itest test/mail_layout_test.rb -n test_explicit_class_layout The `-n` option allows you to run a single method instead of the whole file. -##### Testing Active Record +#### Testing Active Record + +First, create the databases you'll need. For MySQL and PostgreSQL, +running the SQL statements `create database activerecord_unittest` and +`create database activerecord_unittest2` is sufficient. This is not +necessary for SQLite3. This is how you run the Active Record test suite only for SQLite3: |