Re: [zeta-dev] Re: PHPUnit regression: cannot run the testsuite of one component

2012-02-09 Thread James Pic
Sorry there was a small isssue with the previous pull request so here's the
new URL: https://github.com/sebastianbergmann/phpunit/pull/495


Re: [zeta-dev] Re: PHPUnit regression: cannot run the testsuite of one component

2012-02-09 Thread Maxime Thomas
2012/2/9 James Pic 

> We might have a better solution, if only Sebastian accepts to add a
> --testsuite filter.
>
> Please read the pull request description for details:
> https://github.com/sebastianbergmann/phpunit/pull/494
>
> Credits to Derick for his great support while finding/implementing this
> solution (0day fix found, feels great B).
>
> Cheers from Portugal
>

Ahah.
Harass him !

-- 
Maxime
maxime.tho...@wascou.org | www.wascou.org | http://twitter.com/wascou


[zeta-dev] Re: PHPUnit regression: cannot run the testsuite of one component

2012-02-09 Thread James Pic
We might have a better solution, if only Sebastian accepts to add a
--testsuite filter.

Please read the pull request description for details:
https://github.com/sebastianbergmann/phpunit/pull/494

Credits to Derick for his great support while finding/implementing this
solution (0day fix found, feels great B).

Cheers from Portugal


Re: [zeta-dev] Zeta Components report is late

2012-02-09 Thread Derick Rethans
On Wed, 8 Feb 2012, Jukka Zitting wrote:

> The February 2012 [1] report from Zeta Components is still missing. If
> you don't have a report ready for this month, please note so in the
> wiki page and prepare to report again next month.

I've added one now.

> What's the status of the Zeta Components project nowadays? You missed
> also the November 2011 report [2], and I only see three commits and
> three dev@ posts since the beginning of this year, so I'm a bit
> worried about the future of the project.

It's all slow going. There is some progress however. The main issue that 
deters me from spending more time on it, is that all the tests are 
horribly broken, and they are difficult to get working again.

cheers,
Derick

-- 
http://derickrethans.nl | http://xdebug.org
Like Xdebug? Consider a donation: http://xdebug.org/donate.php
twitter: @derickr and @xdebug


Re: [zeta-dev] Zeta Components report is late

2012-02-09 Thread Derick Rethans
Hi,

I've added a template; can you guys look at it and improve it so that 
one of our mentors can approve it?

cheers,
Derick


On Wed, 8 Feb 2012, Jukka Zitting wrote:

> Hi,
> 
> The February 2012 [1] report from Zeta Components is still missing. If
> you don't have a report ready for this month, please note so in the
> wiki page and prepare to report again next month.
> 
> What's the status of the Zeta Components project nowadays? You missed
> also the November 2011 report [2], and I only see three commits and
> three dev@ posts since the beginning of this year, so I'm a bit
> worried about the future of the project.
> 
> [1] http://wiki.apache.org/incubator/February2012
> [2] http://wiki.apache.org/incubator/November2011
> 
> BR,
> 
> Jukka Zitting
> 

-- 
http://derickrethans.nl | http://xdebug.org
Like Xdebug? Consider a donation: http://xdebug.org/donate.php
twitter: @derickr and @xdebug


[zeta-dev] PHPUnit regression: cannot run the testsuite of one component

2012-02-09 Thread James Pic
Hi all,

Before, we could run the test suite of a component as such:
UnitTest/src/runtests.php Database

But the new test runner does not allow this. For example, phpunit --filter
Database will fail in two ways:

0) test cases without Database in the class name will be omited
(ie. ezcQueryExpressionTest from
Database/tests/sqlabstraction/expression_test.php)
1) test cases with Database in the class name from other components will be
included (ezcDatabaseSchemaGenericTest from
DatabaseSchema/tests/generic_test.php)

Solutions:

0) Flyingmana suggested to use regexps in --filter, document the regexp to
use for each component
1) annotate every test method with @group ComponentName

I'm not sure about these solutions because correct me if I'm wrong but that
looks error prone.

So, should we start implementing any of these solutions ?

Cheers from Lisboa at eZ Winter Conference