mirror of https://github.com/moodle/moodle.git synced 2025-07-10 00:46:32 +02:00

Files

Eloy Lafuente (stronk7) 032c75ec43 MDL-65204 phpunit: tweak constraint_object_is_equal_with_exceptions

In PHPUnit 7.x and above, IsEqual->value became private and, as far
as our with exceptions class inherits from it, we cannot access to
that anymore.

So, in order to avoid that, we are overriding the constructor, capturing
the original value for own use and forgetting.

A more formal, alternative, solution would be to make our
exceptional class to inherit from Constraint and make the
class a pure dispatcher to different constraints, with IsEqual being
just one of them.

But we followed the easiest path here. Not ideal, but efective.

2019-04-03 10:39:19 +08:00

classes

MDL-65204 phpunit: tweak constraint_object_is_equal_with_exceptions

2019-04-03 10:39:19 +08:00

tests

MDL-61742 messaging: Do not send messages from inactive providers

2018-08-31 12:15:30 +02:00

bootstrap.php

MDL-63811 phpunit: Fix typo in new allowed config variable

2018-10-30 09:15:59 +10:30

bootstraplib.php

…

lib.php

…

phpunit.xsd

MDL-60611 phpunit: switch to namespaced phunit classes

2017-11-02 23:45:34 +01:00

readme.md

…

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 with local_my_testcase class that extends basic_testcase or advanced_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