I think I get it now: We 're just making sure that our views has everything it should in it's place (links, html elements etc) even after some new features we may add to our site (permission levels, authentication etc)?
However I think that in the book it isn't explained in a clear way: > *The unit testing of models that we did previously seemed straightforward > enough. We called a method and compared what it returned against what > we expected it to return. But now we are dealing with a server that > processes > requests and a user viewing responses in a browser. What we will need is > functional tests that verify that the model, view, and controller work well > together. Never fear, Rails makes this easy too.* It just states that we'll verify that the model, view and controller work well together. But as I see it, functional test is all about the controller and the view since *it checks for elements that appear on the view to see if the controller is functioning properly*, isn't that right? -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-talk/-/dIO_zNdPMZMJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
