<?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>Thu, 23 May 2013 16:33:48 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Till's Blog: Avoiding common pitfalls with Zend_Test]]></title>
      <guid>http://www.phpdeveloper.org/news/12242</guid>
      <link>http://www.phpdeveloper.org/news/12242</link>
      <description><![CDATA[<p>
<i>Till</i> has <a href="http://till.klampaeckel.de/blog/archives/21-Avoiding-common-pitfalls-with-Zend_Test.html">recently made a post</a> to his blog looking to help other developers avoid some of the common issues that he's seen with the Zend_Test component of the <a href="http://framework.zend.com">Zend Framework</a>.
</p>
<blockquote>
I feel like I've wasted a great deal of time last week with basics that were nowhere to be found or required debugging to no end. The following is the outcome, a rather random list of things to watch out for when you're starting on Zend_Test.
</blockquote>
<p>
He has notes on a few different topics like debugging, environment control, crating an AllTests file, avoiding direct calls to PHP and bootstrapping correctly. A knowledge of PHPUnit and unit testing is recommended.
</p>]]></description>
      <pubDate>Tue, 31 Mar 2009 10:23:13 -0500</pubDate>
    </item>
  </channel>
</rss>
