From d10a7516d0ddc7bf16f210a129f0fff7299f6eff Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Luca=20B=C3=B6sch?= Date: Wed, 17 Jun 2026 11:19:55 +0200 Subject: [PATCH] The phpunit init commands could be prefixed by public/ --- general/development/tools/phpunit/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/general/development/tools/phpunit/index.md b/general/development/tools/phpunit/index.md index 665cd6105..43e262749 100644 --- a/general/development/tools/phpunit/index.md +++ b/general/development/tools/phpunit/index.md @@ -103,7 +103,7 @@ Then you need to initialise the test environment using following command. ``` cd /home/example/moodle - php admin/tool/phpunit/cli/init.php + php public/admin/tool/phpunit/cli/init.php ``` This command has to be repeated after any upgrade, plugin (un)installation or if you have added tests to a plugin you are developing: @@ -249,7 +249,7 @@ It's easy to create alternative `phpunit.xml` files defining which tests must be Also, for commodity, you can use this command: ``` - php admin/tool/phpunit/cli/util.php --buildcomponentconfigs + php public/admin/tool/phpunit/cli/util.php --buildcomponentconfigs ``` It will, automatically, create one valid `phpunit.xml` file within each component (plugin or subsystem) and other important directories, so later you will be able to execute tests like