Debugging CiviCRM cheatsheet » History » Revision 3

« Previous | Revision 3/38 (diff) | Next »
Jon Goldberg, 07/03/2020 09:04 PM

Debugging CiviCRM cheatsheet

Command-line runs of PHPUnit:

From a buildkit civiroot, run a specific file's tests::

CIVICRM_UF=UnitTests phpunit5 tests/phpunit/CRM/Core/BAO/AddressTest.php

You can also limit to a single test by filtering on name:

CIVICRM_UF=UnitTests phpunit5 tests/phpunit/CRM/Core/BAO/AddressTest.php --filter testShared

With XDebug

  • You need to define an additional php.ini setting at runtime (otherwise XDebug will always be on for CLI, leading to a big loss in performance);
  • You need to specify a full path to phpunit5 (because running php <script> won't check your path for the script, just php).
  • You need to have XDebug otherwise configured for CLI. Here's the contents of my /etc/php/7.3/cli/conf.d/xdebug.ini: xdebug.remote_enable=1 xdebug.remote_autostart=1 xdebug.remote_handler=dbgp xdebug.remote_mode=req xdebug.remote_host= xdebug.remote_port=9000
  • You need to enable "Listen for XDebug" in VS Code.

Once you've got all that:

env CIVICRM_UF=UnitTests idekey=VSCODE php -dzend_extension=/usr/lib/php/20180731/ /home/jon/local/civicrm-buildkit/bin/phpunit5 /home/jon/local/civicrm-buildkit/build/dmaster/web/sites/all/modules/civicrm/tests/phpunit/CRM/Contact/Import/Parser/ContactTest.php --filter '^.*::testIgnoreLocationTypeId( .*)?$'

Updated by Jon Goldberg about 3 years ago · 3 revisions