Re: Re: Daily updated unit tests and code coverage forPEAR

Hi Sebastian,

Was wondering if there is a wiki page anywhere explaining
the conventions tests must follow in order to be capable of
aggregation into your test runs?

I think a PEAR top-level AllTests.php is sorely missing and
pulling in more classes (even if it means someone editing
current tests, or adding tests if non-existent) is well
worth the effort.

Paddy
 
Pádraic Brady
http://blog.astrumfutura
.com
http://www.patternsforp
hp.com


----- Original Message ----
From: Sebastian Mendel <listssebastianmendel.de>
To: pear-devlists.php.net
Sent: Tuesday, July 17, 2007 4:32:11 PM
Subject: Re: [PEAR-DEV] Re: Daily updated unit tests and
code coverage forPEAR

Sebastian Mendel schrieb:
> Christian Weiske schrieb:
>> Sebastian,
>>
>>
>>>> You can find them at
>>>> http://pear.cwe
iske.de/unittests-cvs/
>>> not very daily ... 
>> And your package is one of the offending packages.
>>
>> $ phpunit SQL_Parser_AllTests AllTests.php
>> PHPUnit 3.1.3 by Sebastian Bergmann.
>>
>>
>> - does simply not stop, it runs forever.
>> The other problem was pear_info (again).
> 
> yes, there must be already somehting before mine, cause
it was already not
> updated before i added AllTests.php
> 
> i will look into it

ok, should be fixed now


-- 
Sebastian Mendel

www.sebastianmendel.de

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php








       
____________________________________________________________
________________________
Looking for a deal? Find great prices on flights and hotels
with Yahoo! FareChase.
http://farechase.yahoo.co
m/

Pádraic Brady schrieb:
> Hi Sebastian,
> 
> Was wondering if there is a wiki page anywhere
explaining the conventions tests must follow in order to be
capable of aggregation into your test runs?

Yourpackage/tests/AllTests.php is required, and will be
included automatically

and it is not my test 

-- 
Sebastian

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Padraic,


> Was wondering if there is a wiki page anywhere
explaining the
> conventions tests must follow in order to be capable of
aggregation
> into your test runs?
Read the text  on http://pear.cweiske.de/
and the class commment
on the linked AllTests.php

> I think a PEAR top-level AllTests.php is sorely missing
and pulling
> in more classes (even if it means someone editing
current tests, or
> adding tests if non-existent) is well worth the
effort.
We actually have such a file and it automatically includes
AllTests.php
files from packages according to the rules I wrote down in
the file.
http://cvs.php.net/viewvc.cgi/pear/AllTests.php?view=
markup

One thing that is still missing is automatically pulling in
.phpt tests
for packages using them instead of PHPUnit. Sebastian
Bergmann will
include phpt testing facility from within phpunit in version
3.14.

Once phpunit 3.14 is out, I will extend pear's global
AllTests.php to
automatically pull in .phpt files in packages not having
AllTests.php.


Together with automated coding standards tests,
documentation coverage
and package.xml checks it will be the base of the pear-wide
QA suite
that is partially running on my server (http://pear.cweiske.de). I
am
still working on a unified interface whose code can be found
at 
http://cvs.php.net/viewvc.cgi/pear/AllTests.php?view=
markup

-- 
Regards/Mit freundlichen Grüßen
Christian Weiske

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php