Re: rewriting run-tests.php

On October 29, 2002 05:22 pm, Shane Caraveo wrote: > 2. tests via http. rather than executing php a http request is made. An interesting idea, certainly would allow us to test the request processing code and so on. However, I am not certain we need to run all the tests from the webserver sapi. IMHO the webserver testing should be limited to output control tests as well as input (FILES/GET/POST) parsing. There is one potential problem that I see with web server tests, this problem being the fact that the PHP's output could be skewed/altered by other modules/extensions running on the server. Making the output of the test unreliable, so you may need to have the test output the results to a file on the harddrive and compare that to the expected data. > 3. multithreaded testing. Majority of the problems with ZTS builds are the results of various ZTS wrappers having bugs in them, 99% of those can be resolved by simply adding the --enable-experimental-zts flag and compiling the PHP and then running the test suit on the code. As for testing PHP & thread-safety another possibility is to use the embed 'sapi' in combination with a simple c program that would receive a sample test to run as well as how many threads to run the test in. This is probably better then using a PECL module, since it does not add additional dependencies. Ilia