From ae040ed6d8c48bf0cd6d5d6b434d60c9c8c27f81 Mon Sep 17 00:00:00 2001 From: Vijay Dev Date: Tue, 27 Mar 2012 21:24:21 +0530 Subject: minor edits in testing guide [ci skip] --- guides/source/testing.textile | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) (limited to 'guides/source') diff --git a/guides/source/testing.textile b/guides/source/testing.textile index c1c7b2f341..60b0aa89b9 100644 --- a/guides/source/testing.textile +++ b/guides/source/testing.textile @@ -524,7 +524,7 @@ You also have access to three instance variables in your functional tests: * +@request+ - The request * +@response+ - The response -h4. Testing Template and Layout Example +h4. Testing Templates and Layouts If you want to make sure that the response rendered the correct template and layout, you can use the +assert_template+ method: @@ -543,13 +543,11 @@ things clearer. On the other hand, you have to include the "layouts" directory n file in this standard layout directory. Hence, - assert_template :layout => "application" +assert_template :layout => "application" will not work. -Gotcha: Watch out if your view renders any partial - If your view renders any partial, when asserting for the layout, you have to assert for the partial at the same time. Otherwise, assertion will fail. -- cgit v1.2.3