c23d5edb0f
One of the error levels PHP previously emitted was E_STRICT, on code that was not strictly correct to ensure interoperability and forward compatibility. PHP 7.0 converted the majority of existing E_STRICT warnings to E_NOTICE, and since PHP 8.0, all E_STRICT notices have changed to E_NOTICE. Because all of the E_STRICT notices are upgraded to E_NOTICE since PHP 8.0, PHP 8.4 deprecates the E_STRICT constant. The E_STRICT constant is deprecated in PHP 8.4. Using the constant anywhere in PHP code now emits a deprecation notice in PHP 8.4 and later. The E_STRICT constant will be removed in PHP 9.0. PHP core and core extensions since PHP 8.0 and later do not emit E_STRICT notices at all. It is safe to assume that any PHP applications that run on PHP 8.0 and later will never encounter E_STRICT notices, and error reporting and handling can be safely updated to ignore E_STRICT notices. See: https://php.watch/versions/8.4/E_STRICT-deprecated Signed-off-by: Daniel Ziegenberg <daniel@ziegenberg.at>
PHPUnit testing support in Moodle
Documentation
- Moodle PHPUnit integration
- Moodle Writing PHPUnit tests
- PHPUnit online documentation
- Composer dependency manager
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/phpunitfrom dirroot directory - you can execute a single test case class using class name followed by path to test file
vendor/bin/phpunit 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.phpfile withmy_testclass that extendsbasic_testcaseoradvanced_testcase - set the test class namespace to that of the class being tested
- add some
test_*()methods - execute your new test case
vendor/bin/phpunit local/mytest/tests/my_test.php - execute
php admin/tool/phpunit/cli/init.phpto get the plugin tests included in main phpunit.xml configuration file
Windows support
- use
\instead of/in paths in examples above