<?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>Sat, 25 May 2013 10:43:54 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Zoe Slattery's Blog: Lateral Thinking]]></title>
      <guid>http://www.phpdeveloper.org/news/11410</guid>
      <link>http://www.phpdeveloper.org/news/11410</link>
      <description><![CDATA[<p>
When it comes to code coverage and untested parts of your application (unit tested, of course), <i>Zoe Slattery</i> <A href="http://zoomsplatter.blogspot.com/2008/11/lateral-thinking.html">has a suggestion</a> that could make your life easier anyway - follow the core PHP developer's example:
</p>
<blockquote>
But - there is another way, and as usual the PHP core developers are showing us the way. The fastest way to improve percentage of code covered is to REMOVE UNTESTED CODE! Accordingly we saw the test coverage of PHP 5.3 increase from about 55% to a little over 70% over the <a href="http://gcov.php.net/viewer.php?version=PHP_5_3&func=graph&mode=Year">summer of 2008</a>. At the same time the lines of code in PHP dropped by about 50KLOC. How can this be?
</blockquote>
<p>
Removing untested code (that's not needed anyway) can reduce unit testing times dramatically and can help you keep your code clean, lean and simple for the upgrades that will come later on.
</p>]]></description>
      <pubDate>Fri, 14 Nov 2008 11:19:54 -0600</pubDate>
    </item>
  </channel>
</rss>
