Re: Failing Autotests / Bugs
| From: | Lester Caine | Date: | Wed, 24 Aug 2011 08:26:49 +0000 |
| Subject: | Re: Failing Autotests / Bugs | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-54848@lists.php.net to get a copy of this message | ||
Lester Caine wrote:
Rasmus Lerdorf wrote:I can raise patches for items originating from bugs, but what is the right way of doing the same for tests that are not linked to existing bugs? Raise a bug with some notes and post to that? -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk// Firebird - http://www.firebirdsql.org/index.phpand visit it daily from now on? I'd like to see this go to 0 before we release the first 5.4 beta later this year. Probably by moving the bulk of these to XFAIL, but in some cases the tests themselves really are bogus and either need to be removed or fixed.I think that there is a need to review how the whole PDO test setup works, since many of the bug/tests I am seeing there are SQL specific, yet are being applied to all drivers? Certainly there should be base functionality that works transparently, but as soon as one tries running driver specific SQL then those tests need to be driver specific rather then part of a generic set? Or every test needs to cater for the SQL differences?