Manuel Pichler - phpundercontrol

phpUnderControl 0.6.0beta2 released

nospam@example.com (Manuel Pichler) — Thu, 10 Jun 2010 12:25:00 +0200

Today I have released the second beta version of phpUnderControl. Beside several minor tweaks and bug fixes, this release contains one additional feature I was asked for during the IPC in Berlin. This feature allows you to specify a maximum number of log entries that will be shown in the generated metric charts. This can be very useful once you have a project with a great amount of builds and the chart rendering gets slower and slower.

This feature adds a new option --max-number to phpUnderControl's chart command. To rebuild all your charts you can call phpUnderControl's shell script with the following command:

  mapi@arwen ~ $ phpuc --force-update --max-number 42 \
                 /opt/cruisecontrol/logs/phpUnderControl \
                 /opt/cruisecontrol/logs/phpUnderControl

You can get the latest release of phpUnderControl through its pear channel:

  mapi@arwen ~ $ pear upgrade --alldeps phpuc/phpUnderControl-0.6.0beta2
  Starting to download phpUnderControl-0.6.0beta2.tgz (546,314 bytes)
  ...................................................................
  .............................done: 546,314 bytes

or you can get the latest development version on github.

Artikel zum Thema Softwaremetriken

nospam@example.com (Manuel Pichler) — Wed, 12 May 2010 09:04:12 +0200

This blog post is in German as the mentioned article was published in German.

In der heute erschienenen Ausgabe 4.10 des PHP Magazins ist auch ein Artikel von mir enthalten, und wie sollte es wohl anders sein *Trommelwirbel*, beschäftigt der sich mit dem Thema Softwaremetriken In diesem Artikel gibt es eine sehr ausführliche Einführung in die Thematik, mit eine Reihe von praktischen Beispielen und den daraus ableitbaren Aussagen über den untersuchten Quelltext.

Über Kommentare, Anregungen und Kritik rund um den Artikel würde ich mich sehr freuen. Und sollte euch der Artikel gefallen haben, empfehle ich die Internationale PHP Conference 2010, die vom 30. Mai bis 2. Juni in Berlin stattfindet, an der ich teilnehmen und zwei Vorträge halten werden.

PHP-Magazin Artikel zum Thema Softwaremetriken

nospam@example.com (Manuel Pichler) — Wed, 12 May 2010 09:04:12 +0200

This blog post is in German as the mentioned article was published in German.

Goodbye Cologne

nospam@example.com (Manuel Pichler) — Thu, 29 Apr 2010 13:20:00 +0200

As many of you may already have noticed, there will be a big change in my career as a professional software engineer and architect this summer. Together with Kore and Toby I am in the process of founding a company. The focus of this company will be on services all around the whole quality life cycle in PHP projects.

Under the hood of our company we will also offer support, trainings and consulting for several quality assurance tools, like pdepend, phpmd and phpUnderControl. For you, this opens a great opportunity. You can use the tools and the documentation, as well as participate in the community, as usual. But from now on you can also purchase professional support, if you get stuck or need general assitance. And when you miss a feature or need an individual extension for one of these tools, don't hesitate to contact us.

I am really excited what cool things will happen in the next couple of years and I am looking forward to cowork with professionals like Toby and Kore.

To finalize the little marketing for the company and its services I would appreciate to meet you, your colleagues and your compmany, to give presentations or into-depth trainings on one of the tools or on quality assurance in general.

phpUnderControl 0.5.1 released

nospam@example.com (Manuel Pichler) — Sun, 31 Jan 2010 21:16:35 +0100

Today I have released phpUnderControl version 0.5.1. It's a bug fix release that closes several issues open since a long time. First of all I would like to thank Sebastian Marek who was the main contributor to this releases, so a big thankyou to you.

Now phpUnderControl should work with CruiseControl 2.8.3. Thanks to Mike van Riel who provided some hints on this issue in a blog comment.
Fixed #983: Graph unitests throw fatal error when ezComponents not available.
Fixed #966: phpcs-details.xsl not showing file name.
Closed #863: Destination option is now deprecated.
Fixed #862: Command line switches without parameter don't work.
Fixed #861: Password is used as username in check outs. This patch was supplied by Thorsten Daners via e-mail.
Fixed #734: Now the build dropdown redirects to the correct build uri.
Implemented #703: PHPUnit test results are now the first entry on the project overview page.
Fixed #700: Throw an exception when the specified project does not exist.
Implemented #675: Use "php -l" for lint checking and not PHPUnit.
Implemented #625: Integrate PHP_Depend results.

Beside the new release some more things have changed. From now on the phpUnderControl development is hosted on github. This means that from now on the latest version of phpUnderControl can be obtained with the following command:

mapi@arwen ~ $ git clone \
               git://github.com/manuelpichler/phpUnderControl.git

Additionally we have moved the phpUnderControl's PEAR Channel Server from pear.phpunit.de to its own server pear.phpundercontrol.org. At this point I would like to thank Sebastian for providing phpUnderControl's infrastructure under the PHPUnit umbrella for the last three years.

mapi@arwen ~ $ pear uninstall phpunit/phpUnderControl
mapi@arwen ~ $ pear channel-discover pear.phpundercontrol.org
mapi@arwen ~ $ pear install --alldeps phpuc/phpUnderControl-beta
Starting to download phpUnderControl-0.5.1.tgz (539,717 bytes)
..........................................done: 539,717 bytes
install ok: channel://pear.phpundercontrol.org/phpUnderControl-0.5.1

phpUnderControl 0.5.0 released

nospam@example.com (Manuel Pichler) — Sun, 06 Dec 2009 15:16:00 +0100

After quite some time of silence around phpUnderControl I have bundled the 0.5.0 release today. Beside minor changes, bugfixes and enhancements this release contains one new major feature, the PHP_CodeBrowser.

phpUnderControl integrating PHP_CodeBrowser

The PHP_CodeBrowser is a separate application that collects various XML log files with different project metrics/violations and presents them in a browseable source view with syntax highligting. This tool is a contribution by the Mayflower GmbH, where it was developed and now shared with the Open Source Community. At this point I would like to thank Mayflower as a whole and in particular at Elger and Thorsten, which were responsible for all technical aspects of this contribution.

To use the PHP_CodeBrowser you must add an additional execute publisher to your CruiseControl config.xml file that generates the PHP_CodeBrowser html report and an additional artifacts publisher to move the generated PHP_CodeBrowser report into the projects artifacts directory.

<?xml version="1.0" encoding="UTF-8" ?>
<cruisecontrol>
  <!-- ... -->
  <project name="PHP_Depend" buildafterfailed="false">
    <!-- ... -->
    <publishers>
      <!-- ... -->
      <execute command="phpcb 
        --log projects/${project.name}/build/logs 
        --source projects/${project.name}/source/PHP 
        --output projects/${project.name}/build/php-code-browser"/>
      <artifactspublisher 
        dir="projects/${project.name}/build/php-code-browser" 
        dest="artifacts/${project.name}" 
        subdirectory="php-code-browser"/>
      <!-- ... -->
    </publishers>
  </project>
</cruisecontrol>

But why do we use a CruiseControl publishers instead of a regular ant (Your build tool here) target? The answer is really simple. The PHP_CodeBrowser must be the very last artifact generated for a project, which means it must also run after PHPUnit, to collect the test result logs. But in most setups PHPUnit is configured with failonerror="on" to mark a build as failed, when an error occured during the test execution. But with this configuration a following PHP_CodeBrowser target would never be executed by ant, because the build failed already. This cannot happen with a CruiseControl publisher which is always executed in a separated process.

If you create a new project with phpUnderControl's project command, phpUnderControl will automatically search for an installed PHP_CodeBrowser and add the required publishers to your config.xml file when it is present.

mapi@arwen ~ $ phpuc project \
       --project-name PHP_Depend \
       --source-dir PHP \
       --test-case PHP_Depend_AllTests \
       --test-dir tests \
       --test-file PHP/Depend/AllTests.php \
       --version-control svn \
       --version-control-url http://svn.pdepend.org/branches/0.9.0 \
       /opt/cruisecontrol/cruisecontrol-bin-2.8.2

To get the latest version of phpUnderControl, you can use the PEAR-Channel-Server:

mapi@arwen ~ $ pear channel-discover pear.phpunit.de
mapi@arwen ~ $ pear install phpunit/phpUnderControl-beta

or you can check it out from the subversion repository:

mapi@arwen ~ $ svn co svn://phpunit.de/phpunit/phpUnderControl/trunk

The value of complexity metrics - Cyclomatic Complexity (1/2)

nospam@example.com (Manuel Pichler) — Tue, 07 Jul 2009 21:20:00 +0200

Software metrics are currently on everyone's lips and a frequently discussed topic. There are many conference talks, blog posts and other presentations that talk about software metrics. But to me it seems as if this subject is a closed book for many developers, so I decided to write this little post about a special category of software metrics, the complexity metrics.

Complexity metrics are a theoretical approach to measure the subjective complexity of a software fragment, where the words software fragment stand for a paraphrase for functions, methods, classes and nearly every logical unit that can be found in a software system. The most prevalent procedure to calculate complexity values is static code analysis, where an application parses the raw source code of a project, counts different statements and expressions and packs up the determined results in simple classification numbers. And with this information you already know the main concepts behind most software metrics, classification numbers and counting. As you can see there is no magic behind the scene, the only thing required is a good background knowledge to interpret those values.

The Cyclomatic Complexity Number or short CCN is the oldest complexity metrics. The first time this software metric was mentioned was 1976 by Thomas J. McCabe. This metric counts the available decision paths in a software fragment to determine its complexity. Each decision path starts with one of the conditional statements from the following list, so that it is fairly easy to detect them in existing source code.

?
case
elseif
for
foreach
if
while

A look at this list of statements may result in the questions: Is this list wrong, it doesn't list else and default? But it is correct. The assumption is that both statements will contain the defaut execution path of a program which also exists when there are no special cases to capture.

Each decision path gets the value 1 and the sum of all these values represents the Cyclomatic Complexity of the analyzed software fragment. Note that each function and method also counts with a value of 1 With this knowlegde we can now calculate the complexity of the following example code:

<?php
class CyclomaticComplexityNumber
{
public function exampe( $x, $y ) // (1)
{
if ( $x > 23 || $y < 42 ) // (1)
{
for ( $i = $x; $i >= $x && $i <= $y; ++$i ) // (1)
{
}
}
else
{
switch ( $x + $y )
{
case 1: // (1)
break;
case 2: // (1)
break;
default:
break;
}
}
}
file_exists('/tmp/log') or touch('/tmp/log');
}

Based on the previous definition the Cyclomatic Complexity Number of the example code example is 5. But you may have noticed that this approach does not capture all decision paths that exist. We haven't catched those paths that came from the by the boolean expression || line 6 and && line 8, and the logical or expression in line 25. A variation of the Cyclomatic Complexity Number that also captures those paths is the so called CCN2. The CCN2 is the most widely used variation of this software metrics. Tools like PHPUnit, PMD and Checkstyle report it as Cyclomatic Complexity of an analyzed software fragment.

Now we get a complexity value of 8 when we apply the CCN2 to the previous example, what is a growt of the software's complexity of 60%.

Due to the fact that Cyclomatic Complexity Number was originally invented for procedural programming languages, this definition for the Cyclomatic Complexity Number still misses one element to measure the complexity of an object oriented software system. With the concept of exceptions a software gets additional decision paths for each catch statement used in the source code. While try contains the code for the regular execution code without special cases, similar to else and default statements.

?
&&
||
or
and
xor
case
catch
elseif
for
foreach
if
while

Now that we know what the Cyclomatic Complexity Number is, what can we do with the measured information? We can find the complexity hotspots in a system, for example the top ten artifacts with the highest complexity, but this is only important during an initial analyses phase to get the big picture of an application. For a continuous inspection this information is not so important. A continuous analyses requires thresholds that help to categories calculated values. During the time four values have emerged as good thresholds for the Cyclomatic Complexity Number of a software system.

A software fragment with a CCN value between 1-4 has low complexity.
A complexity value between 5-7 is moderate and still easy to understand.
Everything between 6-10 has a high complexity, while everything greater 10 is very complex and hard to understand.

You may ask, why should I care about the complexity of a software system, where is the value of benefit in this metric?

Mostly the complex parts of an application contain business critical logic. But this complexity has negative impacts on the readability and understandability of source code. Those parts will normally become a maintainence and bug fixing nightmare, because no one knows all the constraints, side effects and what's exactly going on in that part of the software. This situation results in the well known saying "Never touch a running system" which in turn mostly ends in copy&paste programming. The situation can even become more critical when the original author leaves the development team or the company.

Finally a small example how to apply the new knowledge about the Cyclomatic Complexity Number, thresholds and the negative impacts of complex software to an existing development process. The following source listing shows a complex method taken from PHP_Depend's source. This method has a Cyclomatic Complexity Number of 16 and I must admit that the original author needed some time to understand what was going on in this method.

<?php
// ...
private function _countCalls(AbstractCallable $callable)
{
$callT = array(
TokenizerI::T_STRING,
TokenizerI::T_VARIABLE
);
$chainT = array(
TokenizerI::T_DOUBLE_COLON,
TokenizerI::T_OBJECT_OPERATOR,
);
$called = array();
$tokens = $callable->getTokens();
$count = count($tokens);
for ($i = 0; $i < $count; ++$i) {
// break on function body open
if ($tokens[$i]->type === TokenizerI::T_CURLY_BRACE_OPEN) {
break;
}
}
for (; $i < $count; ++$i) {
// Skip non parenthesis tokens
if ($tokens[$i]->type !== TokenizerI::T_PARENTHESIS_OPEN) {
continue;
}
// Skip first token
if (!isset($tokens[$i - 1]) || !in_array($tokens[$i - 1]->type, $callT)) {
continue;
}
// Count if no other token exists
if (!isset($tokens[$i - 2]) && !isset($called[$tokens[$i - 1]->image])) {
$called[$tokens[$i - 1]->image] = true;
++$this->_calls;
continue;
} else if (in_array($tokens[$i - 2]->type, $chainT)) {
$identifier = $tokens[$i - 2]->image . $tokens[$i - 1]->image;
for ($j = $i - 3; $j >= 0; --$j) {
if (!in_array($tokens[$j]->type, $callT)
&& !in_array($tokens[$j]->type, $chainT)
) {
break;
}
$identifier = $tokens[$j]->image . $identifier;
}
if (!isset($called[$identifier])) {
$called[$identifier] = true;
++$this->_calls;
}
} else if ($tokens[$i - 2]->type !== TokenizerI::T_NEW
&& !isset($called[$tokens[$i - 1]->image])
) {
$called[$tokens[$i - 1]->image] = true;
++$this->_calls;
}
}
}

The first thing to do is to make sure that the test suite is good enough to ensure that the required refactorings will not change the public behavior of the component or class. When this is donw and we are sure our that api breaks will be detected by the test suitewe can start to extract logic into separate methods.

The following example shows the result of the refactoring:

<?php
// ...
private function _countCalls(AbstractCallable $callable)
{
$called = array();
$tokens = $callable->getTokens();
$count = count($tokens);
for ($i = $this->_findOpenCurlyBrace($tokens); $i < $count; ++$i) {
if ($this->_isCallableOpenParenthesis($tokens, $i) === false) {
continue;
}
if ($this->_isMethodInvocation($tokens, $i) === true) {
$image = $this->_getInvocationChainImage($tokens, $i);
} else if ($this->_isFunctionInvocation($tokens, $i) === true) {
$image = $tokens[$i - 1]->image;
} else {
$image = null;
}
if ($image !== null) {
$called[$image] = $image;
}
}
$this->_calls += count($called);
}

The subjective feeling of readability heavily depends on the complexity of control structures, as we can see by a comparison of the original and the refactored version of the method example. The new version with its Cyclomatic Complexity Number of 5 is much easier to read and understand.

This text is the first of two blog posts. The second article will give a short introduction into the NPath Complexity You liked this article and you are interested in this and other quality assurence related topics? - Then you should now order your copy of the Book Quality Assurance in PHP Projects. The book talks about nearly all aspect of quality assurence, with practical tips and expert knowledge contributed by certain PHP professionals.

phpUnderControl tutorial

nospam@example.com (Manuel Pichler) — Wed, 25 Feb 2009 15:40:20 +0100

Just now I found in Felix's blog this excellent phpUnderControl tutorial that comes with useful tips and helping scripts. Because I think it is a really good source to get started with phpUnderControl I will link it here.

phpUnderControl 0.4.7 released

nospam@example.com (Manuel Pichler) — Sun, 30 Nov 2008 13:31:38 +0100

Bug fix: CC is compatible with Java 1.5, but the phpUnderControl 0.4.6 sources were compiled against Java 1.6.

Visit phpUnderControl's download page for release packages.

phpUnderControl 0.4.6 released

nospam@example.com (Manuel Pichler) — Sun, 23 Nov 2008 21:14:16 +0100

Fixed #621: phpUnderControl dashboard is broken with CruiseControl 2.8 - [4085]
Closed #609: Use artifacts directory for artifacts - [4118]
Closed #611: opera: code coverage not visible - [4119]
Closed #622: phpUnderControl needs a custom error page - [4116]

Documentation error for "merge-phpunit"

nospam@example.com (Manuel Pichler) — Sat, 20 Sep 2008 10:51:47 +0200

There was a documentation error in the previously presented ant build file for the new merge-phpunit command of phpUnderControl. The @failonerror-attribute of the <exec />-tag in the merge target was set to false, which results in not failed CruiseControl builds To fix this behaviour, you must modify the merge target in your build.xml, so that it looks similar to the following example.

<?xml version="1.0" encoding="UTF-8"?>
<project name="phpuc-test" default="build" basedir=".">
....
<target name="merge">
<exec executable="/usr/local/pear/PEAR/bin/phpuc" dir="${basedir}" failonerror="true">
<arg line="merge-phpunit
-b php-5.3.0,php-5.2.6,php-5.2.5
-i ${basedir}/build/tmp/php-5.3.0.xml,${basedir}/build/tmp/php-5.2.6.xml,${basedir}/build/tmp/php-5.2.5.xml
-o ${basedir}/build/logs/log.xml"/>
</exec>
</target>
</project>

Beside this documentation error, there was a bug in version 0.4.3 related to the same topic, which is fixed now. So please make sure you have the latest version (at least 0.4.4) installed.

phpUnderControl 0.4.4 bugfix release

nospam@example.com (Manuel Pichler) — Wed, 10 Sep 2008 21:10:26 +0200

I recently released a bugfix version of phpUnderControl. Beside some minor view errors like the odd/even rows problem, the 0.4.4 release of phpUnderControl fixes a bug in the new merged phpunit logs feature, which doesn't cause CruiseControl to fail for such builds.

phpUnderControl 0.4.3 released

nospam@example.com (Manuel Pichler) — Sun, 07 Sep 2008 19:11:00 +0200

I currently released a new version of phpUnderControl. Beside some minor fixes this release comes with a new feature to aggregate test results of multiple PHPUnit runs.

Use the new cli command merge-phpunit of phpUnderControl to merge multiple log files produced with PHPUnit, as shown in the following example build file for ant.

<?xml version="1.0" encoding="UTF-8"?>
<project name="phpuc-test" default="build" basedir=".">
<target name="build" depends="clean,p5.3.0,p5.2.5,p5.2.6,merge"/>
<target name="clean">
<delete>
<fileset dir="${basedir}/build/tmp">
<include name="*.xml"/>
</fileset>
</delete>
</target>
<target name="p5.2.5">
<exec executable="/usr/local/bin/php525" dir="${basedir}" failonerror="false">
<arg line="/usr/local/pear/bin/phpunit
--configuration ${basedir}/phpunit.xml
--log-xml ${basedir}/build/tmp/php-5.2.5.xml
PhpUnderControl_Example_MathTest source/tests/MathTest.php"/>
</exec>
</target>
<target name="p5.2.6">
<exec executable="/usr/local/bin/php526" dir="${basedir}" failonerror="false">
<arg line="/usr/local/pear/bin/phpunit
--configuration ${basedir}/phpunit.xml
--log-xml ${basedir}/build/tmp/php-5.2.6.xml
PhpUnderControl_Example_MathTest source/tests/MathTest.php"/>
</exec>
</target>
<target name="p5.3.0">
<exec executable="/usr/local/php/bin/php" dir="${basedir}" failonerror="false">
<arg line="/usr/local/pear/bin/phpunit
--configuration ${basedir}/phpunit.xml
--log-xml ${basedir}/build/tmp/php-5.3.0.xml
PhpUnderControl_Example_MathTest source/tests/MathTest.php"/>
</exec>
</target>
<target name="merge">
<exec executable="/home/manu/Desktop/Projects/workspace.xplib.de/phpUnderControl/trunk/bin/phpuc.php" dir="${basedir}" failonerror="false">
<arg line="merge-phpunit
-b php-5.3.0,php-5.2.6,php-5.2.5
-i ${basedir}/build/tmp/php-5.3.0.xml,${basedir}/build/tmp/php-5.2.6.xml,${basedir}/build/tmp/php-5.2.5.xml
-o ${basedir}/build/logs/log.xml"/>
</exec>
</target>
</project>

The following picture shows the phpUnderControl result of such a merged log file:

phpUnderControl merged phpunit log view

Things go on

nospam@example.com (Manuel Pichler) — Wed, 20 Aug 2008 21:26:00 +0200

Even if there is not much noise around phpUnderControl and PHP_Depend at the moment, the development of both projects still goes on. Due to the fact that there are some personal movements in these days I have modified my priorities and everything evolves slower, but I plan to spend more time on these projects, at least from the last quarter of this year.

To put your minds on rest, the next release of phpUnderControl is nearly finished, so stay tuned.

Greetings Manuel

Everything looks fine, but it fails

nospam@example.com (Manuel Pichler) — Sun, 27 Jul 2008 15:14:00 +0200

Yesterday kore asked me about a strange behavior of phpUnderControl. The last arbit build done by phpUnderControl has failed, but when we looked over the different result pages everything looks fine.

phpUnderControl overview page of arbit

Strange! What has happened?

After an analysis session of the 6MB XML log file I detected the following self explaining entry. The PHPUnit tests for arbit had completely failed.

