aboutsummaryrefslogtreecommitdiffstats
path: root/railties
diff options
context:
space:
mode:
authorJosiah Ivey <josiah.ivey@gmail.com>2010-05-16 13:58:56 -0500
committerJosiah Ivey <josiah.ivey@gmail.com>2010-05-16 13:58:56 -0500
commit774f596693a78c9a2f5cc92049a74ec817abffa1 (patch)
tree40f60e3ab3c0fbc282e77f24976cd5009c9e0b8a /railties
parent5de2e0d416b0635fc99655fbfcb24acddf5536e5 (diff)
downloadrails-774f596693a78c9a2f5cc92049a74ec817abffa1.tar.gz
rails-774f596693a78c9a2f5cc92049a74ec817abffa1.tar.bz2
rails-774f596693a78c9a2f5cc92049a74ec817abffa1.zip
Fix punctuation and keep the tone consistent
Diffstat (limited to 'railties')
-rw-r--r--railties/guides/source/testing.textile2
1 files changed, 1 insertions, 1 deletions
diff --git a/railties/guides/source/testing.textile b/railties/guides/source/testing.textile
index a4d5189376..91c92d0a65 100644
--- a/railties/guides/source/testing.textile
+++ b/railties/guides/source/testing.textile
@@ -858,7 +858,7 @@ The goals of testing your mailer classes are to ensure that:
h5. From All Sides
-There are two aspects of testing your mailer, the unit tests and the functional tests. In the unit tests, you run the mailer in isolation with tightly controlled inputs and compare the output to a known value (a fixture -- yay! more fixtures!). In the functional tests you don't so much test the minute details produced by the mailer Instead we test that our controllers and models are using the mailer in the right way. You test to prove that the right email was sent at the right time.
+There are two aspects of testing your mailer, the unit tests and the functional tests. In the unit tests, you run the mailer in isolation with tightly controlled inputs and compare the output to a known value (a fixture.) In the functional tests you don't so much test the minute details produced by the mailer; instead, we test that our controllers and models are using the mailer in the right way. You test to prove that the right email was sent at the right time.
h4. Unit Testing