jon Wed Oct 23 17:44:43 2002 EDT
Modified files:
/php4 README.TESTING
Log:
Correct mispellings and some word misuse.
Index: php4/README.TESTING
diff -u php4/README.TESTING:1.11 php4/README.TESTING:1.12
--- php4/README.TESTING:1.11 Wed Oct 23 17:32:09 2002
+++ php4/README.TESTING Wed Oct 23 17:44:43 2002
@@ -39,7 +39,7 @@
[Which php.ini is used]
-----------------------
"make test" uses the same php.ini file as it would once installed.
-The tests have been written to be independant of that php.ini file,
+The tests have been written to be independent of that php.ini file,
so if you find a test that is affected by a setting, please report
this, so we can address the issue.
@@ -51,12 +51,12 @@
from the source root and any subdirectories below. If there are files,
which have a "phpt" extension, "run-tests.php" looks at the sections
in these files, determines whether it should run it, by evaluating
-the 'SKIP' section. If the test is elligable for execution, the 'FILE'
+the 'SKIP' section. If the test is eligible for execution, the 'FILE'
section is extracted into a ".php" file, with a unique name and
executed.
When an argument is given or TESTS environment variable is set, the
GLOB is expanded by the shell and any file with extension "*.phpt" is
-regarded as a testfile.
+regarded as a test file.
Tester can easily execute tests selectively with as follows.
@@ -72,7 +72,7 @@
code executed to the test script directory. For example, if
ext/myext/tests/myext.phpt fails to pass, the following files are created:
-ext/myext/tests/myext.php - actual testfile executed
+ext/myext/tests/myext.php - actual test file executed
ext/myext/tests/myext.log - log of test execution (L)
ext/myext/tests/myext.exp - expected output (E)
ext/myext/tests/myext.out - output from test script (O)
@@ -80,11 +80,11 @@
Failed tests are always bugs. Either the test is bugged or not considering
factors applying to the tester's environment, or there is a bug in PHP.
-If this is a known bug, we strive to provide bugnumbers, in either the
+If this is a known bug, we strive to provide bug numbers, in either the
test name or the file name. You can check the status of such a bug, by
-going to: http://bugs.php.net/12345 where 12345 is the bugnumber.
-For clarity and automated processing, bugnumbers are prefixed by a hash
-sign '#' in testnames and/or testcases are named bug12345.phpt.
+going to: http://bugs.php.net/12345 where 12345 is the bug number.
+For clarity and automated processing, bug numbers are prefixed by a hash
+sign '#' in test names and/or test cases are named bug12345.phpt.
NOTE: The files generated by tests can be selected by setting the
environment variable TEST_PHP_LOG_FORMAT. For each file you want to be
@@ -100,7 +100,7 @@
prompt the tester for any user input.
Normally, the exit status of "make test" is zero, regardless of the results
-of independant tests. Set the environment variable REPORT_EXIT_STATUS to 1,
+of independent tests. Set the environment variable REPORT_EXIT_STATUS to 1,
and "make test" will set the exit status ("$?") to non-zero, when an
individual test has failed.
@@ -212,10 +212,10 @@
/ext/standard/tests/strings 003.phpt is a good example for using EXPECTF
-instead of EXPECT. From time to time the algorythmn used for shuffle
+instead of EXPECT. From time to time the algorithm used for shuffle
changed and sometimes the machine used to execute the code has influence
-on the result of shuffle. But it always retuns a three character string
-detectable by %s. Other forms scanable are %i for integers, %f for
+on the result of shuffle. But it always returns a three character string
+detectable by %s. Other scan-able forms are %i for integers, %f for
floating point values and %x for hexadecimal values.
==== /ext/standard/tests/strings 003.phpt ===
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
