In order to run tests that carry out automated functionality testing for the Moodle App, you can write Acceptance tests. This can be useful if you want to test plugins that are compatible with the app, or you're contributing to the app core. Behat tests for the app work the same way as tests for Moodle core, but they are not run as part of a normal Behat execution and there are some differences that we'll go through in this page.
This page complements Behat providing info about how to run the acceptance tests suite in different browsers.
A summary of the various development processes used in Moodle development.
The development of new features and improvements in the Moodle App is organised in the following six phases:
This page gives an overview of the process of developing Moodle and outlines some of the basic concepts to better understand this Developer documentation.
All the information related to the Qualify Assurance tests during the Moodle development.
Moodle uses Behat, a php framework for automated functional testing, as part of a suite of testing tools.
All the information related to testing during the Moodle development.
The following people have helped with Quality Assurance (QA) testing:
All the information related to the integration review process during the Moodle development.
A summary of the most common actions in Moodle tracker.
Unit tests are written in JavaScript using Jest. If you want to create a new one, Jest is already configured and you only need to create a file ending with .test.ts within the project. If you're going to do so, remember to follow the file location conventions.