Previously, both unit and integration tests used the same base test class. While this worked, integration tests weren't using the polyfilled WP_UnitTestCase case from the wp-test-utils package.
This, in turn, meant that the tests weren't properly cleaned up and that some usefull features, like WordPress test factories couldn't be used easily in the integration tests.
This commit fixes this issue.
The caveat is that, because of how Pest works, we cannot just define the uses statement in the Pest.php file, because the WordPress unit test class becomes available after the bootstrap process. For more details see the issue https://github.com/pestphp/pest/issues/623.
Checklist:
[x] My code is tested.
[x] My code follows the code style set by the project.
Description
Previously, both unit and integration tests used the same base test class. While this worked, integration tests weren't using the polyfilled WP_UnitTestCase case from the wp-test-utils package.
This, in turn, meant that the tests weren't properly cleaned up and that some usefull features, like WordPress test factories couldn't be used easily in the integration tests.
This commit fixes this issue.
The caveat is that, because of how Pest works, we cannot just define the
usesstatement in thePest.phpfile, because the WordPress unit test class becomes available after the bootstrap process. For more details see the issue https://github.com/pestphp/pest/issues/623.Checklist: