Re: Please contact package maintainer before to do something
| From: | Laurent Laville | Date: | Tue, 03 Jan 2012 11:11:54 +0000 |
| Subject: | Re: Please contact package maintainer before to do something | ||
| References: | 1 2 3 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-5992@lists.php.net to get a copy of this message | ||
Le 03/01/2012 10:54, Daniel O'Connor a écrit :
Of course the include_path may solve this issue, tests suites may failed on others machine if include_path is not set as expected. I prefer to use a solution like the XML phpunit configuration file With such mini content <phpunit bootstrap="../Net/Growl/Autoload.php"> </phpunit> And launcher, for example like : C:\home\pear\Net_Growl\trunk>phpunit -c tests/phpunit.xml tests/ PHPUnit 3.6.7 by Sebastian Bergmann. Configuration read from C:\home\pear\Net_Growl\trunk\tests\phpunit.xml ..................... Time: 1 second, Memory: 5.00Mb OK (21 tests, 82 assertions) What do you think of this proposal ?And I'm not sure this is the right solution applied here.http://test.pear.php.net:8080/job/Net_Growl/ For some time, no tests could execute. Having a 'Net' and executing the tests from the top level dir means that the include_path of . will pick up the right files - you can see build #10 started working.