Move all testing docs to qa.php.net

The qa.php.net currently includes nice collection of information about
tests and how to run them. Instead of maintaining two locations of this
information, this patch removes the README.TESTING from the php-src
repo. Patch for qa.php.net has been sent separately to that repo.

Author: petk

CODING_STANDARDS

@@ -251,7 +251,7 @@ Testing
 -------
 
 1.  Extensions should be well tested using *.phpt tests. Read about that
-    in README.TESTING.
+    at https://qa.php.net/write-test.php.
 
 Documentation and Folding Hooks
 -------------------------------

CONTRIBUTING.md

@@ -52,9 +52,6 @@ We love getting new tests! PHP is a huge project and improving code coverage is
 a huge win for every PHP user.
 
 [Our QA site includes a page detailing how to write test cases.](http://qa.php.net/write-test.php)
-Please note that the section on submitting pull requests is outdated: in
-addition to the process listed there, you can also
-[submit pull requests](#pull-requests).
 
 ## Writing documentation
 

README.SUBMITTING_PATCH

@@ -138,11 +138,10 @@ work on "master".
 
 Read CODING_STANDARDS before you start working.
 
-After modifying the source see README.TESTING and
-http://qa.php.net/write-test.php for how to test.  Submitting test
-scripts helps us to understand what functionality has changed.  It is
-important for the stability and maintainability of PHP that tests are
-comprehensive.
+After modifying the source see https://qa.php.net/write-test.php for
+how to test.  Submitting test scripts helps us to understand what
+functionality has changed.  It is important for the stability and
+maintainability of PHP that tests are comprehensive.
 
 After testing is finished, create a patch file using the command:
 

README.TESTING

@@ -37,3 +37,10 @@ Guidelines for contributors
 - [README.GIT-RULES](/README.GIT-RULES)
 - [README.MAILINGLIST_RULES](/README.MAILINGLIST_RULES)
 - [README.RELEASE_PROCESS](/README.RELEASE_PROCESS)
+
+## Testing
+
+To run tests the `make test` is used after successful compilation of the sources.
+
+See [Creating new test files](https://qa.php.net/write-test.php) chapter for more
+information about testing.

README.md

@@ -7,9 +7,7 @@ output_handler=
 zlib.output_compression=0
 --FILE--
 <?php
-/* Do not change this test it is a README.TESTING example.
- * test5.jpg is a 1*1 image that contains an Exif section with ifd = 00000009h
- */
+// test5.jpg is a 1*1 image that contains an Exif section with ifd = 00000009h
 $image  = exif_read_data(dirname(__FILE__).'/test5.jpg','',true,false);
 var_dump($image['IFD0']);
 ?>

ext/exif/tests/exif005.phpt

@@ -12,9 +12,6 @@ echo "sodium extension is available";
   text in the --EXPECT-- section below for the tests
   to pass, differences between the output and the
   expected text are interpreted as failure
-
-        see php7/README.TESTING for further information on
-  writing regression tests
 */
 ?>
 --EXPECT--

ext/sodium/tests/installed.phpt

@@ -2,7 +2,6 @@
 Testing str_shuffle.
 --FILE--
 <?php
-/* Do not change this test it is a README.TESTING example. */
 $s = '123';
 var_dump(str_shuffle($s));
 var_dump($s);

ext/standard/tests/strings/str_shuffle.phpt

@@ -2,7 +2,6 @@
 Test whether strstr() and strrchr() are binary safe.
 --FILE--
 <?php
-/* Do not change this test it is a README.TESTING example. */
 $s = "alabala nica".chr(0)."turska panica";
 var_dump(strstr($s, "nic"));
 var_dump(strrchr($s," nic"));

ext/standard/tests/strings/strings001.phpt

@@ -2,7 +2,6 @@
 strtr() function
 --FILE--
 <?php
-/* Do not change this test it is a README.TESTING example. */
 $trans = array("hello"=>"hi", "hi"=>"hello", "a"=>"A", "world"=>"planet");
 var_dump(strtr("# hi all, I said hello world! #", $trans));
 ?>