<?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>Wed, 19 Jun 2013 04:08:42 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[PHPImpact Blog: PHPUnit: Testing Zend Framework Controllers]]></title>
      <guid>http://www.phpdeveloper.org/news/11632</guid>
      <link>http://www.phpdeveloper.org/news/11632</link>
      <description><![CDATA[<p>
On the PHP::Impact blog there's a <a href="http://phpimpact.wordpress.com/2008/12/27/phpunit-testing-zend-framework-controllers/">recent post</a> looking at using the popular unit testing PHP framework <a href="http://www.phpunit.de">PHPUnit</a> to test Zend Framework controllers.
</p>
<blockquote>
Testing a Web application is a complex task, because a Web application is made of several layers of logic. Unit testing a Zend Framework controller can be very difficult, specially for those who are not familiar with the Zend Framework. You can test your action controllers using <a href="http://framework.zend.com/manual/en/zend.test.html">Zend_Test</a> and/or <a href="http://www.phpunit.de/">PHPUnit</a>. Zend_Test allows you to simulate requests, insert test data, inspect your application's output and generally verify your code is doing what it should be doing.
</blockquote>
<p>
He opts for the second one and includes the directory structure you'll need to set up the tests, an example bootstrap file and a simple controller (AllTests). A simple test example is also included that checks a few things - if its the default action, the first action, parameter names and method names.
</p>]]></description>
      <pubDate>Mon, 29 Dec 2008 10:21:37 -0600</pubDate>
    </item>
  </channel>
</rss>
