Skip to content

The phpunit init commands could be prefixed by public/ #1619

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lucaboesch wants to merge 1 commit into
base: main
Choose a base branch
from
Open

The phpunit init commands could be prefixed by public/ #1619

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions general/development/tools/phpunit/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down Expand Up @@ -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
Expand Down
Loading