Note: You are currently viewing documentation for Moodle 3.11. Up-to-date documentation for the latest stable version of Moodle may be available here: Unit tests.

Unit tests: Difference between revisions

From MoodleDocs
mNo edit summary
(redirect to dev docs)
 
Line 1: Line 1:
administration > reports> Unit tests
#redirect [[:dev:Unit tests]]
 
The Unit Test report is a tool for developers to let them automatically test various parts of the Moodle code.
 
You are advised not to run the unit tests on a production site (unless you are sure you know what you are doing). There are two main reasons for this recommendation:
# The tests involve a lot of processing, and so will slow down your Moodle for all your other users for a while.
# Some of the tests involve adding and deleting data from the database. This should be done in a reversible way, but if there is a bug in the test code, it might damage the real data in the database.
 
On the other hand, if you are doing development, then running the tests on your development server is strongly encouraged, as is writing new tests.
 
==Filters for report==
 
[[Image:Reports_Unit_Tests_1.jpg]]
 
==Example report==
 
[[Image:Reports Site Unit Test Example 1.jpg|thumb|center|500px|Example of unit test]]
 
==See also==
 
* [[Development:Unit tests]]
* [[Site reports]]

Latest revision as of 11:50, 19 October 2011

Redirect to: