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

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