XDebug with WP-Setup

Introduction

WP Setup has been updated to version 1.1.0, introducing Xdebug support and allowing for easy generation of test coverage reports.

Additionally, some small fixes and improvements were made, such as using the adm-zip library instead of unzipper, providing a simpler and reliable extractor that avoids uncompress errors as with Query Monitor (that we add by default in wp-setup.json during the initialization process) that in some cases did not complete the unzip process correctly, causing errors during WordPress loading.

Running XDebug

Now we can simple start the containers with XDebug running by adding a --xdebug flag in the start command. This will restart all server and CLI containers with the xdebug up and running.

You can use the recommended scripts in wp-setup readme to easily start with the command npm run env:start:xdebug.

With this, you can use XDebug in all environments, enabling debugging of CLI commands, tests (facilitating a better TDD approach in development), and normal HTTP executions through the server.

To only stop the XDebug when not needed, you can run the stop command with the flag --xdebug or with our package scripts run npm run env:stop:xdebug.

Mapping directories

As we are running inside docker containers, we need to map our local directories with the container ones so we can fully use the debugger with our IDE.

In VSCode for example this can be easily done by adding the following .vscode/launch.json file:

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Listen for XDebug",
            "type": "php",
            "request": "launch",
            "port": 9003,
            "pathMappings": {
                "/var/www/html/wp-content/plugins/my-plugin": "${workspaceFolder}/plugins/my-plugin",
            }
        }
    ]
}

Replace the pathMappings with your project directories accordingly

With this we can go to VSCode debug tab and click in "Listen for XDebug".

Tests coverage repport

An important aspect of any development project is to measure how much of our code is tested. This allows us to gauge the reliability of our codebase before sending it to production.

The CLI test container now starts with XDebug in "coverage" mode by default, enabling the generation of this report.

Currently, it is not possible to run --coverage directly with our global-pest command, to use the cli coverage (very usefull to enforce a minimal test coverage in CI processes) you need to require pest and yoast/phpunit-polyfills locally in your project.

composer require --dev pestphp/pest yoast/phpunit-polyfills

then you can run your tests with your locally installed pest with:

npx wp-setup run -w . wp-test-cli ./vendor/bin/pest

This will give you full pest CLI access and allow the use of --coverage flag.

Conclusion

This latest update, introduces important enhancements, which are designed to streamline and enhance your WordPress development experience. While the new features enhance the local development process by introducing powerful debugging and testing capabilities, it is important to note that the WP Setup is not yet fully optimized for running CI processes directly. However, the groundwork has been laid, paving the way for future enhancements that will support more robust CI integrations.

As the sole developer behind WP Setup, I invite other developers to explore the potential of this tool. Your feedback and contributions are invaluable to not only improve its existing features but also to help in expanding its capabilities. The project is open for contributions on GitHub, and I am eager to collaborate with other developers to make WP Setup even more powerful and versatile.

Please take this opportunity to test WP Setup. Together, we can work towards making a comprehensive development tool that better serves the WordPress community.