Re: Re: Daily updated unit tests and code coverage for PEAR

On 7/5/07, Christian Weiske <cweiske@cweiske.de> wrote:

Sebastian, something similar for PHP_CodeSniffer would be great too! Yes, and I will make such a cron job if we get proper HTML-output for phpcs (currently, phpcs generates plain text only). What I imagine: - A page with a table listing all packages and the number of errors and warnings - Clicking the package name directs to a detailled package page with all files, having the same listing as phpcs detailled output but as html table and with light yellow/red background for warnings and errors

I've started some work on PHP_CodeSniffer reports with a little help from a new XML output format from PHP_CodeSniffer. This requires a patch to PHP_CodeSniffer available at http://pear.php.net/bugs/patch-display.php?bug=11535&patch=PHP_CodeSniffer_XMLOutput&revision=latest With this we can run a shell script such as: #!/bin/sh cd pear mkdir /tmp/phpcs for i in *; do if [ -d $i ]; then echo $i phpcs --report=xml $i > /tmp/phpcs/$i.xml php ~/workspace/pear_testresults/index.php $i > ~/workspace/pear_testresults/phpcs/$i.htm fi done To create static pages like this - http://ucommbieber.unl.edu/workspace/pear_testresults/phpcs/ Christian, et al, does this sound like the right way to move ahead? -- -Brett Bieber http:saltybeagle.com aim:ianswerq