diff options
| author | Zachary Scott <e@zzak.io> | 2014-12-22 06:45:33 -0500 |
|---|---|---|
| committer | Zachary Scott <e@zzak.io> | 2014-12-22 06:45:33 -0500 |
| commit | a1ec6a5d1a202414947edaba66b7fb4d60a38b4e (patch) | |
| tree | 9c42be1a33958392a2ab4187bcb86084e47d6d66 | |
| parent | e77f24b9374837d805b43b5c2c8bb6221721550f (diff) | |
| parent | f5489f9ab4eddeb5d4ee57b5b4d1f2967073194d (diff) | |
| download | rails-a1ec6a5d1a202414947edaba66b7fb4d60a38b4e.tar.gz rails-a1ec6a5d1a202414947edaba66b7fb4d60a38b4e.tar.bz2 rails-a1ec6a5d1a202414947edaba66b7fb4d60a38b4e.zip | |
Merge pull request #18125 from codeodor/master
Clarify ActiveRecord testing guidelines [ci skip]
| -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: |