Wp-env: Add phpunit support #20090

noahtallen · 2020-02-07T10:14:21Z

This PR allows the phpunit script to work with @wordpress/env.

Changes:

Add phpunit service to wp-env docker
Add wp_phpunit composer dependency so we don't have to use wordpress-develop
switch package.json to use wp-env for phpunit tests.

To test, run:

# Get the new composer changes.
./packages/env/bin/wp-env run composer 'composer install'  

# Run phpunit via package.json:
npm run test-unit-php

# With multisite setup:
npm run test-unit-php-multisite

# Alternatively, directly run phpunit command (the package commands are aliases for this)
./packages/env/bin/wp-env run phpunit 'phpunit -c /var/www/html/wp-content/plugins/gutenberg/phpunit.xml.dist'

External API

This works pretty well for us internally, but I think it will be difficult to use from a 3rd party perspective for a few reasons:

Currently, you are required to know the absolute path to the phpunit config file inside Docker. That will be different for every source.
You have to install the correct wp-phpunit dependency yourself.
You have to know how to setup the bootstrap and config files correctly.

See #22365 for explorations on how to improve the external API.

To do:

Should we export functions from @wordpress/env to handle things like getDockerComposeDir? (or even for reading the config file if needed.)
Provide a phpunit service in the default docker config. (Similar to the WordPress one we used before.)
verify multisite tests also work
verify exit code is 1 if tests fail
use different tests port in travis to avoid conflicting with scripts/env
verify php version from LOCAL_PHP is used in phpunit environment
make sure wordpress is installed before continuing
make sure we have permissions to rename files in travis

epiqueras

Should we export functions from @wordpress/env to handle things like getDockerComposeDir? (or even for reading the config file if needed.)

The wp-env run command removes the need for any of that.

Provide a phpunit service in the default docker config. (Similar to the WordPress one we used before.)

Sure

In order to remove the wp-env package.json field, what if we added a primaryPluginDir field to the .wp-env.json file? If not, we'll need to pass it through args and/or default to cwd.

It should be cwd like with other scripts.

noahtallen · 2020-02-07T23:15:00Z

Thanks, @epiqueras! I've modified this to call wpEnv.run instead (which adds a dependency on @wordpress/env.)

Though this raises the question: is test-php/phpcs needed anymore?

In a project, I can add: "test:php": "wp-env run phpunit phpunit -c /var/www/src/wp-content/plugins/full-site-editing-plugin/phpunit.xml.dist", to my package.json file and it should work so long as we have a phpunit service in the default docker config (which I'll look at adding next)

epiqueras · 2020-02-07T23:21:00Z

I guess we need them for backwards compatibility. I don’t think importing wp-env is a good idea. Why not make it a peer dependency and invoke the bin file like the other scripts do.

noahtallen · 2020-02-08T02:15:16Z

so long as we have a phpunit service in the default docker config

I've added the basic configuration for the phpunit service but ran into an issue. Previously, we always used the wordpress-develop repository, which includes the WordPress test files all the required bootstrapping. Since we are now using the production image, those directories don't exist.

This means that WordPress phpunit bootstrap scripts will fail (like this):

gutenberg/phpunit/bootstrap.php

Lines 28 to 31 in 4030f73

    
           // Give access to tests_add_filter() function. 
        
           require_once $_tests_dir . '/includes/functions.php';

It's possible we'll have to add a requirement to use WordPress/wordpress-develop in order to run phpunit. Otherwise, we'll have to make sure those test files are downloaded to the Docker image somehow.

epiqueras · 2020-02-08T02:29:21Z

Ideally, the test bootstrap code would be a separate composer package that we load in isolation. I've heard that was planned for Core, but it's not a priority. The issue with adding the requirement to use wordpress-develop is that we force ourselves to build it and lose the excellent speed wp-env start has right now.

epiqueras · 2020-02-08T02:30:15Z

Maybe we should require it only for that test script.

gziolo · 2020-02-19T06:52:52Z

@noahtallen - nice to see progress on migrating PHPUnit tests to wp-env 💯

Is it necessary to update wp-scripts env to make it work? It feels like we are going to deprecate the whole env subset of scripts and advice to use wp-env instead. Once everything is working with wp-env on Travis, there is no reason to keep two competing implementations.

epiqueras · 2020-02-19T13:42:11Z

Agreed, I'd rather see this PR deprecating wp-scripts env and replacing its usage with wp-env everywhere instead of doing it in a follow-up. It will help catch any possible bugs.

noahtallen · 2020-02-19T18:08:23Z

Definitely agree! How would we go about deprecating those scripts? Is there a previous example I could look at for how we typically handle these things?

(Or do we just delete those files and the references to them and move on?)

replacing its usage with wp-env everywhere

I think we'll only need to update phpcs and phpunit within the scripts package, which is convenient, but as we can see here it might not work out of the box :)

epiqueras · 2020-02-19T18:16:50Z

Use the deprecate utility to add messages, add a change-log entry, and write a dev note.

noisysocks · 2020-02-20T02:46:23Z

Ideally, the test bootstrap code would be a separate composer package that we load in isolation. I've heard that was planned for Core, but it's not a priority. The issue with adding the requirement to use wordpress-develop is that we force ourselves to build it and lose the excellent speed wp-env start has right now.

I think it's probably worth biting the bullet and doing this. A WordPress plugin that wants to use WP_UnitTestCase shouldn't have to vendor all of wordpress-develop in order to do so.

epiqueras · 2020-02-20T03:00:18Z

Agreed, who would be the best person to work on that?

noisysocks · 2020-02-20T04:58:42Z

My DMs are open if somebody is interested in doing this and needs help navigating Trac or the codebase 😄

noahtallen · 2020-02-23T23:22:07Z

My DMs are open if somebody is interested in doing this and needs help navigating Trac or the codebase

Nice :) I'm afraid my cycles got taken up by a different project at the moment, so I probably won't be able to revisit this PR for a while. (Maybe days, more likely weeks)

talldan · 2020-03-06T07:01:56Z

I haven't been able to find any reference in trac to making the unit test bootstrap a separate composer package. Would you be able to share that discussion if you can find it @epiqueras, @noisysocks?

noahtallen · 2020-03-10T19:29:09Z

Also, I'd be interested in poking around at that, but I'm not sure how much work it would take, or even what steps need to be taken to make it happen

noisysocks · 2020-03-12T23:33:03Z

I also can't find any discussion about this, but I spoke with @johnbillion who suggested that Gutenberg could use the third party wp-phpunit/wp-phpunit package, and to look at this PR for inspiration on what needs to happen: johnbillion/user-switching#38

chrisvanpatten · 2020-04-11T17:38:10Z

I would LOVE this to happen. Setting up the core unit test bootstrap is such a pain — smoothing over that with wp-env would be incredible. Are there any action items that could help move this forward?

ockham · 2020-04-30T10:45:59Z

Rebased.

- install wp-phpunit via composer - include composer autoload and config in bootstrap - add missing config options - allow service to be run without starting wp-env first

noahtallen · 2020-05-14T18:34:20Z

this PR now only exposes the phpunit and composer changes itself. it doesn't try to expose it in a nice way for other consumers. see #22365 for that.

To test, run:

# Get the new composer changes.
./packages/env/bin/wp-env run composer 'composer install'  

# Run phpunit command pointing at Gutenberg config file.
./packages/env/bin/wp-env run phpunit 'phpunit -c /var/www/html/wp-content/plugins/gutenberg/phpunit.xml.dist'

noahtallen · 2020-05-14T18:53:27Z

currently checking two things:

multisite tests (✅)
make sure that exit code is not 0 if a test fails (✅)

packages/env/lib/build-docker-compose-config.js

noahtallen · 2020-05-14T20:36:12Z

currently troubleshooting this error in CI. it looks like running the phpunit command fails because it doesn't like that tests-wordpress is already running, or something like that.

36.43s$ npm run test-php && npm run test-unit-php-multisite

> gutenberg@8.1.0 test-php /home/travis/build/WordPress/gutenberg

