<?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 00:24:30 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Volker Dusch's Blog: Textual code coverage information for PHPUnit]]></title>
      <guid>http://www.phpdeveloper.org/news/17173</guid>
      <link>http://www.phpdeveloper.org/news/17173</link>
      <description><![CDATA[<p>
In <a href="http://edorian.posterous.com/textual-code-coverage-information-for-phpunit">a new post</a> to his blog <i>Volker Dusch</i> points out a new feature in a recent release of <a href="http://phpunit.de">PHPUnit</a>, the popular unit testing framework for PHP - textual code coverage details.
</p>
<blockquote>
Three weeks ago PHPUnit 3.6 was released and it has a little new feature you might have missed until now. PHPUnit can now show you code coverage information on the command line.
</blockquote>
<p>
Options for the report output include: colorizing, writing the output to a file, including a project summary, namespace separation and package (using the @package phpdoc tag) information. He includes a use case he's found for it - small projects where you can cover the whole codebase quickly (with a "watch" command example filtering based on a certain class).
</p>]]></description>
      <pubDate>Fri, 25 Nov 2011 16:11:41 -0600</pubDate>
    </item>
  </channel>
</rss>
