<?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, 21 May 2013 19:51:55 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[DZone.com: Contributing to Paratest]]></title>
      <guid>http://www.phpdeveloper.org/news/19278</guid>
      <link>http://www.phpdeveloper.org/news/19278</link>
      <description><![CDATA[<p>
On DZone.com today there's an update about <a href="http://css.dzone.com/articles/contributing-paratest">recent additions to Paratest</a>, the parallel PHPUnit test runner (created by <a href="https://github.com/brianium/paratest">Brian Scaturro</a>). He talks some about the benefits of running tests in parallel and shares some of the recent contributions to the project from other developers.
</p>
<blockquote>
I've already written about <a href="http://css.dzone.com/articles/parallel-phpunit">my experiments with Paratest</a>. Paratest is a PHPUnit wrapper that allows you to run tests written for PHPUnit in parallel, making us of multiple processes running on the same machine. In a world where cycle time is an important metric, trading resources to get the test suite to finish earlier is a net gain; especially when you're stepping on unstable stones and run the suite very often.
</blockquote>
<p>
He (<i>Giorgio Sironi</i>) has contributed a new test runner to the project - the "WrapperRunner" that limits the number of processes spawned by the parallel testing tool. Another contribution came from <i>Dimitris Baltas</i> involving the addition of a <a href="https://github.com/brianium/paratest/pull/23">TEST_TOKEN variable</a> that can be used to uniquely identify each process as they're executing.
</p>]]></description>
      <pubDate>Wed, 06 Mar 2013 10:16:00 -0600</pubDate>
    </item>
  </channel>
</rss>
