Re: New run-tests code

Hannes Magnusson wrote:

On Wed, Sep 9, 2009 at 10:25, zoe<zoe.slattery@googlemail.com> wrote:

At the moment when you use run-tests.php the test results can be affected by 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?

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. OK - I guess that as a Linux PHP command line user I always compile what extensions I need with PHP and don't rely on php.ini to load them. So I _never_ use a php.ini of any sort, I have never had any problem with that approach so haven't really explored alternatives.

I always thought that the intention of run-tests.php was that the tests should always be runnable and always produce the same result no matter what you put in the php.ini. Unfortunately this is not the case, for example whatever Stefan P has in his php.ini apparently caused 2000+ core tests to fail when they pass for Georg and I. The run-tests code makes an attempt to manage the environment by overiding some ini settings, for example the error_reporting - so in this case whatever you put in the php.ini is simply ignored. Another approach to this might be to define a more extensive set of ini overrides. Zoe