Testing: Difference between revisions
David Mudrak (talk | contribs) m (→Integration functional testing: Fix the docs, we always test patches even if they include unit tests and behat tests.) |
Dev Docs Bot (talk | contribs) m (Protected "Testing": Developer Docs Migration ([Edit=Allow only administrators] (indefinite))) |
||
| (3 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{Template:Migrated|newDocId=/general/development/process/testing}} | |||
This page is the top level page regarding all testing activities around the Moodle project. Testing is essential to make sure that developed code does what it is meant to do, without causing new problems. | This page is the top level page regarding all testing activities around the Moodle project. Testing is essential to make sure that developed code does what it is meant to do, without causing new problems. | ||
| Line 17: | Line 19: | ||
* [[Testing of integrated issues]] | * [[Testing of integrated issues]] | ||
===QA | ===QA testing=== | ||
Volunteer testers from the Moodle community systematically try each feature in Moodle and test that it works in the current version of the Moodle code. These tests are repeated in series of cycles, usually 4 weeks before a major release, once all major features have landed. | |||
* [[QA testing]] | * [[QA testing]] | ||
For major theme changes, additional manual tests may be run. | |||
==Automated testing== | ==Automated testing== | ||
| Line 44: | Line 48: | ||
A failure here notifies the integrators that the build has failed. | A failure here notifies the integrators that the build has failed. | ||
=== | ===Regression testing=== | ||
Every day an automated build in a test server runs a large number of tests | Every day, an automated build in a test server runs a large number of tests concerning key functions of Moodle, to make sure that everything still works and that some new fix in Moodle hasn't caused problems elsewhere. | ||
These tests must pass completely before a release can be made. | These tests must pass completely before a new release can be made. | ||
* [[Acceptance testing]] using the Behat framework | * [[Acceptance testing]] using the Behat framework | ||
| Line 54: | Line 58: | ||
Moodle uses a sponsored version of [https://www.browserstack.com BrowserStack] for testing on multiple browsers. | Moodle uses a sponsored version of [https://www.browserstack.com BrowserStack] for testing on multiple browsers. | ||
[[Category:Quality Assurance]] | [[Category:Quality Assurance]] | ||
Latest revision as of 07:27, 6 May 2022
| 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! |
This page is the top level page regarding all testing activities around the Moodle project. Testing is essential to make sure that developed code does what it is meant to do, without causing new problems.
Manual testing
Code testing
Code is tested as part of reviewing at some key parts of the Moodle development process.
- Development - the developer of some code should test their own work on a wide variety of environments for correctness and performance
- Peer review - developers often test each others work early in the development process
- Integration reviews - Our integration team tests code weekly while they are evaluating suitability for integration into Moodle.
Integration functional testing
On Wednesday (all timezones) our Moodle HQ developers spend the day to manually test the functionality of all the issues that have been integrated that week. Developers submitting patches should always cover the patch with unit tests and/or Behat behavioural tests. Still, all issues are tested by a human and it is usually worth it.
QA testing
Volunteer testers from the Moodle community systematically try each feature in Moodle and test that it works in the current version of the Moodle code. These tests are repeated in series of cycles, usually 4 weeks before a major release, once all major features have landed.
For major theme changes, additional manual tests may be run.
Automated testing
Unit tests
Moodle 2.3 and later fully supports PHPUnit tests as part of the code. These are automated tests of very low-level code functionality that a developer should write as part of any new code.
Continuous integration testing
As soon as code is added to the integration repository, our continuous integration server tests the new code for:
- Coding guidelines
- PHPUnit tests
- SimpleTest unit tests on older versions of Moodle
- Detect unresolved merge conflicts
- Compare databases upgraded from previous versions
- Check the version.php is correct
A failure here notifies the integrators that the build has failed.
Regression testing
Every day, an automated build in a test server runs a large number of tests concerning key functions of Moodle, to make sure that everything still works and that some new fix in Moodle hasn't caused problems elsewhere.
These tests must pass completely before a new release can be made.
- Acceptance testing using the Behat framework
- Performance testing using JMeter.
Moodle uses a sponsored version of BrowserStack for testing on multiple browsers.
