You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe your use case and the problem you are facing
When working with the Behat tests, I'd like to be able to step debug the actual WP CLI + WordPress code which is being run.
Describe the solution you'd like
Add a WP CLI environmental variable to enable Xdebug, which would prepend any WP CLI commands run by Behat with Xdebug environmental variables to enable it.
Feature Request
Describe your use case and the problem you are facing
When working with the Behat tests, I'd like to be able to step debug the actual WP CLI + WordPress code which is being run.
Describe the solution you'd like
Add a WP CLI environmental variable to enable Xdebug, which would prepend any WP CLI commands run by Behat with Xdebug environmental variables to enable it.
WP_CLI_TEST_XDEBUG=true composer behat
In wp-cli/wp-cli/php/WP_CLI/Process.php:73 add:
Drawbacks:
Definitely slower. And I seem to have to click play often, but maybe that's just a PhpStorm setting I've got wrong.
Alternatives:
Edit every Behat feature to add
XDEBUG_CONFIG="idekey=WP_CLI_XDEBUG remote_connect_back=1 log_level=0" XDEBUG_MODE=debug
as needed.I seem to need
XDEBUG_SESSION=1
sometimes – I certainly did not need it when I opened the issue.The text was updated successfully, but these errors were encountered: