Re: 4.0.2 Release date
| From: | Manuel Lemos | Date: | Sun, 06 Aug 2000 09:26:27 +0000 |
| Subject: | Re: 4.0.2 Release date | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-27921@lists.php.net to get a copy of this message | ||
Hello Stig,
On 06-Aug-00 06:19:07, you wrote:
>> Now, a greater challenge: many existing bugs lead PHP to crash. How do
>> you (plan to) handle crashes in your test suite? Since you use PHP scripts
>> to test features I supposed you have to use something external, like shell
>> scripts or PHP scripts running independently of the actual test scripts, to
>> detect failures that lead to crashes.
>The idea is very simple: a PHP/shell script runs the PHP interpreter
>(with a dedicated php.ini file and/or customization directives on the
>command line) once for each test. The stdout of the test is then
>compared to the expected output, if they differ, the test fails. If it
>gets harder than this, I fear people won't bother writing tests.
I know how regression tests work, but if you run from shell, it will be
hard to run them on non-unix platforms. OTOH hand, if you run from a
single PHP script it terminates when a bug leads PHP to crash. You have to
rely on a PHP only solution to a master PHP script call individual test
scripts using only the standalone CGI executable. Besides that there may
exist bugs that only show when PHP is run as a server module, so the scripts
may have to runnable that way.
Regards,
Manuel Lemos
Web Programming Components using PHP Classes.
Look at: http://phpclasses.UpperDesign.com/?user=mlemos@acm.org
--
E-mail: mlemos@acm.org
URL: http://www.mlemos.e-na.net/
PGP key: http://www.mlemos.e-na.net/ManuelLemos.pgp
--