> npm run lint-php && npm run test-unit-php

> gutenberg@8.1.0 prelint-php /home/travis/build/WordPress/gutenberg

> npm run wp-env run composer install -- --no-interaction

> gutenberg@8.1.0 wp-env /home/travis/build/WordPress/gutenberg

> packages/env/bin/wp-env "run" "composer" "install" "--no-interaction"

- 

latest: Pulling from library/composer

Digest: sha256:7d49a2b42bf742f39e0f8e823612ab0def8a479379d9610275c28c39d746fde6

Status: Downloaded newer image for composer:latest

PHP CodeSniffer Config installed_paths set to ../../phpcompatibility/php-compatibility,../../sirbrillig/phpcs-variable-analysis,../../wp-coding-standards/wpcs

✔ Ran `install` in 'composer'. (in 11s 417ms)

> gutenberg@8.1.0 lint-php /home/travis/build/WordPress/gutenberg

> npm run wp-env run composer run-script lint

> gutenberg@8.1.0 wp-env /home/travis/build/WordPress/gutenberg

> packages/env/bin/wp-env "run" "composer" "run-script" "lint"

- 

............................................................  60 / 114 (53%)

......................................................       114 / 114 (100%)

Time: 2.89 secs; Memory: 30MB

✔ Ran `run-script lint` in 'composer'. (in 4s 695ms)

> gutenberg@8.1.0 test-unit-php /home/travis/build/WordPress/gutenberg

> wp-env run phpunit 'phpunit -c /var/www/html/wp-content/plugins/gutenberg/phpunit.xml.dist'

- 

✖ Error while running docker-compose command.

latest: Pulling from library/mariadb

Digest: sha256:d96a3364fc783c02d19c54aa81e0dcf81a339340f74a4b3a64db1e72a419f5ab

Status: Downloaded newer image for mariadb:latest

latest: Pulling from library/wordpress

Digest: sha256:19faa564fd56e817cb6057ebacd3fda84fc2b4805a477aaf9eaa495c712f9e29

Status: Downloaded newer image for wordpress:latest

Pulling mysql (mariadb:)...

Pulling tests-wordpress (wordpress:)...

Creating ce047cf4da04af20491927334fb977c6_mysql_1 ... 

ERROR: for ce047cf4da04af20491927334fb977c6_tests-wordpress_1  Cannot start service tests-wordpress: driver failed programming external connectivity on endpoint ce047cf4da04af20491927334fb977c6_tests-wordpress_1 (39fa3b493882f2ce74659df096654f2ac142838d07ba071e17d35008c329b8fa): Bind for 0.0.0.0:8889 failed: port is already allocated

ERROR: for tests-wordpress  Cannot start service tests-wordpress: driver failed programming external connectivity on endpoint ce047cf4da04af20491927334fb977c6_tests-wordpress_1 (39fa3b493882f2ce74659df096654f2ac142838d07ba071e17d35008c329b8fa): Bind for 0.0.0.0:8889 failed: port is already allocated

Encountered errors while bringing up the project.

noahtallen · 2020-05-14T20:47:50Z

Ahh. That's probably because the port is already allocated to the scripts/env instance 😆

.travis.yml

noahtallen · 2020-05-14T22:00:52Z

Hm. Now getting this error. The weird thing is that it does not cause phpunit to fail. I wonder if this could be caused by not having run the wordpress install yet 🤔

> wp-env run phpunit 'phpunit -c /var/www/html/wp-content/plugins/gutenberg/phpunit.xml.dist'

- 

latest: Pulling from library/mariadb

Digest: sha256:d96a3364fc783c02d19c54aa81e0dcf81a339340f74a4b3a64db1e72a419f5ab

Status: Downloaded newer image for mariadb:latest

latest: Pulling from library/wordpress

Digest: sha256:19faa564fd56e817cb6057ebacd3fda84fc2b4805a477aaf9eaa495c712f9e29

Status: Downloaded newer image for wordpress:latest

latest: Pulling from wordpressdevelop/phpunit

Digest: sha256:df71f7489bf95c4aa19e6de1ff581929f17d15c8a6d8a23a98310803cced0820

Status: Downloaded newer image for wordpressdevelop/phpunit:latest

<!DOCTYPE html>

<html xmlns="http://www.w3.org/1999/xhtml" dir='ltr'>

<head>

	<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />

	<meta name="viewport" content="width=device-width">

			<title>Database Error</title>

	<style type="text/css">

		html {

			background: #f1f1f1;

		}

		body {

			background: #fff;

			color: #444;

			font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Oxygen-Sans, Ubuntu, Cantarell, "Helvetica Neue", sans-serif;

			margin: 2em auto;

			padding: 1em 2em;

			max-width: 700px;

			-webkit-box-shadow: 0 1px 3px rgba(0, 0, 0, 0.13);

			box-shadow: 0 1px 3px rgba(0, 0, 0, 0.13);

		}

		h1 {

			border-bottom: 1px solid #dadada;

			clear: both;

			color: #666;

			font-size: 24px;

			margin: 30px 0 0 0;

			padding: 0;

			padding-bottom: 7px;

		}

		#error-page {

			margin-top: 50px;

		}

		#error-page p,

		#error-page .wp-die-message {

			font-size: 14px;

			line-height: 1.5;

			margin: 25px 0 20px;

		}

		#error-page code {

			font-family: Consolas, Monaco, monospace;

		}

		ul li {

			margin-bottom: 10px;

			font-size: 14px ;

		}

		a {

			color: #0073aa;

		}

		a:hover,

		a:active {

			color: #00a0d2;

		}

		a:focus {

			color: #124964;

			-webkit-box-shadow:

				0 0 0 1px #5b9dd9,

				0 0 2px 1px rgba(30, 140, 190, 0.8);

			box-shadow:

				0 0 0 1px #5b9dd9,

				0 0 2px 1px rgba(30, 140, 190, 0.8);

			outline: none;

		}

		.button {

			background: #f7f7f7;

			border: 1px solid #ccc;

			color: #555;

			display: inline-block;

			text-decoration: none;

			font-size: 13px;

			line-height: 2;

			height: 28px;

			margin: 0;

			padding: 0 10px 1px;

			cursor: pointer;

			-webkit-border-radius: 3px;

			-webkit-appearance: none;

			border-radius: 3px;

			white-space: nowrap;

			-webkit-box-sizing: border-box;

			-moz-box-sizing:    border-box;

			box-sizing:         border-box;

			-webkit-box-shadow: 0 1px 0 #ccc;

			box-shadow: 0 1px 0 #ccc;

			vertical-align: top;

		}

		.button.button-large {

			height: 30px;

			line-height: 2.15384615;

			padding: 0 12px 2px;

		}

		.button:hover,

		.button:focus {

			background: #fafafa;

			border-color: #999;

			color: #23282d;

		}

		.button:focus {

			border-color: #5b9dd9;

			-webkit-box-shadow: 0 0 3px rgba(0, 115, 170, 0.8);

			box-shadow: 0 0 3px rgba(0, 115, 170, 0.8);

			outline: none;

		}

		.button:active {

			background: #eee;

			border-color: #999;

			-webkit-box-shadow: inset 0 2px 5px -3px rgba(0, 0, 0, 0.5);

			box-shadow: inset 0 2px 5px -3px rgba(0, 0, 0, 0.5);

		}

			</style>

</head>

<body id="error-page">

	<div class="wp-die-message"><h1>Error establishing a database connection</h1></div></body>

</html>

	

✔ Ran `phpunit -c /var/www/html/wp-content/plugins/gutenberg/phpunit.xml.dist` in 'phpunit'. (in 21s 312ms)

noahtallen · 2020-05-14T22:56:49Z

Alright, I think we're down to the last error.

1) Extend_Styles_Test::test_without_built_styles

rename(/var/www/html/wp-content/plugins/gutenberg/build/editor/editor-styles.css,/var/www/html/wp-content/plugins/gutenberg/build/editor/editor-styles.css.bak): Permission denied

There's a php test that renames some CSS files and we don't have permission to do that in travis with wp-env apparently

