revises RUNNING_UNIT_TESTS to delegate stuff to the contributing guide

1 files changed, 5 insertions, 11 deletions

diff --git a/activerecord/RUNNING_UNIT_TESTS b/activerecord/RUNNING_UNIT_TESTS
index 7f512e06fb..bdd8834dcb 100644
--- a/activerecord/RUNNING_UNIT_TESTS
+++ b/activerecord/RUNNING_UNIT_TESTS
@@ -1,16 +1,10 @@
-If you don't have the environment set make sure to read
-http://edgeguides.rubyonrails.org/contributing_to_ruby_on_rails.html#testing-active-record.
-
-== Configure databases
+== Setup
 
-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).
-
-Create a mysql superuser named 'rails' that does not have a password.
+If you don't have the environment set make sure to read
 
-You can build postgres and mysql databases using the postgresql:build_databases and mysql:build_databases rake tasks.
+    http://edgeguides.rubyonrails.org/contributing_to_ruby_on_rails.html#testing-active-record.
 
-== Running the tests
+== Running the Tests
 
 You can run a particular test file from the command line, e.g.
 
@@ -31,7 +25,7 @@ You can run all the tests for a given database via rake:
 
 The 'rake test' task will run all the tests for mysql, mysql2, sqlite3 and postgresql.
 
-== Config file
+== Custom 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.