At 00:27 24-10-2002, Yasuo Ohgaki wrote:
PS: If you would like to write INI independent scripts, I
suggest you to use php.ini-recommended at least. You don't/
didn't know phps crashing and make test does not work well with
php.ini-recommended, nonetheless, you're insisting there is no
problems.
This is a totally different issue. If ini settings affect the test suite,
it's a bug in the test suite, period. If you depend on a preset environment,
you are testing how things behave in that environment, you are not testing
how that specific build for the __end user__ will behave once installed.
Test authors, can enforce specific settings they need, in the --INI--
section. If other settings affect the tests behavior, it is a good thing (tm)
to know this. It may be totally unexpected and shed light on why certain
bugs surface.
I also removed your statement in README.TESTING, which stated that "if a test
fails, the user can see if it's a real bug". There are no maybe's in a test
suite. It's a bug or it isn't. Putting in maybe's makes it's purpose confusing
and unreliable.
This is one of the reasons, that during QA periods, some major bugs are not
uncovered ('file_exists'). People feel like "oh well, the test is probably
bogus", and do not report it.
Current work being done on the testsuite is IMO the right direction. Tests for
every function under whatever environment and the option to post to QA so that
the data can now be collected and analyzed.
If you see that the test suite is not working well, with php.ini-recommended,
than please report the tests affected. You don't adjust the road, just because
certain cars, have questionable steering - you fix the cars.
Met vriendelijke groeten / With kind regards,
Webmaster IDG.nl
Melvyn Sopacua
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
