#Debugger phpstorm code
Set a breakpoint in your code by doing any of the following:Ĭlick the left gutter area at a line where you want to toggle a breakpoint. Debugging ports are set at the PhpStorm level on the PHP | Debug page of the Settings dialog ( Control+Alt+S). After that PhpStorm starts listening to the port of the debugging engine used in the current project. Toggle the Start Listen PHP Debug Connections button ( in the classic UI) on the PhpStorm toolbar or status bar so that it changes to. If you check the debug tab of the subprocess you’ll see “Cannot find a local copy of the file on server /var/This is why we uncheck “Force break at first line when no path mapping specified”.You can also Validate the Configuration of a Debugging Engine in PhpStorm to make sure that the provided configuration parameters are correct.Įnable listening to incoming debugging connections When you debug the test you will see the debugger pauses with two tabs, one for the Kernel test and one for “Standard input code”, which is the subprocess. We also need to ensure the PHP_IDE_CONFIG env var is actually set in the subprocess. To intercept the subprocess we need to make sure we’re listening for connections first. See KernelTestBase::runTestInSeparateProcess. Kernel tests run in a separate PHP process which means PHPStorm has a harder time dealing with them. In ddev you can use which is the internal connection string for the database, or for better performance use sqlite://localhost/sites/simpletest/db.sqlite We need to make sure the database configured in SIMPLETEST_DB is accessible to the remote PHP interpreter. Just make sure you have xdebug enabled ( ddev xdebug on).
These should essentially “just work” as they run in a single process with no database, you don’t even need to be listening for connections. It's best to refer to the video above for these, but some brief info below. chrome:$DDEV_HOSTNAME Running and debugging tests Will be fixed in ddev soon.Ĭontainer_name: ddev-$ # DDev already sets this, add it here to debug Kernel tests.
#Debugger phpstorm full
Add the following files then run ddev restart to regenerate the full docker-compose file. Fortunately we can extend the generated docker-compose file by adding extra files in the. There are a few extra parts we need for running every kind of test. For now you can revert ddev's docker-compose version with the following command:ĭdev config global -required-docker-compose-version=v1.29.2įor the most part DDev configures everything we need to use xdebug in PHPStorm. This defaults to v2 which still has some compatibility issues with PHPStorm.
#Debugger phpstorm update
UPDATE JANUARY 2022 - Since v1.18.2 ddev now ships its own docker-compose version. Default config file - /var/www/html/phpunit.xml.PHPUnit library - Use Composer autoloader, set to absolute path in container, i.e.From the add dropdown choose PHPUnit by Remote Interpreter, then choose the one we set up already.CLI Interpreter: choose the interpreter we set up previously.Path to composer.json - absolute path on your local machine.You don’t need to map the web root or vendor dir since you’re mapping the entire project.home/michael/www/drupal -> /var/www/html
This setting allows us to listen on multiple ports. Note that xdebug 3 uses 9003 by default whereas xdebug 2 uses 9000. This should be set for you automatically.
You may be able to achieve the same result with an alternative docker-compose environment, but I'm using DDev here since it mostly works out of the box. You can also checkout the ddev-phpunit-demo repo if you want to try it out yourself with DDev and PHPUnit pre-configured. Drupal Test Traits / Selenium2DriverTests.
#Debugger phpstorm how to
Have a look at the video below that demonstrates how to configure everything you need to run and debug:
0 kommentar(er)
