aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source/testing.md
diff options
context:
space:
mode:
authorKadu Ribeiro <mail@carlosribeiro.me>2018-09-10 10:28:03 -0300
committerCarlos Ribeiro <mail@carlosribeiro.me>2018-09-27 23:27:35 -0300
commit919b50822f637d05c45d0b82a27e24bd2579bbf9 (patch)
treec1d94292c8145f12895fe89987ee4ad37eff59b6 /guides/source/testing.md
parent12b32d804996c6bb3d215a22762c0c1a27f223d3 (diff)
downloadrails-919b50822f637d05c45d0b82a27e24bd2579bbf9.tar.gz
rails-919b50822f637d05c45d0b82a27e24bd2579bbf9.tar.bz2
rails-919b50822f637d05c45d0b82a27e24bd2579bbf9.zip
[ci skip] Recommend testing information displayed over object stored
Since `assigns` is not placed by default with Rails, we suggested to test if the right information was displayed instead of suggesting to test if the right object was stored in the template.
Diffstat (limited to 'guides/source/testing.md')
-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 de93e1c653..9de2229672 100644
--- a/guides/source/testing.md
+++ b/guides/source/testing.md
@@ -1028,8 +1028,8 @@ You should test for things such as:
* was the web request successful?
* was the user redirected to the right page?
* was the user successfully authenticated?
-* was the correct object stored in the response template?
* was the appropriate message displayed to the user in the view?
+* was the correct information displayed in the response?
The easiest way to see functional tests in action is to generate a controller using the scaffold generator: