NULL is NULL
NULL is EMPTY
NULL is FALSE
NULL has a sizeof 0

BUT

FALSE is not NULL
FALSE is EMPTY
FALSE is FALSE
FALSE has a sizeof 1

AND

empty ARRAY is not NULL
empty ARRAY is EMPTY
empty ARRAY is FALSE
empty ARRAY has a sizeof 0

$test=NULL;
if(is_null($test)){print("NULL is NULL");}else{print("NULL is not NULL");}
// NULL is NULL
if(empty($test)){print("NULL is EMPTY");}else{print("NULL is not EMPTY");}
// NULL is empty
if($test){print("NULL is TRUE");}else{print("NULL is FALSE");}
// NULL is FALSE
print(count($test));
// 0
$test=false;
if(is_null($test)){print("FALSE is NULL");}else{print("FALSE is not NULL");}
// FALSE is not NULL
if(empty($test)){print("FALSE is EMPTY");}else{print("FALSE is not EMPTY");}
// FALSE is EMPTY
if($test){print("FALSE is TRUE");}else{print("FALSE is FALSE");}
// FALSE is FALSE
print(count($test));
// 1
$test=array();
if(is_null($test)){print("empty ARRAY is NULL");}else{print("empty ARRAY is not NULL");}
// empty ARRAY is not NULL
if(empty($test)){print("empty ARRAY is EMPTY");}else{print("empty ARRAY is not EMPTY");}
// empty ARRAY is EMPTY
if($test){print("empty ARRAY is TRUE");}else{print("empty ARRAY is FALSE");}
// empty ARRAY is FALSE

As Jedi

• phpunit and code coverage
• phing deployment
• svn and continuous integration

As Padawan

• Working agile
• Scrum

Now let’s decide a timeline

I had several:

Generating code coverage report, this may take a moment.PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 21503527 bytes) in /usr/share/php/PHPUnit/Util/Report/Node/File.php on line 406

And here is how it started:

At work we are using phpunit to test our framework, we flew from SimpleTest as there was no real integration with our tools and no real followup of the the product.

So to automate the test, as there is no “build” in php (interpreted vs compiled remember?) we ran it after each commit …

Until it tooks 30 minutes to run throught the whole set of tests…

Then we decided to run it locally before comitting… until it tooks up to 2 hours to run tests (yes we have slow laptops I know, at least 4 times slower than the servers).

Actually we use phpunit for recipe test, including database change, third parties, providers… everything from A to Z… and that needs a lot of time and CPU power…

So we solved the problem by running test in a cronjob, hourly on the integration server.

This was done running phpunit in command line


> phpunit --include-path ../code/ MyTestSuite.php


Of course as we had several tests suites and we had to put them all in one bigger testsuite… but that was not easy so we moved to the Phpunit config file, added code coverage reporting and send a mail everytime sometimes goes wrong

PhpunitConfig.xml

<?xml version="1.0" encoding="UTF-8"?>
<phpunit
         colors="true"
         >
         <testsuites>
         	<testsuite name="RTBF_Service">
         		<file>RTBF/Service/Rating/Adapter/AbstractPhpunittest.php</file>
         		<file>RTBF/Service/Rating/Adapter/MediaPhpunittest.php</file>
         	<--! ... -->
         	</testsuite>
         	<testsuite name="RTBF">
         		<file>RTBF/AclPhpunittest.php</file>
         	</testsuite>
         	<testsuite name="RTBF_Utility">
         		<file>RTBF/Utility/AjaxConnectorPhpunittest.php</file>
	         	<--! ... -->
         	</testsuite>
         	<--! ... -->
	</testsuites>
	<listeners>
  		<listener class="SimpleTestListener" file="PhpunitTestListener.php">
  		</listener>
  	</listeners>
  	<!--
	<logging>
		<log type="coverage-html" target="/reporting/phpunit/library/" charset="UTF-8" />
	</logging>
	-->
	<php>
		<ini name="memory_limit" value="2047M" />
	</php>
	<filter>
	  <blacklist>
	    <directory suffix=".php">library/code/Zend</directory>
	  </blacklist>
	</filter>
</phpunit>

PhpunitTestListener.php

class SimpleTestListener implements PHPUnit_Framework_TestListener
{
	private $emailContent=array(self::Error=>"",self::Failure=>"",self::Incomplete=>"",self::Skipped=>"");
	private $assertions=0;
	private $itemCount=array(self::Error=>0,self::Failure=>0,self::Incomplete=>0,self::Skipped=>0);
	private $totalItems=0;

	const Error="Error";
	const Failure="Failure";
	const Incomplete="Incomplete";
	const Skipped="Skipped";

	private function addEmailContent($severity,$test,$e){
		$result = $test->getResult();
		$traces = $e->getTrace();
		$continue=true;
		$tracingMessage="";
		for($i=1;$i<count($traces)&&$continue;$i++){
			if(isset($traces[$i]['file'])){
				$tracingMessage.=$traces[$i]['file'].":(".$traces[$i]['line'].")\n\t";
			}else{
				$continue=false;
			}
		}
		$this->itemCount[$severity]++;
		$this->emailContent[$severity].=$this->itemCount[$severity].")\t".get_class($test).'::'.$test->getName(TRUE)."\n\t".str_replace("\n","\n\t",PHPUnit_Framework_TestFailure::exceptionToString($e))."".$tracingMessage."\n\n";
		$this->totalItems++;
	}

	public function addError(PHPUnit_Framework_Test $test,Exception $e,$time){
		$this->addEmailContent(self::Error,$test,$e);
	}

	public function addFailure(PHPUnit_Framework_Test $test,PHPUnit_Framework_AssertionFailedError $e,$time){
		$this->addEmailContent(self::Failure,$test,$e);
	}

	public function addIncompleteTest(PHPUnit_Framework_Test $test,Exception $e,$time){
		$this->addEmailContent(self::Incomplete,$test,$e);
	}

	public function addSkippedTest(PHPUnit_Framework_Test $test,Exception $e,$time){
		$this->addEmailContent(self::Skipped,$test,$e);
	}

	public function startTest(PHPUnit_Framework_Test $test){
	}

	public function endTest(PHPUnit_Framework_Test $test, $time){
	}

	public function startTestSuite(PHPUnit_Framework_TestSuite $suite){
	}

	public function endTestSuite(PHPUnit_Framework_TestSuite $suite){
	}

	public function __destruct(){
		if($this->totalItems>0){
			// HIDDEN but concat everything from $this->emailContent nicely and send the mail
			//print("\n\nMail sent: ".$text."\n");
		}
	}
}

That’s it for the big picture…

And as you can see there are several point in the XML that are quite important:

memory limit 2047MBthat’s huge… but this is the price to pay to have a fully working code-coverage HTML report. As we are using suhosin we had to change the memory limit in suhosin too… and yes when the limit is 2048 MB don’t try to set the memory to 2048 MB it really means this is a limit you have to be under that limit (here 2047 MB).

2 Gigs!!! I know this is huge but believe me I went through several tries and 128 MB was not enought, nor 256 MB, nor 512 MB, not even 1 GB … I didn’t try to see where is my limit … I put 2 gigs and then it worked… we have about 30% of lines covered so I think that if we shift to 100% we will have to give more memory… I’m pretty sure, there is something leaking somewhere… but according to phpunit.de site… I have the answer remains: Give more memory

/etc/php5/conf.d/suhosin.ini

logging is commented out because logging needs xdebug and while we stay with ZendServer CE we do not have xdebug… (see my previous post for more info).

But the server which is not running Zend Server CE does!

So I commented out the line in the config to let developers run the unit test and pasted it as command line argument on the server’s cronjob.

phpunit --include-path ../code/ --coverage-html /reporting/phpunit/library/ --configuration PhpunitConfig.xml

the listener This is a simple easy listener. It’s always useful to have one sample so I pasted here above, feel free to copy, enhance… The only ‘hack’ we use it to call the send email on listener destruction, so the email will be sent at the end. But there is a drawback… if there is a php error somewhere, nothing is sent. And as nothing is sent when everythign goes well… we dont know if everythings goes well or if there is a real bug…
This problem will be addressed later. Stay tuned!

user@laptop:~$ sudo bash

1st be sre to have the pecl, pear available as root in command line

root@laptop:~# PATH=$PATH:/usr/local/zend/bin

trying to install

root@laptop:~# pecl install xdebug
downloading xdebug-2.1.0.tgz ...
Starting to download xdebug-2.1.0.tgz (301,354 bytes)
.....................................................done: 301,354 bytes
66 source files, building
running: phpize
Configuring for:
PHP Api Version: 20041225
Zend Module Api No: 20060613
Zend Extension Api No: 220060519
Cannot find autoconf. Please check your autoconf installation and the
$PHP_AUTOCONF environment variable. Then, rerun this script.

ERROR: `phpize' failed

Argl it seems to be failing…

looks like autoconf is missing

root@laptop:~# autoconf
The program 'autoconf' can be found in the following packages:
* autoconf
* autoconf2.13
Try: apt-get install <selected package>


ok let’s add it:


root@laptop:~# apt-get install autoconf


and now let’s try again


root@laptop:~# pecl install xdebug
downloading xdebug-2.1.0.tgz ...
Starting to download xdebug-2.1.0.tgz (301,354 bytes)
.............................................................done: 301,354 bytes
66 source files, building
running: phpize
Configuring for:
PHP Api Version: 20041225
Zend Module Api No: 20060613
Zend Extension Api No: 220060519
configure.in:3: warning: prefer named diversions
configure.in:3: warning: prefer named diversions
building in /var/tmp/pear-build-root/xdebug-2.1.0
running: /tmp/pear/temp/xdebug/configure
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for a sed that does not truncate output... /bin/sed
checking for cc... cc
...
Build process completed successfully
Installing '/usr/local/zend/lib/php_extensions/xdebug.so'
install ok: channel://pecl.php.net/xdebug-2.1.0
configuration option "php_ini" is not set to php.ini location
You should add "extension=xdebug.so" to php.ini


Great!

Don’t forget to add the librairy in the php.ini

create the xdebug.ini in the ext.d directory and the symlink in the conf.d directory


root@laptop:/usr/local/zend/etc/ext.d# more xdebug.ini
zend_extension=/usr/local/zend/lib/php_extensions/xdebug.so
; You may put any extension-specific directives here

root@laptop:/usr/local/zend/etc/conf.d# ln -s ../ext.d/xdebug.ini xdebug.ini


Now let’s try PHP:

scips@laptop:~$ php
Segmentation fault


Looks like I need to investigate deeper…

Ok problem solved:

Instructions

Warning: You seem to be using Zend Server, which is known to cause issues with Xdebug. It might work, but you’re on your own.

Download xdebug-2.1.0.tgz
Unpack the downloaded file with tar -xvzf xdebug-2.1.0.tgz
Run: cd xdebug-2.1.0
Run: phpize

As part of its output it should show:

Configuring for:
…
Zend Module Api No: 20060613
Zend Extension Api No: 220060519
If it does not, you are using the wrong phpize. Please follow this FAQ entry and skip the next step.

Run: ./configure
Run: make
Run: cp modules/xdebug.so /usr/local/zend/lib/php_extensions
Open /usr/local/zend/etc/conf.d/debugger.ini and put a ; in front of the line that says zend_extension_manager.dir.debugger= so that it says ;zend_extension_manager.dir.debugger=
Edit /usr/local/zend/etc/php.ini and add at the begining of the file the line
zend_extension = /usr/local/zend/lib/php_extensions/xdebug.so

I did just paste in has requested my php -i output on http://xdebug.org/find-binary.php then compiled and everything ran fine.

The problem is that you have to use one or the other not the both at the same time… still not a real option for me.

You have a little problem?

This is The solution (thanks to @DwebConsulting).

1. sudo service mysql stop
2. sudo cp /etc/mysql/my.cnf /etc/mysql/my.cnf.bak
3. sudo cp /etc/mysql/debian.cnf /etc/mysql/debian.cnf.bak
4. sudo vim /etc/mysql/my.cnf
   1. replace every line starting with “socket =” by “socket = /tmp/mysql.sock”
5. sudo vim /etc/mysql/debian.cnf
   1. replace every line starting with “socket =” by “socket = /tmp/mysql.sock”
6. sudo service mysql start

in the Zend Server CE admin (http://localhost:10081/ZendServer/) > Server Setup > Directives >
Search for default_socket and in mysql and mysqli remove the content of the textarea (empty value => default value used instead)
Then click Save Changes and click Restart PHP

It will work until Zend Server CE bug is fixed (release 5.0).

<?php
for($i=a;$i&lt;=z;$i++) echo("$i\n");
?>

And what’s the difference with?

<?php
for($i=a;$i&lt;z;$i++) echo("$i\n");
?>

Why is the result different? and How?
…
Worst:

<?php
$i=a;
while(strcmp($i,z)<=0){
   echo($i."\n");
   $i++;
}
?>

Gives exactly the same result as the second exemple.
…

hints:
http://www.php.net/manual/en/language.types.string.php#language.types.string.conversion
http://www.php.net/manual/en/language.operators.comparison.php
http://www.php.net/manual/en/language.types.string.php

Session process:

1. Problem choosing (5 min)
2. Problem discussion (10 min)
3. Coding session (1h)
4. Retrospective (10 min)

2 Style of coding sessions:

• Randori dojo
• Prepared Kata

Session roles:

• Moderator: Moderating the discussion, conducting the retrospective
• Organizer: Room Reservation, setting up computer, projector, sending reminder, preparing the program, cleaning the room
• Scribe: Publishing and sharing the result of the meeting, taking photo, video…
• Participants: Maximum 16 (including Moderator/Organize/Scribe)

Principles:

• TDD
• Time Boxing (strictly 7 min / programming pair)
• Time Boxed Discussion Break
• Silence during Randori
• Everyone must be in a programming pair
• Use only the software hardware prepared fot the session

See also: www.codingdojo.org