Re: First look at revamping regression tests for php3

> o Keep the current test regression scheme which does *NOT* > require httpd running. > > o Being able to quickly do a `make test' with just the cgi version > of PHP3 is very valuable -- after things looks good, one can then move > on to making Apache / SSL / etc third party packages/modules. This may be convenient, but it doesn't test the environment that PHP is actually going to be running in. We are at the point where just testing the core language features doesn't give us very much. It is pretty much stable and we are not changing too many things. If you looked under the hood you would also see that a lot of the code is different depending on whether PHP is compiled as a server module as opposed to a CGI. Running a "make test" on the CGI code and then installing the module version is absolutely useless. And this is the situation most people would be in. And when it comes to ISAPI, NSAPI, WSAPI versions this CGI-based tester is even more useless. With an http-based regression testing mechanism we could even have a test.php.net site that you could go to and tell it to test your setup once you have things installed in case you are unable to run Perl on your platform. There is no doubt that the regression testing code needs a serious overhaul. Rocky volunteered and I am quite happy to sit back and see what sort of ideas he has. I'll provide input when asked, but until I am able and willing to get my hands dirty and contribute to the effort (which I don't have time for right now) I definitely am not in any position to criticize his efforts, and neither are you. -Rasmus -- PHP Development Mailing List http://www.php.net/ To unsubscribe send an empty message to php-dev-unsubscribe@lists.php.net For help: php-dev-help@lists.php.net