From 32626dec3f9d39c2d93152fb856f0b0e939bc732 Mon Sep 17 00:00:00 2001 From: Zachary Scott Date: Sat, 20 Dec 2014 11:05:36 -0800 Subject: Update comment regarding test environment with help from @matthewd [ci skip] --- guides/source/testing.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/guides/source/testing.md b/guides/source/testing.md index 40abac0507..ed04ccd100 100644 --- a/guides/source/testing.md +++ b/guides/source/testing.md @@ -29,7 +29,9 @@ Testing support was woven into the Rails fabric from the beginning. It wasn't an By default, every Rails application has three environments: development, test, and production. The database for each one of them is configured in `config/database.yml`. -A dedicated test database allows you to set up and interact with test data in isolation. Tests can mangle test data with confidence, that won't touch the data in the development or production databases. +A dedicated test database allows you to set up and interact with test data in isolation. This way your tests can mangle test data with confidence, without worrying about the data in the development or production databases. + +Also, each environment's configuration can be modified similarly. In this case, we can modify our test environment by changing the options found in `config/environments/test.rb`. ### Rails Sets up for Testing from the Word Go -- cgit v1.2.3