Unify test command naming with wordpress-develop test commands

Author: JanJakes

.github/workflows/wp-tests-phpunit-run.js

@@ -1,5 +1,5 @@
 /*
- * Wrap the "composer run wp-tests-phpunit" command to process tests
+ * Wrap the "composer run wp-tests-php" command to process tests
  * that are expected to error and fail at the moment.
  *
  * This makes sure that the CI job passes, while explicitly tracking
@@ -108,7 +108,7 @@ console.log( 'Expected failures:', expectedFailures );
 try {
 	try {
 		execSync(
-			`composer run wp-test-phpunit -- --log-junit=phpunit-results.xml --verbose`,
+			`composer run wp-test-php -- --log-junit=phpunit-results.xml --verbose`,
 			{ stdio: 'inherit' }
 		);
 		console.log( '\n⚠️ All tests passed, checking if expected errors/failures occurred...' );

.github/workflows/wp-tests-phpunit.yml

@@ -1,4 +1,4 @@
-name: WordPress Tests
+name: WordPress PHPUnit Tests
 
 on:
   push:
@@ -31,7 +31,7 @@ jobs:
         run: composer run wp-test-start
 
       - name: Run WordPress PHPUnit tests
-        run: node .github/workflows/wp-tests-phpunit-run.js
+        run: node .github/workflows/wp-tests-php-run.js
 
       - name: Stop Docker containers
         if: always()

composer.json

@@ -49,7 +49,7 @@
 			"npm --prefix wordpress run env:start",
 			"npm --prefix wordpress run env:install"
 		],
-		"wp-test-phpunit": [
+		"wp-test-php": [
 			"rm -rf wordpress/src/wp-content/database && npm --prefix wordpress run test:php --"
 		],
 		"wp-test-clean": [