<?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 07:39:01 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Sebastian Bergmann's Blog: Even More Work on Reporting in PHPUnit 3]]></title>
      <guid>http://www.phpdeveloper.org/news/5589</guid>
      <link>http://www.phpdeveloper.org/news/5589</link>
      <description><![CDATA[<p>
<i>Sebastian Bergmann</i> has a <a href="http://www.sebastian-bergmann.de/blog/archives/604-Even-More-Work-on-Reporting-in-PHPUnit-3.html">new post</a> on his blog today with even more details on the reporting that's to come with the next version of PHPUnit, version 3.
</p>
<blockquote>
<p>
When I moved to Norway just over a month ago, the Code Coverage Reporting of PHPUnit 3 needed almost six hours to run the test suite and generate a Code Coverage report for the eZ components.
</p>
<p>
Then Derick Rethans committed a patch to [...] reduce the time spent on running the tests dramatically. It now took only two hours to run the test suite and generate the report.
</p>
<p>
Over the past couple of days, Michael Lively Jr., Jan Kneschke, and myself optimized some hot spots in PHPUnit3 moving the initial six hours have been reduced to eight minutes.
</p>
</blockquote>
<p>
Many congrats to <i>Sebastian</i> and <a href="http://www.sebastian-bergmann.de/blog/archives/604-Even-More-Work-on-Reporting-in-PHPUnit-3.html">the crew that helped</a> make such a dramatic change in the code coverage report creation! He also notes there's a logger to come to manage the information gathered via the tests (into a SQLite database).
</p>]]></description>
      <pubDate>Wed, 14 Jun 2006 19:34:06 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Sebastian Bergmann's Blog: More Work on Reporting in PHPUnit 3]]></title>
      <guid>http://www.phpdeveloper.org/news/5350</guid>
      <link>http://www.phpdeveloper.org/news/5350</link>
      <description><![CDATA[<p>
<i>Sebastian Bergmann</i> has posted <a href="http://www.sebastian-bergmann.de/blog/archives/599-More-Work-on-Reporting-in-PHPUnit-3.html">several new screenshots</a> of the new reporting feature of the upcoming PHPUnit 3 release, completed via a patch from <i>Michael Lively Jr.</i>
</p>
<quote>
<i>
<p>
Michael Lively Jr. sent me a <a href="http://news.php.net/php.pear.cvs/40068">patch</a> last night that implements most of the bits and pieces that were still missing from the new <a href="http://www.sebastian-bergmann.de/blog/archives/578-Code-Coverage-Reports-with-PHPUnit-3.html">reporting functionality</a> in <a href="http://www.sebastian-bergmann.de/blog/archives/553-PHPUnit-3.0.html">PHPUnit 3</a>.
</p>
<p>
When you compare the current version of the reporting to the <a href="http://www.sebastian-bergmann.de/blog/archives/578-Code-Coverage-Reports-with-PHPUnit-3.html">original version</a> you will notice that I changed the color scheme. It now uses colors from the <a href="http://tango-project.org/Tango_Icon_Theme_Guidelines">Tango Palette</a>.
</p>
</i>
</quote>
<p>
The <a href="http://www.sebastian-bergmann.de/blog/archives/599-More-Work-on-Reporting-in-PHPUnit-3.html">screenshots</a> include views of the summary page, a detail view of the same (and more) information, example test results output, and the code coverage for an internal class.
</p>]]></description>
      <pubDate>Thu, 11 May 2006 05:53:17 -0500</pubDate>
    </item>
  </channel>
</rss>
