Re: New run-tests code
| From: | Rafael Dohms | Date: | Fri, 11 Sep 2009 11:52:38 +0000 |
| Subject: | Re: New run-tests code | ||
| References: | 1 2 3 4 5 6 | Groups: | php.qa |
| Request: | Send a blank email to php-qa+get-65371@lists.php.net to get a copy of this message | ||
On Thu, Sep 10, 2009 at 4:04 AM, zoe <zoe.slattery@googlemail.com> wrote:
> Hi all
>
> I have to agree with Derick and others: The current behavior was chosen
>>> on purpose. The tests should run in every environment, with all
>>> operating systems and all ini settings else either the test or the
>>> environment is broken.
>>>
>>> In the cases where special ini settings are needed they can be set just
>>> few are fix (especially error reporting) and the current situation is a
>>> clear feature.
>>>
>>>
>>
>>
>>
> Thanks for all the responses. Although I initially felt the same way as
> Pierre does - preferring a tightly controlled test environment - I am
> persuaded by the counter arguments. This has been a useful discussion.
>
> Zoe
>
>
>
> --
> PHP Quality Assurance Mailing List <http://www.php.net/>
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
Is there no middle ground we can work on?
As i see we would have problems especially with extension tests and windows,
as Zoe cited linux machines usually compile with extensions. Maybe merging
both ini's and sorting out the main problem causes, as in html_errors.
I see the point in both arguments, with the new run-tests and parallel
testing coming, is it viable to just run tests with both the local ini and
the default? A comparison between those might even help us pickup more edge
cases that depende on config, like Stephan P's 2000+ tests mentioned above.
--
Rafael Dohms
PHP Evangelist and Community Leader
http://www.rafaeldohms.com.br
http://www.phpsp.org.br