Re: New run-tests code
| From: | zoe | Date: | Wed, 09 Sep 2009 09:55:21 +0000 |
| Subject: | Re: New run-tests code | ||
| References: | 1 2 3 | Groups: | php.qa |
| Request: | Send a blank email to php-qa+get-65349@lists.php.net to get a copy of this message | ||
Pierre Joye wrote:
hi all, On Wed, Sep 9, 2009 at 11:11 AM, Hannes Magnusson<bjori@php.net> wrote:Not really. The key part in Zoe's mail was: can always be controlled using the test's --INI-- and I fully agree with that. Running a test with some random php.ini without actually knowing the context is pointless and even produce false positve errors. Thanks Pierre :-) It's a complicated and widely misunderstood subject, so useful to have the discussion here. Neither Stefan, Georg or I were sure that we understood all the issues.On Wed, Sep 9, 2009 at 10:25, zoe<zoe.slattery@googlemail.com> wrote:How are you planning on picking up shared extensions or making sure stuff works on weird configuration setups? Testing only the default php.ini limits the actual testing quite a lot.your php.ini file. This causes endless confusion for people that don't realise that they need to use the -n option to ignore their php.ini. We'd like to make ignoring the user's php.ini file the default behaviour in the new version. Does anyone see a problem with this?At the moment when you use run-tests.php the test results can be affected by
Cheers,