Do you disagree with the notion then that building a reusable set up with: CruiseControl PHPCodeSniffer (PEAR) PHPUnit PHPDoc
and maybe your own scripts rather shell or php to integrate them all together is as "simple" to use for the common, non-elaborate, shop though? Take into account now bug tracking, subversion control, database table structures in the migrations, etc. On Fri, May 2, 2008 at 11:59 AM, Marco <[EMAIL PROTECTED]> wrote: > I use Cruisecontrol in collaboration PHPCodeSniffer, PHPUnit, PHPDoc to > generate both unit test suite results, API documentation and coding > standards violation reports etc. > > I've found it works very well for both automated nightly builds and also > on request builds using a simple web interface. > > Regards > > Marco >
