<?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>Tue, 18 Jun 2013 21:49:44 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[PHPMaster.com: Thoughts of a Pragmatic Tester]]></title>
      <guid>http://www.phpdeveloper.org/news/17753</guid>
      <link>http://www.phpdeveloper.org/news/17753</link>
      <description><![CDATA[<p>
On PHPMaster.com today there's a new article with some <a href="http://phpmaster.com/thoughts-of-a-pragmatic-tester/">thoughts of a pragmatic tester</a> - some thoughts from <i>Michael Bodnarchuk</i> about both unit and functional testing.
</p>
<blockquote>
<p>
Here's how it usually plays out: the developer thinks, "I need to do unit tests, and I should use PHPUnit because it's a standard. I don't know much about it, though." Then he visits the PHPUnit site and reads the first chapter of the documentation, then the second, then the third… and is left scratching his head.
</p>
<p>
[...] Maybe something similar happened to you. Maybe not. But you really should know what to test and how to test it. Such knowledge comes from experience, so in this article I'll share some of my experience with unit testing.
</p>
</blockquote>
<p>
The article's not so much an introduction to unit testing as it is some of the experiences he's had around testing his applications both at the code level and from a functional perspective. He also mentions some alternatives to the standard <a href="http://phpunit.de">PHPUnit</a> testing like <a href="https://github.com/mageekguy/atoum">Atoum</a> and <a href="http://www.enhance-php.com/">EnhancePHP</a>.
</p>]]></description>
      <pubDate>Thu, 29 Mar 2012 13:43:02 -0500</pubDate>
    </item>
  </channel>
</rss>
