diff options
| author | Hartmut Holzgraefe <hholzgra@php.net> | 2004-04-15 15:03:26 +0000 |
|---|---|---|
| committer | Hartmut Holzgraefe <hholzgra@php.net> | 2004-04-15 15:03:26 +0000 |
| commit | 702ca7f53f5de1a1a214bc73b862e5edfed766d3 (patch) | |
| tree | 497b3c30c82627617f27368945870c657e6361a2 | |
| parent | dda0dd4825658a81192e25d8674e288c756fe560 (diff) | |
| download | php-git-702ca7f53f5de1a1a214bc73b862e5edfed766d3.tar.gz | |
be a bit more explanatory ...
| -rw-r--r-- | README.TESTING | 13 |
1 files changed, 11 insertions, 2 deletions
diff --git a/README.TESTING b/README.TESTING index a40c68de42..3dd2309dbb 100644 --- a/README.TESTING +++ b/README.TESTING @@ -1,11 +1,20 @@ [IMPORTANT NOTICE] ------------------ - Please do not ask developers why some or all tests are failing in -your environment! Let us know if you find why it fails. Thank you. + Failed tests usualy indicate a problem with your local system setup +and not within PHP itself (at least for official PHP release versions). +You may decide to automaticaly submit a test summary to our QA workflow +at the end of a test run. + Please do *not* submit a failed test as a bug or ask for help on why +it failed on your system without providing substantial backup information +on *why* the test failed on your special setup. Thank you :-) [Testing Basics] ---------------- + The easiest way to test your PHP build is to run "make test" from the +command line after successfully compiling. This will run the complete +tests for all enabled functionalities and extensions using the PHP +CLI binary ( To execute test scripts, you must build PHP with some SAPI, then you type "make test" to execute all or some test scripts saved under "tests" directory under source root directory. |