Re: External Dependencies

Lukas Smith wrote:

so i would say if there is anything significant missing for your target platform from either phpt or phpunit go head and use some external tool. but dont include it in the package tgz.

A couple of remarks on the regression testing topic: phpt are NOT really documented on the PEAR site, I had trouble finding how to run them. Aidan Lister told me that he heard there was work in progress to improve the documentation. Any idea when that'll be done. He also pointing me to the run-tests script. Not very user friendly, I may say. I had to setup a dummy test structure and wrote a simple .BAT file to run it under Windows without too much pain. So I understand that could "scare" a lot of people off... (More in the topic of this thread) IMHO, test tools shouldn't really be part of the dependency of the package itself... from the user standpoint at least. Have a look at PHPUnit and list of packages that depend on it... Should they really be there? If in the future phpt or PHPUnit2 are mandated for all PHP5 packages, it will be extra work to convert test suites built around other tools for previous versions of the packages. Packages are already time-consuming enough to maintain as-is, without adding a burden of test suite conversion... So if external test suites are accepted, then a strong warning should be given of that risk of extra work. If SimpleTest if not fundamentally different then PHPUnit, then shouldn't PEAR "competition" rule also apply? -Philippe