Re: complete and utter uselessness of run-tests.php

Hi, I vaguely remember trying to run it once and couldn't get anything to work :) I read the comment on the rfc. It makes sense indeed that QA should take care of that. I've had in mind for a while to add a converter to PHPDocumentor to output a basic testsuite, leaving the job to fill it in. I'll try to go back to it. Arnaud. > Hi, > > This email has a vicious subject because I think we have a serious > problem with the unit tests for the PEAR Core. > > I wrote the tests and ran them on my desktop. I recently acquired a > laptop that has the same OS, and half of the tests fail because of > trivial differences in output. For an example of how much work is > required to make these tests work, I will be forced to write code to > verify the output of a 257 line var_dump in the packager test as > compared to the disk, and then output any problems it finds. > > In other words, I would have to basically rewrite the entire PHPUnit > project for every single test case that has any file checking. In > addition, it is harder to figure out whether output is working or not > with run-tests. > > In fact, I would wager that the only person who has EVER gotten a single > one of the unit tests I wrote to work is me. > > Have any of you attempted to get the test suite working for the PEAR core? > > If you have succeeded, I'm astonished. > > A test suite that can't even be run manually, let alone automatically, > is a useless sack of elephant dung. > > Yes, this really pisses me off. Yet another example of a stupid design > choice in PEAR causing months of wasted labor. > > This gives me a bit of an idea as to what QA could be doing, stay tuned > for my comment on the RFC. > > Greg > > -- > PEAR QA Mailing List (http://pear.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php >