PHPUnit lists the failed and risky tests at the end of a run, but it shows skipped and incomplete tests only as a count (Skipped: 62) unless it runs with --verbose. junit.xml does not have the reasons either: PHPUnit 9.6 writes a skipped or incomplete test as an empty <skipped/> element. So a host could not see anywhere which tests were skipped or why. This PR runs PHPUnit with --verbose, the same flag WordPress core's own PHPUnit workflow uses, and describes the lists in the README.

Fixes #47.

Changes

• test.php: add --verbose to the default PHPUnit command. A custom WPT_PHPUNIT_CMD is not changed.
• README: add the R (risky) symbol, and a short paragraph about the lists at the end of the run, with an example from a real run.

The report sent to WordPress.org does not change. I checked the receiving plugin (phpunit-test-reporter/src/class-restapi.php in the WordPress/wordpress.org repository). When a result has failures, it treats every test case under testsuites as a failure in the "new failures" email, so skipped tests should not go into the payload.

Risky tests: PHPUnit already lists them without --verbose. They are not in junit.xml, because --dont-report-useless-tests also turns off risky reporting in the PHPUnit 9.6 JUnit logger (JUnit::addRiskyTest() returns early when reportRiskyTests is false).

Testing Instructions

Environment

• WordPress: trunk, r64693
• PHP: 8.4.27
• Server: Docker image built from this repository's docker/Dockerfile with PHP_VERSION=8.4, run as the non-root wptests user
• Database: MariaDB 11.8.9
• Browser: n/a (command line test)
• OS: Linux (Docker Desktop, WSL2 kernel 6.18.33)
• Theme: the test suite's default theme
• MU Plugins: None
• Plugins: None
• PHPUnit 9.6.38, Node.js 24.22.1, npm 11.19.1, ImageMagick 7.1.1-43, imagick 3.8.1

Steps to Test

1. cp .env.default .env, set the WPT_DB_* values, set WPT_TEST_DIR to the same value as WPT_PREPARE_DIR, then source .env.
2. php prepare.php
3. php test.php
4. php report.php without WPT_REPORT_API_KEY, so it prints the results instead of uploading them.
5. php cleanup.php
6. To compare, run step 3 on master as well, against the same prepared checkout, before step 5.

Expected Results

• ✅ The PHPUnit command that test.php logs ends with --dont-report-useless-tests --verbose.
• ✅ After the warnings, the output lists every skipped test with its reason: There were 62 skipped tests:.
• ✅ junit.xml is the same as on master: the same totals and the same status for every test case.
• ✅ The results that report.php prints (the results field of the upload) are the same as on master, apart from time.

Results

Before (master at 1f276b2), the end of the test.php output:

WARNINGS!
Tests: 30867, Assertions: 4573915, Warnings: 86, Skipped: 62.

After (this branch), the same run adds the list. Three of the 62 entries:

There were 62 skipped tests:
...
3) Tests_DB::test_locale_floats
No European locales available for testing.

/tmp/wp-test-runner/tests/phpunit/tests/db.php:89
...
13) Test_Image_Resize_GD::test_resize_heic
No HEIC support in the editor engine WP_Image_Editor_GD on this system.

/tmp/wp-test-runner/tests/phpunit/tests/image/resize.php:129
...
56) Tests_Sitemaps_wpSitemapsRenderer::test_get_sitemap_index_xml
This test requires the XSL extension.
...
WARNINGS!
Tests: 30867, Assertions: 4573915, Warnings: 86, Skipped: 62.

The XSL entry is how I found that the image built from docker/Dockerfile does not have the xsl extension, so 6 sitemap tests are skipped in the container runs. That is a separate change.

junit.xml from both runs: tests=30867 assertions=4573915 failures=0 errors=0 warnings=86 skipped=62, and the sorted list of test cases with their status is identical (same SHA-1 over 30867 lines).

report.php results from both runs, apart from time: {"tests":"30867","failures":"0","errors":"0","testsuites":[]}.

php -l test.php and vendor/bin/phpcs test.php with the repository ruleset are clean.

Not tested: the multisite flavor and an SSH setup. In both cases the flag is part of the same command string.

My connection to GitHub is slow, so prepare.php cloned wordpress-develop trunk from a local mirror (a git insteadOf rule), and the Gutenberg build was downloaded once beforehand. No runner file was changed for that.

Notes

• PHPUnit 10 removed --verbose (it has --display-skipped and --display-incomplete instead). Core trunk requires yoast/phpunit-polyfills ^1.1.0, which keeps PHPUnit on 9.x, and core's own workflow passes --verbose, so this line would change together with core when it moves to PHPUnit 10.
• Add WPT_PHPUNIT_ARGS to pass extra arguments to PHPUnit #358 changes the lines right after the PHPUnit command in test.php, so whichever of the two is merged second needs a one-line rebase. This branch merges cleanly with the other open PRs (Add host-tools/testrunner.sh to run the full test cycle in one step #346, Add host-tools/setup.sh to create .env with prompts #348, Document the host tools #349, Ensure PHPCS cache directory is tracked and fix docblock typos #357, Check the minimum PHP version from the WordPress checkout, before the build #360).

Use of AI

AI assistance: Yes
Tool(s): Claude Code
Used for: Investigation, implementation, the end-to-end test runs and PR wording. I reviewed the reasoning and the test results, and I take responsibility for the contribution.