Writing PHPUnit tests: Difference between revisions

Latest revision as of 22:48, 13 August 2025

Important:

This content of this page has been updated and migrated to the new Moodle Developer Resources. The information contained on the page should no longer be seen up-to-date.

Why not view this page on the new site and help us to migrate more content to the new site!

@@ Line 1: / Line 1: @@
-{{Moodle 2.3}}
+{{Template:Migrated|newDocId=/docs/guides/testing/}}
-Moodle PHPUnit integration is designed to allow easy adding of new tests. At the start of each test the state is automatically reset to fresh new installation (unless explicitly told not to reset). Tests that need to modify default installation may use generators to create new courses, users, etc.
-=TODO=
-TODO: write more info here
-=Long tests=
-All standard test should execute as fast as possible. Tests that take a loner time to execute (>10s) or are otherwise expensive (such as querying external servers that might be flooded by all dev machines) should be execute only when PHPUNIT_LONGTEST is true. This constant can be set in phpunit.xml or directly in config.php.
-=See also=
-* [[PHPUnit integration]]
-[[Category:Unit testing]]

Documentation

Writing PHPUnit tests: Difference between revisions

Latest revision as of 22:48, 13 August 2025