On Thu, Mar 6, 2008 at 5:21 PM, Lukas Kahwe Smith <[EMAIL PROTECTED]> wrote:
> 1) php internals (php-src, qa, docs etc)
> 2) any other php.net subproject
> 3) 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] (
On 06.03.2008, at 21:40, Pierre Joye wrote:
Hi All,
1) php internals (php-src, qa, docs etc)
2) any other php.net subproject
3) 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.
Hi All,
> 1) php internals (php-src, qa, docs etc)
> 2) any other php.net subproject
> 3) 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 w
On 06.03.2008, at 21:17, Pierre Joye wrote:
On Thu, Mar 6, 2008 at 7:20 PM, David Coallier <[EMAIL PROTECTED]> wrote:
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
On Thu, Mar 6, 2008 at 7:20 PM, David Coallier <[EMAIL PROTECTED]> wrote:
> 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, th
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 a
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/2toen
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
On Thu, Mar 6, 2008 at 9:39 AM, Sebastian Bergmann
<[EMAIL PROTECTED]> 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,
--
Pierre
http://blog.thepimp.net |
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
--
PHP Internals - P
Hi Sebasitian,
On Thu, Mar 6, 2008 at 9:08 AM, Sebastian Bergmann
<[EMAIL PROTECTED]> 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
11 matches
Mail list logo
