mirror of
https://github.com/moodle/moodle.git
synced 2025-08-04 16:36:37 +02:00
![]() PHPUnit 9 comes with various changes in the XML configuration file, namely: - the old "filter" section has been renamed to "coverage". - "whitelist" has been renamed to "include" - "exclude" is not a child of "include" anymore, but of "coverage". - "include" cannot have configuration attributes anymore, only "coverage" can" Visually it means that the old section (invented example): ``` <filter> <whitelist attributes_may_go_here="xx"> <directory suffix=".php">classes</directory> <directory suffix=".php">externallib.php</directory> <exclude> <directory suffix="_test.php">.</directory> </exclude> </whitelist> </filter> ``` Now looks like: ``` <coverage attributes_may_go_here="xx"> <include> <directory suffix=".php">classes</directory> <directory suffix=".php">externallib.php</directory> </include> <exclude> <directory suffix="_test.php">.</directory> </exclude> </filter> ``` So, switching to the new xsd so we can validate the remaining changes. |
||
---|---|---|
.. | ||
classes | ||
tests | ||
bootstrap.php | ||
bootstraplib.php | ||
lib.php | ||
phpunit.xsd | ||
readme.md |
PHPUnit testing support in Moodle
Documentation
Composer installation
Composer is a dependency manager for PHP projects. It installs PHP libraries into /vendor/ subdirectory inside your moodle dirroot.
- install Composer - http://getcomposer.org/doc/00-intro.md
- install PHUnit and dependencies - go to your Moodle dirroot and execute
php composer.phar install
Configure your server
You need to create a new dataroot directory and specify a separate database prefix for the test environment, see config-dist.php for more information.
- add
$CFG->phpunit_prefix = 'phpu_';
to your config.php file - and
$CFG->phpunit_dataroot = '/path/to/phpunitdataroot';
to your config.php file
Initialise the test environment
Before first execution and after every upgrade the PHPUnit test environment needs to be initialised, this command also builds the phpunit.xml configuration files.
- execute
php admin/tool/phpunit/cli/init.php
Execute tests
- execute
vendor/bin/phpunit
from dirroot directory - you can execute a single test case class using class name followed by path to test file
vendor/bin/phpunit core_phpunit_basic_testcase lib/tests/phpunit_test.php
- it is also possible to create custom configuration files in xml format and use
vendor/bin/phpunit -c mytestsuites.xml
How to add more tests?
- create
tests/
directory in your add-on - add test file, for example
local/mytest/tests/my_test.php
file withlocal_my_testcase
class that extendsbasic_testcase
oradvanced_testcase
- add some test_*() methods
- execute your new test case
vendor/bin/phpunit local_my_testcase local/mytest/tests/my_test.php
- execute
php admin/tool/phpunit/cli/init.php
to get the plugin tests included in main phpunit.xml configuration file
Windows support
- use
\
instead of/
in paths in examples above