Re: pear run-tests phpUnit question
| From: | till | Date: | Fri, 18 Jan 2008 17:39:03 +0000 |
| Subject: | Re: pear run-tests phpUnit question | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-48959@lists.php.net to get a copy of this message | ||
On Jan 18, 2008 6:33 PM, Chuck Burgess <demon.gene@gmail.com> wrote:
> On Jan 18, 2008 11:23 AM, Helgi Þormar Þorbjörnsson <helgith@gmail.com>
> wrote:
>
> > Seems a bit complicated unless the package supplies the min / max stuff
> > for phpunit them self via package.xml
> >
>
> That's exactly what I meant... values in the package.xml that identify which
> test harness the package's tests are written for, and what range of versions
> of the test harness that the package's tests are know to run clean against.
> I suppose a use case that this doesn't cover is a package that has both
> phpunit and PHPTs, but my assumption there is that PHPT doesn't require a
> separate test harness and therefore no dependency info for it would be put
> in package.xml. You could still run just the PHPTs via "pear run-tests -p"
> while separately running the PhpUnit tests via "pear run-tests -up",
> irrelevant of the fact that newer PhpUnit versions should be able to
> recognize and run any nearby PHPTs internally.
>
> I wasn't meaning the *run-tests* logic had to figure it all out itself :P
Just for the record and in case people misunderstood.
I had two things on my mind:
a) dependency in package.xml (and obviously min/max)
b) I questioned if the "-up"-part is meant to be
Till