Running the test suite

Now that we have an basic understanding of what kind of testing we’re doing, let’s run the test suite. Before we can run the tests, make sure you have successfully built php from source (see building_php) and you have an executable at sapi/cli/php.

There are two ways to run the test suite.

Running tests directly with run-tests.php

You can run the test suite directly with run-tests.php. At minimum you’ll need to specify the php executable that you wish to test against which you can do with the -p flag. Note that in order to run all tests correctly this should be an absolute path to the PHP executable.

~/php-src> sapi/cli/php run-tests.php -p `pwd`/sapi/cli/php

A shortcut flag you can use to tell run-tests to test against the PHP executable that is currently invoked is by using the -P flag.

~/php-src> sapi/cli/php run-tests.php -P

If you don’t want to have to set the -p or -P flag every time, you could specify the php executable with the TEST_PHP_EXECUTABLE environment variable which can be set with export on Linux machines.

~/php-src> export TEST_PHP_EXECUTABLE=sapi/cli/php
~/php-src> sapi/cli/php run-tests.php

On Windows you can set the environment variable using set.

C:\php-src> set TEST_PHP_EXECUTABLE=sapi/cli/php
C:\php-src> sapi/cli/php run-tests.php

By default run-tests.php will start running all 15,000+ tests in the test suite which would take forever-ever. You can specify a target folder of tests to run or even a single test. The following example will run all the tests associated with PHP 7’s CSPRNG.

~/php-src> sapi/cli/php run-tests.php -P ext/standard/tests/random

You can also specify multiple target folders or files to run.

~/php-src> sapi/cli/php run-tests.php -P Zend/ ext/reflection/ ext/standard/tests/array/

If you run the full test suite, and there are failing tests, the script will ask if you want to send a report to the PHP QA team. This can be annoying sometimes. It is possible suppress this question by setting the -q flag, or by setting environment variable NO_INTERACTION=1.

Executing tests in parallel

You can’t.

More options

Tests that passed are usually not that interesting. You can filter what tests to show with the -g flag. Possible values are PASS, FAIL, XFAIL, SKIP, BORK, WARN, LEAK, REDIRECT For example to only show failing tests:

~/php-src> run-tests.php -g FAIL

For a full list of supported options that run-tests supports, just run it with --help.

~/php-src> sapi/cli/php run-tests.php --help

For example -x to skip slow tests, --offline to skip online tests or -m for testing memory leaks with Valgrind can be very useful.