Re: When Testing controllers, what should I be testing?
On 25 ago, 10:58, j.blotus j.blo...@gmail.com wrote: (..) I would like to get code coverage going for my controllers, but since they do not return anything, what exactly am I going to be testing for? (..) Basically, you can use the testAction method to test the variables an action set to the view (my choice) or even the HTML code rendered. http://book.cakephp.org/view/1210/Testing-controllers#The-testAction-method-1212 -- MARCELO F ANDRADE Belem, Amazonia, Brazil I took the red pill Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups CakePHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
When Testing controllers, what should I be testing?
I just got involved in using the CakePHP test suite, and I have been using it to test my models quite successfully. I would like to get code coverage going for my controllers, but since they do not return anything, what exactly am I going to be testing for? I have read the cookbook and Mark story's blog post on testing controllers, but I would just like to know how other people are testing their controllers. Thanks Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups CakePHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en