<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Fri, 24 May 2013 14:12:42 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Felix Geisendorfer's Blog: Controller Testing in CakePHP]]></title>
      <guid>http://www.phpdeveloper.org/news/6136</guid>
      <link>http://www.phpdeveloper.org/news/6136</link>
      <description><![CDATA[<p>
In <a href="http://www.thinkingphp.org/2006/08/24/controller-testing-in-cakephp/">this new post</a> on ThinkingPHP.org, <i>Felix Geisendorfer</i> talks about some of the development work that he's been doing regarding CakePHP:
</p>
<blockquote>
My first idea was to do unit testing on Controllers. I made a little comment about it here and uploaded some of <a href="http://cakephp.org/pastes/show/8803bd09150cb65cc7da63f92cdbc828">my experimental code</a> for that. In the beginning it looked very promising. I was able to mock Models & Components and add them to the Controller. But the deeper I got into it, the more I realized: Unit Testing with Controllers is insane
</blockquote>
<p>
To <a href="http://www.thinkingphp.org/2006/08/24/controller-testing-in-cakephp/">back it up</a> he points out some of the hurdles he had to work with and includes some of the code he used to test the Controllers he had made inside of CakePHP.
</p>]]></description>
      <pubDate>Thu, 24 Aug 2006 19:06:01 -0500</pubDate>
    </item>
  </channel>
</rss>
