Last year PHPUnit participated in the GSoC under the umbrella of PHP. Is
this possible this year as well?
I discussed this issue with Marcus and Chris DiBona at the mentor summit
and the consensus was that PHPUnit by itself is too small to participate
as a mentoring organization and that PHPUnit should continue to "take
away" a slot from PHP.
One of the ideas [1] is to implement a parser for gcov data files in PHP
to integrate the code coverage information for PHP and PHP extensions
into PHPUnit's code coverage report. This could be helpful for
developers that write both C-level and PHP-level code for their PHP
applications.
--
[1] http://www.phpunit.de/wiki/Ideas
--
Sebastian Bergmann http://sebastian-bergmann.de/
GnuPG Key: 0xB85B5D69 / 27A7 2B14 09E4 98CD 6277 0E5B 6867 C514 B85B 5D69
Hi Sebasitian,
On Thu, Mar 6, 2008 at 9:08 AM, Sebastian Bergmann
sb@sebastian-bergmann.de wrote:
Last year PHPUnit participated in the GSoC under the umbrella of PHP. Is
this possible this year as well?I discussed this issue with Marcus and Chris DiBona at the mentor summit
and the consensus was that PHPUnit by itself is too small to participate
as a mentoring organization and that PHPUnit should continue to "take
away" a slot from PHP.
I don't think it is fair in regard of the other PHP unit tests
project. PHPUnit already has a high visibility.
One of the ideas [1] is to implement a parser for gcov data files in PHP
to integrate the code coverage information for PHP and PHP extensions
into PHPUnit's code coverage report. This could be helpful for
developers that write both C-level and PHP-level code for their PHP
applications.
To add generic testing features to PHP that can be used by any PHP
projects or tests framework sounds like a great idea.
Cheers,
Pierre Joye schrieb:
PHPUnit already has a high visibility.
Huh? This is not about improving the visibility of PHPUnit.
--
Sebastian Bergmann http://sebastian-bergmann.de/
GnuPG Key: 0xB85B5D69 / 27A7 2B14 09E4 98CD 6277 0E5B 6867 C514 B85B 5D69
On Thu, Mar 6, 2008 at 9:39 AM, Sebastian Bergmann
sb@sebastian-bergmann.de wrote:
Pierre Joye schrieb:
PHPUnit already has a high visibility.
Huh? This is not about improving the visibility of PHPUnit.
I know but still.That's a side comment.
Cheers,
Hi!
One of the ideas [1] is to implement a parser for gcov data files in PHP
to integrate the code coverage information for PHP and PHP extensions
into PHPUnit's code coverage report. This could be helpful for
I think speaking of the coverage also there was an issue that phpunit's
coverage calculating algorithm could be optimized, since there where
instances when generating coverage took too much. Is it still the same?
If so, maybe improving it would be a good idea.
Stanislav Malyshev, Zend Software Architect
stas@zend.com http://www.zend.com/
(408)253-8829 MSN: stas@zend.com
Stanislav Malyshev schrieb:
I think speaking of the coverage also there was an issue that phpunit's
coverage calculating algorithm could be optimized, since there where
instances when generating coverage took too much. Is it still the same?
It is much better now, see http://tinyurl.com/2toenr for details. On top
of that, PHPUnit 3.3 brings memory performance improvements (see
http://www.phpunit.de/ticket/405 for details).
--
Sebastian Bergmann http://sebastian-bergmann.de/
GnuPG Key: 0xB85B5D69 / 27A7 2B14 09E4 98CD 6277 0E5B 6867 C514 B85B 5D69
I think the real question we have to ask is "Do we consider PHPUnit"
standard for PHP Development Unit Testing ?
If so, PHPUnit gets a grant (or a chance to get one under the PHP
Project umbrella)
If not, then it doesn't.
I consider PHPUnit the standard for Unit Testing in PHP, now what do
you all think ?
--
David,
Re-read what you are replying.
I think the real question we have to ask is "Do we consider PHPUnit"
standard for PHP Development Unit Testing ?If so, PHPUnit gets a grant (or a chance to get one under the PHP
Project umbrella)If not, then it doesn't.
I consider PHPUnit the standard for Unit Testing in PHP, now what do
you all think ?
I don't consider it as a standard, maybe the leading tool yes (no idea
if it is or not), but not a standard. There is other good unit testing
tools out there (lime, simpletest to cite two). My point was that even
if phpUnit may be the leading unit tests tool for php, it is not a
php.net project. That applies to other PHP frameworks, applications,
etc.
Cheers,
I think the real question we have to ask is "Do we consider PHPUnit"
standard for PHP Development Unit Testing ?If so, PHPUnit gets a grant (or a chance to get one under the PHP
Project umbrella)If not, then it doesn't.
I consider PHPUnit the standard for Unit Testing in PHP, now what do
you all think ?I don't consider it as a standard, maybe the leading tool yes (no idea
if it is or not), but not a standard. There is other good unit testing
tools out there (lime, simpletest to cite two). My point was that even
if phpUnit may be the leading unit tests tool for php, it is not a
php.net project. That applies to other PHP frameworks, applications,
etc.
I think in general we can say the following order applies:
- php internals (php-src, qa, docs etc)
- any other php.net subproject
- other php projects
if a proposal falls in 3) it needs to be really good and all the
prosals left in 1) and 2) need to be pretty unexciting in order to be
accepted.
this is essentially how things have been implicitly handled from what
i have seen in the past years. and so far we have had stuff in 3)
manage to "sneak" in this way.
regards,
Lukas
Hi All,
- php internals (php-src, qa, docs etc)
- any other php.net subproject
- other php projects
if a proposal falls in 3) it needs to be really good and all the
prosals left in 1) and 2) need to be pretty unexciting in order to be
accepted.
And I fully agree.
By the way, I created the GSOC namespace and the 2008 page. Feel free
to update it :)
Cheers,
Hi All,
- php internals (php-src, qa, docs etc)
- any other php.net subproject
- other php projects
if a proposal falls in 3) it needs to be really good and all the
prosals left in 1) and 2) need to be pretty unexciting in order to be
accepted.And I fully agree.
By the way, I created the GSOC namespace and the 2008 page. Feel free
to update it :)
regards,
Lukas
- php internals (php-src, qa, docs etc)
- any other php.net subproject
- other php projects
just to remember last year we had 4 projects in [3] (jaws, phpunit,
doctrine, xdebug), 1 in [2] (PEAR) and 2 in [1] (docs and php-src).
the year before things weren't so different. given that info I would
say there is a high possibility to have a PHPUnit project accepted
again this year.
The key is the number of proposals. The more proposals we have to our
organization, the more slots we will get...