Re: Tests

Lukas Smith wrote: > Specifically the limitations (compared to phpt) would be of interest > and if these can be overcome. I don't see the differences as limitations. I don't think, though, that we should use .phpt for PEAR, but rather use PHPUnit, for instance like this: cvs.php.net/ pear/ AllTests.php A_Package/ tests/ AllTests.php ... pear/AllTests.php would aggregate the Test Suites defined by the individual packages' AllTests.php files into one Test Suite containing a Test Suite for each PEAR package. pear/AllTests.php could then be executed by the TextUI Test Runner using a cronjob generating an XML-based logfile, that can be transformed using XSLT (or XML_Transformer ;-) to something we can put up on pear.php.net (whatever happended to automatically generated API documentation, btw.?). > Also what is the status of phpunit in regards to php4? The PHPUnit 0.x version (ZEND_ENGINE_1 branch in CVS) is stable and a feature-complete implementation of junit.framework with a partial implementation of junit.extensions for PHP 4. Test Cases written for PHPUnit 0.x will work (after chaning one line of code) with PHPUnit 1.x (a/k/a. the PHP 5 version) without hassle. -- Sebastian Bergmann http://sebastian-bergmann.de/ http://phpOpenTracker.de/ http://www.professionelle-softwareentwicklung-mit-php5.de/