[aryanjasala]

@wordpress/env 11.16 (from #790, now on this branch) deprecates the env.tests block and the automatic tests environment, and prints a warning on every wp-env start. Its documented replacement is a second config file passed with --config.

Changes

• .wp-env.tests.json defines the test environment: the theme, PHP 8.2, port 5891, its own containers and database, and WP_DEBUG on (the logger tests need it).
• .wp-env.json sets testsEnvironment to false and drops env.tests.
• pretest:php starts the test environment (a few seconds when it is already up) and installs Composer dependencies in its cli container; test:php runs PHPUnit there.
• Docs, the scaffold skill and the dev-tools test fixture describe the new setup. The test-only WP_DEBUG override step in docs/local-development.md and its row in docs/internal/maintenance.md are gone: the committed test config covers it.
• .gitignore ignores .wp-env.tests.override.json.

Why not run the tests in the development environment's cli container: wp-env's wp-tests-config.php there uses the site's database and wp_ prefix, so the suite wipes the development site's content. Checked: the site's posts went from 3 to 0.

CI needs no change: ci-test-php runs npm run wp-env start and then npm run test:php, whose pretest hook starts the test environment, and WP_ENV_PHP_VERSION and WP_ENV_CORE apply to it too.

Testing

• wp-env start and npm run test:php: no deprecation warnings; the test environment comes up on 5891 in its own containers
• PHPUnit: 101 tests, 267 assertions; a second run takes 8 seconds
• A post created on the development site survives the test run
• WP_ENV_PHP_VERSION=8.3 npm run test:php runs on PHP 8.3.35 and passes
• Jest 59 of 59, lint:all passes