Re: [PEAR-QA] Re: QA enhancements in PEAR 1.4

On Mar 26, 2005, at 10:01 AM, Lukas Smith wrote:

> Greg Beaver wrote: 
>
> btw: i never spend any time on this, but maybe someone knows:
> how hard would it be for me to also be able to run my phpunit tests
> this way? .. i have a clitest.php to be able to run the tests form the
> shell.

This might be an annoying way to go about this, but you could always
write little wrapper .phpt's:

--TEST--
test for this feature
--FILE--
<?php
require 'clitest.php';
echo 'tests done';
//this assumes that your tests only output something when an error
occurs
--EXPECT--
tests done

-ryan
--
http://theryanking.com/

Ryan King wrote:
> On Mar 26, 2005, at 10:01 AM, Lukas Smith wrote:
> 
>
>
> This might be an annoying way to go about this, but you could always
> write little wrapper .phpt's:
>
> --TEST--
> test for this feature
> --FILE--
> <?php
> require 'clitest.php';
> echo 'tests done';
> //this assumes that your tests only output something when an error occurs
> --EXPECT--
> tests done

unfortunately this is not the case
also I have multiple tests and it would be nice to be able to pass
information about the number of passed and failed tests to the end
result of the run-tests call as well

regards,
Lukas

On Mar 27, 2005, at 12:57 AM, Lukas Smith wrote:

> Ryan King wrote: 
>
> unfortunately this is not the case
> also I have multiple tests and it would be nice to be able to pass
> information about the number of passed and failed tests to the end
> result of the run-tests call as well

I'm talking about having one of these for each test case (which could
be quite annoying, unless you automate it). The idea is that it would
pass as along as your phpunit test didnt' output anything. This would
certainly cover the multiple tests issue, wouldn't it?

-ryan

--
http://theryanking.com/