Share » Forums » Developer » Unit testing

Unit testing

Unit testing

Friday 29 October 2010 1:44:00 am - 4 replies

Modified on Friday 29 October 2010 1:54:56 am by Jean-Luc Chassaing

Author Message

Jean-Luc Chassaing

Friday 29 October 2010 2:58:23 am

OK let me give here some more things.

I've fixed my previous problem by adding a require_once in the runtest.php file.

But There's something I still can't get through. looks like I'm not using the right phpunit release !??

here's the error message I'm getting now :

Call to undefined method PHPUnit_Util_Filter::addDirectoryToFilter() in runtest.php on line 22

but in fact the addDirectoryToFilter method doesn't exist in PHPUnit/Util/Filter.php where the PHPUnit_Util_Filter class is declared.

I thought using unit test would be easy but I' m wasting my time trying to fix does problems..

Any help would really be great !

André R.

Friday 29 October 2010 3:28:38 am

Our unit testing code is not yet compatible with 3.5 because of some bc (Backward compatibility) issues.

See sdk-public mailing list archive, there was a thread about it with possible patches a few weeks back.

eZ Online Editor 5: || eZJSCore (Ajax): || eZ Publish EE


Friday 29 October 2010 5:39:30 am




Brookins Consulting |
Certified |
Solutions |
eZpedia community documentation project |

Jean-Luc Chassaing

Friday 29 October 2010 6:45:32 am

Tank you for the help...

Well I found out that there is something more with the 3.5.x release the :

PHPUnit_Util_Filter::addDirectoryToFilter( getcwd() . '/tests' );

can't be used, the addDirectoryTyFilter method has been removed. It has to be replaced by :

PHP_CodeCoverage_Filter::getInstance()->addDirectoryToBlacklist(getcwd() . '/tests');

but the fact is I think I've all messed it up...

I'm trying to downgrade to an older release 3.4 but now the test/runtest.php script is insulting me telling that an unexpected error has occurred ... that's great !

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu