Multi PHP + Multi Environment + Check all commits

.env.default

@@ -11,12 +11,16 @@
 # $ source .env
 ###
 
+# Label for the environment. Can be empty (default) or be like "shared", "vps", "cloud" or similar.
+# Please use only alphanumeric keywords, and try to be descriptive
+export WPT_LABEL=
+
 # Path to the directory where files can be prepared before being delivered to the environment.
 export WPT_PREPARE_DIR=/tmp/wp-test-runner
 
 # Path to the directory where the WordPress develop checkout can be placed and tests can be run.
 # When running tests in the same environment, set WPT_TEST_DIR to WPT_PREPARE_DIR
-export WPT_TEST_DIR=wp-test-runner
+export WPT_TEST_DIR=/tmp/wp-test-runner
 
 # API key to authenticate with the reporting service in 'username:password' format.
 export WPT_REPORT_API_KEY=
@@ -38,6 +42,9 @@ export WPT_TABLE_PREFIX=${WPT_TABLE_PREFIX-wptests_}
 # (Optionally) define the PHP executable to be called
 export WPT_PHP_EXECUTABLE=${WPT_PHP_EXECUTABLE-php}
 
+# (Optionally) array of versions (like: 8.0+/bin/php8.0,8.1+/bin/php8.1)
+export WPT_PHP_EXECUTABLE_MULTI=
+
 # (Optionally) define the PHPUnit command execution call.
 # Use if `php phpunit.phar` can't be called directly for some reason.
 export WPT_PHPUNIT_CMD=
@@ -63,16 +70,21 @@ export WPT_DEBUG=
 
 # Certificate validation
 # Use 1 to validate, and 0 to not validate
-export WPT_CERTIFICATE_VALIDATION=1
+export WPT_CERTIFICATE_VALIDATION=0
 
 # WordPress flavor
 # 0 = WordPress (simple version)
 # 1 = WordPress Multisite
-export WPT_FLAVOR=1
+export WPT_FLAVOR=0
 
 # Extra tests (groups)
 # 0 = none
 # 1 = ajax
 # 2 = ms-files
 # 3 = external-http
 export WPT_EXTRATESTS=0
+
+# Check all commits
+# 0 = latest
+# 1 = all
+export WPT_COMMITS=0

cleanup.php

@@ -24,30 +24,94 @@
 $WPT_SSH_CONNECT     = trim( getenv( 'WPT_SSH_CONNECT' ) );
 $WPT_SSH_OPTIONS     = trim( getenv( 'WPT_SSH_OPTIONS' ) ) ? : '-o StrictHostKeyChecking=no';
 $WPT_TEST_DIR        = trim( getenv( 'WPT_TEST_DIR' ) );
-$WPT_RM_TEST_DIR_CMD = trim( getenv( 'WPT_RM_TEST_DIR_CMD' ) ) ? : 'rm -r ' . $WPT_TEST_DIR;
+$WPT_PHP_EXECUTABLE_MULTI = trim( getenv( 'WPT_PHP_EXECUTABLE_MULTI' ) ) ? : '';
 
 /**
- * The directory path of the test preparation directory is assumed to be previously defined.
- * For example: $WPT_PREPARE_DIR = '/path/to/your/preparation/dir';
- * Clean up the preparation directory.
- * Forcefully deletes only the .git directory and the node_modules cache.
- * Afterward, the entire preparation directory is removed to ensure a clean state for the next test run.
  */
-perform_operations( array(
-	'rm -rf ' . escapeshellarg( $WPT_PREPARE_DIR . '/.git' ),
-	'rm -rf ' . escapeshellarg( $WPT_PREPARE_DIR . '/node_modules/.cache' ),
-	'rm -r ' . escapeshellarg( $WPT_PREPARE_DIR ),
-) );
+$WPT_PHP_EXECUTABLE_MULTI_ARRAY = array();
+if ( '' !== $WPT_PHP_EXECUTABLE_MULTI ) {
 
-/**
- * Cleans up the test directory on a remote server.
- * This conditional block checks if an SSH connection string is provided and is not empty.
- * If a connection string is present, it triggers a cleanup operation on the remote environment.
- * The cleanup operation is executed by the `perform_operations` function which takes an array
- * of shell commands as its input.
- */
-if ( ! empty( $WPT_SSH_CONNECT ) ) {
+	$php_multi_versions = explode( ',', $WPT_PHP_EXECUTABLE_MULTI );
+
+	foreach( $php_multi_versions as $php_multi_version ) {
+
+		$php_multi_v = explode( '+', $php_multi_version );
+
+		if( isset( $php_multi_v[0] ) && $php_multi_v[0] && isset( $php_multi_v[1] ) && $php_multi_v[1] ) {
+			$WPT_PHP_EXECUTABLE_MULTI_ARRAY[] = array( 'version' => trim( $php_multi_v[0] ), 'bin' => trim( $php_multi_v[1] ) );
+		}
+
+		unset( $php_multi_version );
+	}
+
+	unset( $php_multi_versions );
+}
+
+if( count( $WPT_PHP_EXECUTABLE_MULTI_ARRAY ) ) {
+
+	foreach( $WPT_PHP_EXECUTABLE_MULTI_ARRAY as $php_multi ) {
+
+		$WPT_PREPARE_DIR_MULTI = $WPT_PREPARE_DIR . '-' . crc32( $php_multi['version'] );
+		$WPT_TEST_DIR_MULTI = $WPT_TEST_DIR . '-' . crc32( $php_multi['version'] );
+
+		$WPT_RM_TEST_DIR_CMD = trim( getenv( 'WPT_RM_TEST_DIR_CMD' ) ) ? : 'rm -r ' . $WPT_TEST_DIR_MULTI;
+
+		/**
+		 * The directory path of the test preparation directory is assumed to be previously defined.
+		 * For example: $WPT_PREPARE_DIR = '/path/to/your/preparation/dir';
+		 * Clean up the preparation directory.
+		 * Forcefully deletes only the .git directory and the node_modules cache.
+		 * Afterward, the entire preparation directory is removed to ensure a clean state for the next test run.
+		 */
+		perform_operations( array(
+			'rm -rf ' . escapeshellarg( $WPT_PREPARE_DIR_MULTI . '/.git' ),
+			'rm -rf ' . escapeshellarg( $WPT_PREPARE_DIR_MULTI . '/node_modules/.cache' ),
+			'rm -r ' . escapeshellarg( $WPT_PREPARE_DIR_MULTI ),
+		) );
+
+		/**
+		 * Cleans up the test directory on a remote server.
+		 * This conditional block checks if an SSH connection string is provided and is not empty.
+		 * If a connection string is present, it triggers a cleanup operation on the remote environment.
+		 * The cleanup operation is executed by the `perform_operations` function which takes an array
+		 * of shell commands as its input.
+		 */
+		if ( ! empty( $WPT_SSH_CONNECT ) ) {
+			perform_operations( array(
+				'ssh ' . $WPT_SSH_OPTIONS . ' ' . escapeshellarg( $WPT_SSH_CONNECT ) . ' ' . escapeshellarg( $WPT_RM_TEST_DIR_CMD ),
+			) );
+		}
+
+	}
+
+} else {
+
+	$WPT_RM_TEST_DIR_CMD = trim( getenv( 'WPT_RM_TEST_DIR_CMD' ) ) ? : 'rm -r ' . $WPT_TEST_DIR;
+
+	/**
+	 * The directory path of the test preparation directory is assumed to be previously defined.
+	 * For example: $WPT_PREPARE_DIR = '/path/to/your/preparation/dir';
+	 * Clean up the preparation directory.
+	 * Forcefully deletes only the .git directory and the node_modules cache.
+	 * Afterward, the entire preparation directory is removed to ensure a clean state for the next test run.
+	 */
 	perform_operations( array(
-		'ssh ' . $WPT_SSH_OPTIONS . ' ' . escapeshellarg( $WPT_SSH_CONNECT ) . ' ' . escapeshellarg( $WPT_RM_TEST_DIR_CMD ),
+		'rm -rf ' . escapeshellarg( $WPT_PREPARE_DIR . '/.git' ),
+		'rm -rf ' . escapeshellarg( $WPT_PREPARE_DIR . '/node_modules/.cache' ),
+		'rm -r ' . escapeshellarg( $WPT_PREPARE_DIR ),
 	) );
-}
+
+	/**
+	 * Cleans up the test directory on a remote server.
+	 * This conditional block checks if an SSH connection string is provided and is not empty.
+	 * If a connection string is present, it triggers a cleanup operation on the remote environment.
+	 * The cleanup operation is executed by the `perform_operations` function which takes an array
+	 * of shell commands as its input.
+	 */
+	if ( ! empty( $WPT_SSH_CONNECT ) ) {
+		perform_operations( array(
+			'ssh ' . $WPT_SSH_OPTIONS . ' ' . escapeshellarg( $WPT_SSH_CONNECT ) . ' ' . escapeshellarg( $WPT_RM_TEST_DIR_CMD ),
+		) );
+	}
+
+}

commits.json

@@ -0,0 +1,5 @@
+{
+  "executed_commits": [],
+  "pending_commits": [],
+  "testing_commit": []
+}

commits.json.example

@@ -0,0 +1,5 @@
+{
+  "executed_commits": ["hash3"],
+  "pending_commits": ["hash1", "hash2", ..., "hash10"],
+  "testing_commit": ["hash4"]
+}

docs/0-intro.md

@@ -0,0 +1,15 @@
+# About the PHPUnit Test Runner
+
+Hosting companies can have several to millions of websites hosted with WordPress, so it's important to make sure their configuration is as compatible as possible with the software.
+
+To verify this compatibility, the WordPress Community provides a series of PHPUnit tests with which to check the operation of WordPress in any environment.
+
+The Runner tests generates a report with the test results related to a bot user (a hosting company), and this captures and displays those test results at the [Host Test Result](https://make.wordpress.org/hosting/test-results/) page.
+
+## What's the phpunit-test-runner
+
+The [phpunit-test-runner](https://github.com/WordPress/phpunit-test-runner) is a tool designed to make it easier for hosting companies to run the WordPress project’s automated tests.
+
+There is a [whole documentation about this tool](https://make.wordpress.org/hosting/test-results-getting-started/). Also, if you want, you can make your test results appear in the [Host Test Results](https://make.wordpress.org/hosting/test-results/) page of WordPress.
+
+The tool can be run manually or through an automated system like Travis. To see how it works and the purpose of this document, will be shown how to run the tests manually.