Re: What I love about CPAN and what I hope PEAR will be

Well we also have to make sure that the tests are not going to be pushing the developers away in a manner that pear proposals are too strict. (Which is somewhat happening already) Although, if we could say that we accept a package, with the condition that there should be tests before a beta release, that'd be great! On 10/22/06, Lukas Kahwe Smith <lsmith@php.net> wrote:

Arnaud Limbourg wrote: Joshua Eichorn wrote:

Peter Beckman wrote:

On Fri, 20 Oct 2006, Alister Bulman wrote:

On 20/10/06, Joshua Eichorn <josh@bluga.net> wrote:

So whats your suggestion for PEAR, the only difference I see at all

is

build server for compiling on multiple distros (which might apply to pecl but doesn't apply to pear) -josh

I'd think the suggestion is: Automatically running unit tests, could get fancy like a Continuous Integration system (that I would love to be able to run with code I'm developing), or something a little simpler like running every X hours/every time code is checked into the PEAR CVS repository - and

it

just emails to the QA mailing list.

Amen. Well put and yes, that's what I'm suggesting. I think the

coding

standards will need to standardize on something so that EVERY package has the tests in a standard way so that automating testing doesn't rely

on

hacks.

The installer has a run-tests command so im guessing the standized way already exists, it just a matter of setting up some automated testing. Seems like it would be pretty easy to grab the code from the installer and do automatic testing of releases. Then its just a matter of adding some reports and formalizing the

process.

But again its the type of project that needs someone to take the first steps on and get the ball rolling. -josh

As a first step we need each project with unit tests to provide an AllTests.php that can be run with pear run-tests. On a related note that might be of interest is what the ZF guys did Yeah, the main challenge/question is how to unify all the different configs, unit test frameworks etc used under a common enough interface to make it possible to run automated tests. I guess that is what that AllTests.php file is about? regards, Lukas -- PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php

-- David Coallier, Founder & Software Architect, Agora Production (http://agoraproduction.com) 51.42.06.70.18