Acceptance testing for the Moodle App
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 describes the internals of Behat and the integration with Moodle.
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.
Moodle App Development process
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.
PHPUnit by Sebastian Bergmann is an advanced unit testing framework for PHP. It is installed as Composer dependency and is not part of Moodle installation. To run PHPUnit tests, you have to manually install it on your development computer or test server.
All the information related to the Qualify Assurance tests during the Moodle development.
Running acceptance tests
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:
Testing of integrated issues
All the information related to the integration review process during the Moodle development.
A summary of the most common actions in Moodle tracker.
Unit testing for the Moodle App
Working combinations of OS+Browser+selenium
As OS, Browsers and Selenium keeps updating, some combination might fail on different Moodle releases.
Writing acceptance tests
This documentation gives some hints on writing behat tests for Moodle core, and for plugins. The focus of the documentation is on behat tests for plugins. Behat Features and Scenarios are written in a natural language, and should