noahtallen · 2020-05-14T23:46:23Z

phpunit tests look good in Travis now. just some intermittent e2e failures now, so rerunning those.

ockham · 2020-07-07T15:10:41Z

packages/env/lib/config.js

+					WP_TESTS_DOMAIN: 'example.org',
+					WP_PHP_BINARY: 'php',


I'm not sure this is working 🤔 -- at least not for me 🙁

This is the readConfig function, which is used by init-config.js to write the docker-compose.yml file (via build-docker-compose-config.js). But AFAICS, none of those files evaluate the contents of the config object. And if I check my ~/wp-env/12345678/docker-compose.yml, I don't see any of those config constants either. 🤔

Right, the constants are not added to the docker compose config, but set with wp-cli:

gutenberg/packages/env/lib/wordpress.js

Lines 95 to 112 in 066d839

// Set wp-config.php values.

for ( let [ key, value ] of Object.entries( config.config ) ) {

// Ensure correct port setting from config when configure WP urls.

if ( key === 'WP_SITEURL' || key === 'WP_HOME' ) {

const url = new URL( value );

url.port = port;

value = url.toString();

}

const command = [ 'wp', 'config', 'set', key, value ];

if ( typeof value !== 'string' ) {

command.push( '--raw' );

}

await dockerCompose.run(

environment === 'development' ? 'cli' : 'tests-cli',

command,

options

);

}

This function is called during wp-env start

noahtallen changed the title ~~(WIP): Use wp-env docker config within test-php~~ (WIP): Use wp-env docker config for test-php Feb 7, 2020

noahtallen self-assigned this Feb 7, 2020

noahtallen added [Package] Env /packages/env [Package] Scripts /packages/scripts [Type] Build Tooling Issues or PRs related to build tooling labels Feb 7, 2020

epiqueras requested changes Feb 7, 2020

View reviewed changes

noahtallen mentioned this pull request Feb 8, 2020

FSE Plugin: Add phpunit tests Automattic/wp-calypso#39328

Merged

gziolo removed the [Package] Scripts /packages/scripts label Feb 19, 2020

gziolo mentioned this pull request Feb 19, 2020

Replace wp-scripts env usage with wp-env in CI. #20280

Merged

This was referenced Apr 14, 2020

Block API: Add Block Context support #21467

Merged

Build Tools: Install Composer dependencies as pre-lint step #21537

Merged

ockham force-pushed the try/phpunit-tests-with-wp-env branch from 60ea870 to 6fb0e92 Compare April 30, 2020 10:45

noahtallen force-pushed the try/phpunit-tests-with-wp-env branch 2 times, most recently from 069920e to b1d4741 Compare May 14, 2020 18:16

noahtallen mentioned this pull request May 14, 2020

Env: Better way to expose phpunit #22365

Closed

6 tasks

Create phpunit service in docker config

8c8777d

- install wp-phpunit via composer - include composer autoload and config in bootstrap - add missing config options - allow service to be run without starting wp-env first

noahtallen force-pushed the try/phpunit-tests-with-wp-env branch from b1d4741 to 8c8777d Compare May 14, 2020 18:30

noahtallen requested a review from epiqueras May 14, 2020 18:34

Add phpunit to run command

f3ff266

epiqueras approved these changes May 14, 2020

View reviewed changes

packages/env/lib/build-docker-compose-config.js Outdated Show resolved Hide resolved

noahtallen added 2 commits May 14, 2020 12:50

Use tests-wordpress for service image

66651c5

Switch multisite tests over as well

5d10814

Update tests port number for travis

4027a0a

noahtallen commented May 14, 2020

View reviewed changes

.travis.yml Show resolved Hide resolved

Add php version support to phpunit command

1670045

noahtallen added 2 commits May 14, 2020 15:03

Try starting wp-env first.

cab20b1

Set php binary once more

1da33f0

try chmod on build

1c62809

noahtallen merged commit 8044d4a into master May 15, 2020

noahtallen deleted the try/phpunit-tests-with-wp-env branch May 15, 2020 00:03

github-actions bot added this to the Gutenberg 8.2 milestone May 15, 2020

noahtallen mentioned this pull request May 19, 2020

wp-env: Set wp tests domain to localhost url #22476

Merged

6 tasks

TimothyBJacobs mentioned this pull request May 20, 2020

Add plugins endpoints #22454

Merged

6 tasks

ellatrix mentioned this pull request Jun 16, 2020

WP 5.5: merge all PHP changes #23210

Closed

12 tasks

ockham reviewed Jul 7, 2020

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Wp-env: Add phpunit support #20090

Wp-env: Add phpunit support #20090

noahtallen commented Feb 7, 2020 •

edited

Loading

epiqueras left a comment

noahtallen commented Feb 7, 2020 •

edited

Loading

epiqueras commented Feb 7, 2020 via email

noahtallen commented Feb 8, 2020

epiqueras commented Feb 8, 2020

epiqueras commented Feb 8, 2020

gziolo commented Feb 19, 2020

epiqueras commented Feb 19, 2020

noahtallen commented Feb 19, 2020

epiqueras commented Feb 19, 2020

noisysocks commented Feb 20, 2020

epiqueras commented Feb 20, 2020

noisysocks commented Feb 20, 2020

noahtallen commented Feb 23, 2020

talldan commented Mar 6, 2020

noahtallen commented Mar 10, 2020

noisysocks commented Mar 12, 2020

chrisvanpatten commented Apr 11, 2020

ockham commented Apr 30, 2020

noahtallen commented May 14, 2020

noahtallen commented May 14, 2020 •

edited

Loading

noahtallen commented May 14, 2020

noahtallen commented May 14, 2020

noahtallen commented May 14, 2020

noahtallen commented May 14, 2020

noahtallen commented May 14, 2020

ockham Jul 7, 2020

noahtallen Jul 7, 2020

	// Set wp-config.php values.
	for ( let [ key, value ] of Object.entries( config.config ) ) {
	// Ensure correct port setting from config when configure WP urls.
	if ( key === 'WP_SITEURL' \|\| key === 'WP_HOME' ) {
	const url = new URL( value );
	url.port = port;
	value = url.toString();
	}
	const command = [ 'wp', 'config', 'set', key, value ];
	if ( typeof value !== 'string' ) {
	command.push( '--raw' );
	}
	await dockerCompose.run(
	environment === 'development' ? 'cli' : 'tests-cli',
	command,
	options
	);
	}

Wp-env: Add phpunit support #20090

Wp-env: Add phpunit support #20090

Conversation

noahtallen commented Feb 7, 2020 • edited Loading

Changes:

External API

To do:

epiqueras left a comment

Choose a reason for hiding this comment

noahtallen commented Feb 7, 2020 • edited Loading

epiqueras commented Feb 7, 2020 via email

noahtallen commented Feb 8, 2020

epiqueras commented Feb 8, 2020

epiqueras commented Feb 8, 2020

gziolo commented Feb 19, 2020

epiqueras commented Feb 19, 2020

noahtallen commented Feb 19, 2020

epiqueras commented Feb 19, 2020

noisysocks commented Feb 20, 2020

epiqueras commented Feb 20, 2020

noisysocks commented Feb 20, 2020

noahtallen commented Feb 23, 2020

talldan commented Mar 6, 2020

noahtallen commented Mar 10, 2020

noisysocks commented Mar 12, 2020

chrisvanpatten commented Apr 11, 2020

ockham commented Apr 30, 2020

noahtallen commented May 14, 2020

noahtallen commented May 14, 2020 • edited Loading

noahtallen commented May 14, 2020

noahtallen commented May 14, 2020

noahtallen commented May 14, 2020

noahtallen commented May 14, 2020

noahtallen commented May 14, 2020

ockham Jul 7, 2020

Choose a reason for hiding this comment

noahtallen Jul 7, 2020

Choose a reason for hiding this comment

noahtallen commented Feb 7, 2020 •

edited

Loading

noahtallen commented Feb 7, 2020 •

edited

Loading

noahtallen commented May 14, 2020 •

edited

Loading