- 🇺🇸United States mlncn Minneapolis, MN, USA
Reopening as documentation cannot in itself replace a good developer UX.
Is there a reason this critical file for running tests, including tests for contrib and custom modules, has to live in /core and not somewhere it can work like a standard scaffolding file?
Having to do non-standard things just to keep your own tests running as you update Drupal core is surely holding back more widespread testing. (Or maybe this is documentation, if the other phpunit.xml file at project root can be used instead, but its phpunit.xml.dist has none of the needed info.)
- 🇪🇪Estonia pjotr.savitski
I've just had the of restoring the phpunit.xml file after updating the core and it seems that a better solution might be to just put the configuration file outside of web/core and then change the path to the bootstrap file (Example:
bootstrap="web/core/tests/bootstrap.php"). Running the code from project root where configuration file is situated should work as expected./vendor/bin/phpunit --stop-on-fail /path/to/direcotry/or/test/file.Using an IDE like PhpStorm allows setting location for both files, but just changing the path would do the trick.