2.4 Test Plan: Difference between revisions
From MoodleDocs
Tim Barker (talk | contribs) |
Tim Barker (talk | contribs) |
||
Line 3: | Line 3: | ||
=Testing Applied to the Roadmap= | =Testing Applied to the Roadmap= | ||
Suitable testing methods will be applied to the tracker issues to | Suitable testing methods will be applied to the tracker issues in the roadmap for 2.4. | ||
==Unit Testing== | |||
PHP Unit tests will be provided where applicable(tba) and scheduled to run in via the [http://integrationci.test.local:8080 CI Server]. | |||
=Test Tools= | =Test Tools= |
Revision as of 05:51, 9 July 2012
General Aim
The general aim of testing applied to Moodle 2.4 is to provide early feedback and critique to developers about the system under test. This in turn will hopefully mitigate the bulk of issues earlier in the release cycle than Moodle QA. It may also increase flexibility and mitigate the risk posed by changing requirements; thus allowing requirements to change if necessary with the minimum of impact on the delivery of the project.
Testing Applied to the Roadmap
Suitable testing methods will be applied to the tracker issues in the roadmap for 2.4.
Unit Testing
PHP Unit tests will be provided where applicable(tba) and scheduled to run in via the CI Server.