<?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, 06 Jan 2009 09:13:43 -0600</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Sebastian Bergmann's Blog: Isolated (and Parallel) Test Execution]]></title>
      <guid>http://www.phpdeveloper.org/news/9281</guid>
      <link>http://www.phpdeveloper.org/news/9281</link>
      <description><![CDATA[<p>
<i>Sebastian Bergmann</i> <a href="http://sebastian-bergmann.de/archives/730-Isolated-and-Parallel-Test-Execution.html">points out</a> a new feature that <a href="http://www.phpunit.de/">PHPUnit</a> (the popular PHP unit testing tool) now has - <a href="http://www.phpunit.de/browser/phpunit/branches/feature/parallel_test_execution">parallel_test_execution</a> allowing for each test to execute on a separate PHP process.
</p>
<blockquote>
The advantages of this include full test isolation and the fact that a test can now cause a PHP fatal error or even a segmentation fault of the PHP interpreter without interrupting the test execution.
</blockquote>
<p>
He does mention, however, that it can cause a bit more overhead for larger testing suites since it needs to create a new process (complete with memory usage) for each running test. There are also coding issues that could be thrown off by this option (he gives an example of an inheritance issue with eZ Components).  
</p>
<p>
He also notes some of his thoughts on how to control/configure the process (like in a configuration file) and via an "@isolated" notation to make it easy to do it dynamically.
</p>]]></description>
      <pubDate>Wed, 19 Dec 2007 15:26:00 -0600</pubDate>
    </item>
  </channel>
</rss>
