Commit:    56ef58697ca27a35b9f35f6605844a6a9e816646
Author:    Kalle Sommer Nielsen <ka...@php.net>         Wed, 17 Aug 2016 
23:08:18 +0200
Parents:   06cb697d5ae6cf43cf4a657e35637aace9febe11
Branches:  master

Link:       
http://git.php.net/?p=web/qa.git;a=commitdiff;h=56ef58697ca27a35b9f35f6605844a6a9e816646

Log:
Added some more information regarding TESTS=X as suggested by Christoph

Changed paths:
  M  running-tests.php


Diff:
diff --git a/running-tests.php b/running-tests.php
index dca2d1f..801b877 100644
--- a/running-tests.php
+++ b/running-tests.php
@@ -26,7 +26,12 @@ common_header();
     Specific tests can also be executed, like running tests for a certain 
extension. To do 
     this you can do like so (for example the standard library): 
     <code>make test TESTS=ext/standard</code>. Where <code>TESTS=</code> 
points to a 
-    directory containing <code>.phpt</code> files.
+    directory containing <code>.phpt</code> files or a single 
<code>.phpt</code> file like: 
+    <code>make test TESTS=tests/basic/001.phpt</code>. You can also pass 
options directly 
+    to the underlaying script that runs the test suite 
(<code>run-tests.phpt</code>) using 
+    <code>TESTS=</code>, for example to check for memory leaks using Valgrind, 
the <code>-m</code> 
+    option can be passed along: <code>make test TESTS="-m Zend/"</code>. For a 
full list 
+    of options that can be passed along, then run <code>make test 
TESTS=-h</code>.
    </p>
 
    <p>


--
PHP Quality Assurance Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to