aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorZachary Scott <e@zzak.io>2014-12-29 13:05:14 -0800
committerZachary Scott <e@zzak.io>2014-12-29 13:05:14 -0800
commit1a7ab647de4af7129533ffb87c8a5e5670f96a01 (patch)
tree67416b08c1257eafa022e032ce612affdb09d098
parent4be29e5b5dcd385e75b1a7481b38ad131ee78729 (diff)
downloadrails-1a7ab647de4af7129533ffb87c8a5e5670f96a01.tar.gz
rails-1a7ab647de4af7129533ffb87c8a5e5670f96a01.tar.bz2
rails-1a7ab647de4af7129533ffb87c8a5e5670f96a01.zip
Rephrase functional testing in its relation to Rails Controller Unit Testing.
[ci skip]
-rw-r--r--guides/source/testing.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/testing.md b/guides/source/testing.md
index f7103adc1c..0d6121d307 100644
--- a/guides/source/testing.md
+++ b/guides/source/testing.md
@@ -450,7 +450,7 @@ You'll see the usage of some of these assertions in the next chapter.
Functional Tests for Your Controllers
-------------------------------------
-In Rails, testing the various actions of a single controller is called writing functional tests for that controller. Controllers handle the incoming web requests to your application and eventually respond with a rendered view.
+In Rails, testing the various actions of a controller is a form of writing functional tests. Remember your controllers handle the incoming web requests to your application and eventually respond with a rendered view. When writing functional tests, you're testing how your actions handle the requests and the expected result, or response in some cases an HTML view.
### What to Include in your Functional Tests