<?xml version="1.0" encoding="UTF-8"?>
<cruisecontrol>
...
<build error=".../arbit/build.xml:20: exec returned: 255" time="12 minutes 56 seconds">
...
<target name="phpunit" time="1 second">
<task location=".../arbit/build.xml:20: " name="exec" time="1 second">
<message priority="debug"><![CDATA[Current OS is Linux]]></message>
<message priority="debug"><![CDATA[Executing 'phpunit' with arguments:
'--log-xml'
'build/logs/phpunit.xml'
'--log-pmd'
'build/logs/phpunit.pmd.xml'
'--log-metrics'
'build/logs/phpunit.metrics.xml'
'--coverage-xml'
'build/logs/phpunit.coverage.xml'
'--coverage-html'
'build/coverage'
'arbitTestSuite'
'source/tests/suite.php'

The ' characters around the executable and arguments are
not part of the command.]]></message>
<message priority="info"><![CDATA[Fatal error: main(): Failed opening required 'modules_tracker_suite.php' (include_path='.../arbit/source/src/:.../arbit/source/src/libraries/:.:.../php-5.3-cvs/lib/php') in .../arbit/source/tests/suite.php on line 0]]></message>
<message priority="info"><![CDATA[Call Stack:]]></message>
<message priority="info"><![CDATA[0.0005 318436 1. {main}() .../php-5.3-cvs/bin/phpunit:0]]></message>
<message priority="info"><![CDATA[0.2345 542264 2. require('.../php-5.3-cvs/lib/php/PHPUnit/TextUI/Command.php') .../php-5.3-cvs/bin/phpunit:44]]></message>
<message priority="info"><![CDATA[1.0595 5278380 3. PHPUnit_TextUI_Command::main() .../php-5.3-cvs/lib/php/PHPUnit/TextUI/Command.php:528]]></message>
<message priority="info"><![CDATA[1.0616 5294940 4. PHPUnit_Runner_BaseTestRunner->getTest() .../php-5.3-cvs/lib/php/PHPUnit/TextUI/Command.php:90]]></message>
<message priority="info"><![CDATA[1.0617 5295224 5. PHPUnit_Runner_BaseTestRunner->loadSuiteClass() .../php-5.3-cvs/lib/php/PHPUnit/Runner/BaseTestRunner.php:200]]></message>
<message priority="info"><![CDATA[1.0617 5295508 6. PHPUnit_Runner_StandardTestSuiteLoader->load() .../php-5.3-cvs/lib/php/PHPUnit/Runner/BaseTestRunner.php:269]]></message>
<message priority="info"><![CDATA[1.0828 5295792 7. PHPUnit_Util_Fileloader::checkAndLoad() .../php-5.3-cvs/lib/php/PHPUnit/Runner/StandardTestSuiteLoader.php:97]]></message>
<message priority="info"><![CDATA[1.1736 5296168 8. PHPUnit_Util_Fileloader::load() .../php-5.3-cvs/lib/php/PHPUnit/Util/Fileloader.php:105]]></message>
<message priority="info"><![CDATA[1.1746 5328364 9. include_once('.../arbit/source/tests/suite.php') .../php-5.3-cvs/lib/php/PHPUnit/Util/Fileloader.php:120]]></message>
</task>
</target>
</build>
...
</cruisecontrol>

Ok, the test run failed, but why did phpUnderControl say: All Tests passed?

The answer is really simple. Due to the fact that phpunit died, it didn't generate any log file and previous log files still reside in build/logs. Because CruiseControl cannot know anything about these outdated build artifacts, it still publishes them as result for last build.

At this moment I realized that I have never mentioned a clean-target for the ant build.xml file, neither in the example file nor in a blog post or the FAQ. So now its time to catch up on this topic.

You should add an additional target to your ant build.xml file, that removes all log files and build artifacts of previous builds, before the main build cycle starts.

<?xml version="1.0" encoding="UTF-8"?>
<project name="phpundercontrol.org" default="build" basedir=".">
...
<target name="clean">

<delete>
<fileset dir="${basedir}/build/logs" includes="**.*" />
</delete>

<delete>
<fileset dir="${basedir}/build/api" includes="**.*" />
</delete>

<delete>
<fileset dir="${basedir}/build/coverage" includes="**.*" />
</delete>
</target>

<target name="build"
depends="clean,checkout,php-documentor,php-codesniffer,phpunit" />
...
</project>

That's it. Now you will get the expected(not really) result: No Tests Run - This project doesn't have any tests.