Migrate test infrastructure to wp-test-utils#142
Merged
Conversation
Aligns the test infrastructure with the a8c-plugins standard by using yoast/wp-test-utils bootstrap pattern with conditional WordPress loading. The bootstrap now only loads WordPress when the integration testsuite is requested, and tests are relocated from tests/unit/ to tests/Integration/ to reflect their true nature as integration tests requiring a full WordPress environment.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The test bootstrap and configuration still used the old
yoast/phpunit-polyfillspattern directly, even thoughdevelopalready listsyoast/wp-test-utilsincomposer.json. This PR completes the migration by adopting the wp-test-utils bootstrap pattern from the plugin standards, bringing zoninator in line with the other a8c-plugins.The bootstrap now conditionally loads WordPress only when the
integrationtestsuite is requested, usingWPIntegration\bootstrap_it()for path resolution and environment setup. Tests have been relocated fromtests/unit/totests/Integration/to accurately reflect that they are integration tests requiring a full WordPress environment, and the test file has been renamed to follow PSR-4 conventions. The test class is now namespaced underAutomattic\Zoninator\Tests\Integrationand extends a localTestCasebase class that wrapsYoast\WPTestUtils\WPIntegration\TestCase.Test plan