Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54740
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.42 as permitted sender)
References: <4E4EEED3.4070001@sugarcrm.com> <4E4EF9AE.6090102@lerdorf.com>
In-Reply-To: <4E4EF9AE.6090102@lerdorf.com>
Mime-Version: 1.0 (iPhone Mail 7A400)
Date: Sat, 20 Aug 2011 09:57:48 +0900
Message-ID: <6398514652009622327@unknownmsgid>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: Stas Malyshev <smalyshev@sugarcrm.com>, PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] 5.3.7pl1
From: catch56@gmail.com (Nathaniel Catchpole)

 From my phone. Apologies for brevity and typos.

On 2011/08/20, at 9:03, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:


>>
>>
>
> The secondary problem is that we are not doing a good job running our
> tests prior to releases. I think this is mostly because we have way
> too
> many tests that fail and one more or less failing test gets lost in
> the
> noise.

This was a major problem when Drupal added automated testing. Our
solution was to get to a 100% pass rate via a combination of fixing
bugs but also removing failing tests (moving them to patches against
bug reports in the issue queue or occasionally commenting out
assertions). This means we're able to tell instantly if there's a
regression committed when there's test coverage for it, since we test
patches in the queue this usually happens before that anyway.

  Tests that fail stay in the queue until they're committed along with
the accompanying bug fix. It's not ideal but it was impossible to keep
track any other way.

Nat


>
> -Rasmus
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>