Acceptance testing: Difference between revisions
From MoodleDocs
No edit summary |
m (t_po, missing y) |
||
| Line 5: | Line 5: | ||
* To define new steps that can you used when writing tests, see [[Writing new acceptance test step definitions]] | * To define new steps that can you used when writing tests, see [[Writing new acceptance test step definitions]] | ||
Because Behat tests work through the Moodle user interface, | Because Behat tests work through the Moodle user interface, they are a bit slow. Therefore, you should probably also use [[PHPUnit]] to test the detailed edge cases in your code. | ||
[[Category:Behat]] | [[Category:Behat]] | ||
Revision as of 01:56, 28 May 2019
Moodle uses a framework called Behat to automatically test the user-interface. Tests can be written for each plugin, and for Moodle core.
- To run the existing tests, read Running acceptance test. You really need to do this first.
- To write new tests, read Writing acceptance tests.
- To define new steps that can you used when writing tests, see Writing new acceptance test step definitions
Because Behat tests work through the Moodle user interface, they are a bit slow. Therefore, you should probably also use PHPUnit to test the detailed edge cases in your code.
