On Wed, 23 Oct 2002, Marcus Börger wrote: > Derick this is nonsense!!!!!
Yeah, start yelling. That will really help us all. > We developers can use php -c bla run-tests.php xyz > > But make is for automated things and for those not reading > README.TESTING where everything should be explained. If people refuse to read documentatino for tool they don't deserve to use it. Come'n.. if you are professional enough to even run a testsuite then you're certainly professional enough to read a README. > The typical user who is just glad to be able to build his > private distribution of php will just call 'make test' to check > that the created php executable works. After doing some ini > settings many tests will fail.... No, not true. All tests we have should be made working with the settings it depends on hardcoded in the --INI-- section, or for the run-tests.php script with ini_set()'s. _That_ will make a robust test suite. > In contrast when you want complex tests just use --INI-- > section to test different ini values. Even better would be > to use this --INI-- section where ever a special value is > needed. > > Remeber the tests are not made to test your ini file but > for testing the general functionality of PHP. And this should > of cause not be affected by some private ini settings. Actually, it should, see my reasoning before. > So please readd the ini to make test and use commandline > when you want to test other ini files. This is not for me, it's the general idea that the test suite works whatever stupid ini settings a user made. If tests fail because of this, or the test suite doesn't work we need to fix the tests and the suite. That's the intention behind it all. Derick -- --------------------------------------------------------------------------- Derick Rethans http://derickrethans.nl/ JDI Media Solutions --------------[ if you hold a unix shell to your ear, do you hear the c? ]- -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
