<?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>Fri, 09 Jan 2009 22:51:17 -0600</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Sebastian Bergmann's Blog: Distributed Testing with PHPUnit 3.1]]></title>
      <guid>http://www.phpdeveloper.org/news/7331</guid>
      <link>http://www.phpdeveloper.org/news/7331</link>
      <description><![CDATA[<p>
In his latest post, <i>Sebastian Bergmann</i> <a href="http://sebastian-bergmann.de/archives/659-Distributed-Testing-with-PHPUnit-3.1.html">spotlights another new feature</a> of the upcoming <a href="http://www.phpunit.de/">PHPUnit</a> release - distributed testing.
</p>
<blockquote>
One of the new features in the upcoming <a href="http://www.phpunit.de/">PHPUnit 3.1</a> release is the support for distributed testing through the ability to log test result and code coverage data to a database. This way, the same test suite can be run on different platforms with the results being aggregated in the database. For this to work, however, we need a key in the database that identifies test runs from different machines as being related. A <a href="http://subversion.tigris.org/">Subversion</a> revision number is a perfect candidate for this.
</blockquote>
<p>
He <a href="http://sebastian-bergmann.de/archives/659-Distributed-Testing-with-PHPUnit-3.1.html">includes a sample script</a> that helps with the storage of the results in the database by grabbing a unique id for the machine pushing the updates in.
</p>]]></description>
      <pubDate>Thu, 22 Feb 2007 12:14:00 -0600</pubDate>
    </item>
  </channel>
</rss>
