-
For now, the project only contains **unit tests**, which doesn't require a full WordPress environment to be triggered. Sooner or later, we will need to connect this project with WordPress itself, so w…
-
## What problem does this address?
Currently there is some duplication of block test fixtures between Gutenberg plugin and WordPress core, and 3rd party plugins can't easily access and make use of th…
-
I think we need to move the factory set up to a different setter for php8. It's throwing errors in php8 pipelines. Not 100% sure if that's the right way to fix this.
https://github.com/penske-medi…
-
https://wordpress.slack.com/archives/C3D6T7F8Q/p1593596189094100
-
Environment information collection happens via a string replacement on https://github.com/WordPress/phpunit-test-runner/blob/master/prepare.php#L91.
This means that if the comments in `wp-tests-con…
-
The theme is getting larger and more complex and is lacking in tests. This is the best testing framework I've been able to find:
http://stackoverflow.com/questions/9138215/unit-testing-wordpress-plug…
-
### Reproduction Steps
The LifterLMS unit tests that use the `@runInSeparateProcess` annotation return an error and are not tested when run with PHP 8.0 and Windows 10.
The tests are successful …
-
Most of the plugin code is not tested with unit tests. And I'm not certain whether I'm Doing It Right™ or not with the current basic tests.
-
WordPress Core currently runs PHPUnit tests in two steps.
The first step checks out the WordPress repo, installs NPM, builds WP for use, and then zips everything to upload as an artifact on the wor…
-
Normally I'd do something like `patch -p0 -R < patch_file_path.patch` but if I'm using the (really rather brilliant) `grunt patch:` then I don't have the file locally in order to undo that... do I?