-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add export content parsers tests #181
Conversation
@@ -23,6 +23,7 @@ phpcs.xml.dist | |||
/source/wp-content/mu-plugins/* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe need to add /source/wp-content/tests/*
here then un-ignore phpunit
to make docker load tests...
22e6f72
to
406e4c2
Compare
@adamwoodnz I just pushed a few changes that get the tests to work in docker — I've set this up a few times :) I used WordPress/wporg-mu-plugins#299 as the most recent reference. Make sure to run the following to to get the polyfill package, and update the containers with the new yarn wp-env stop
composer install # or composer update
yarn wp-env start |
Thanks so much! That's awesome |
…nifest (#247) * Update parsers This includes the updates from WordPress/wordpress.org#90, a new AttributeParser for attribute-only blocks, and a fix for the ListItem block to allow child lists. Fixes #211 * Add phpunit test infrastructure and tests Pulled from #181 * Remove swag page from manifest * Update content with new parser * Add a phpunit workflow
Fixes #179
Props @iandunn
How to test the changes in this Pull Request: