2.4 Test Plan

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 using the CI Server.

Feature Comparison Testing

Feature Comparison testing of MDL-21538 and MDL-31830 will take place at regular intervals during implementation. Theses tracker issues involve completely replacing existing Moodle plugins/features. The purpose of this testing is to ensure that no features are lost during implementation i.e. when implemented the features/plugins being implemented retain all of the functionality of what they are replacing without prior agreement.

The testing will provide a critique of the changes and the method used to test will be in the form of session based testing.

Usability Testing

MOBILE-153, MDL-34080 and MDL-31830 require usability testing. The method to be used for this is persona based testing. This involves creating a number of personas of potential users of these features and then running exploratory tests role playing as these users. e.g. a study at home single mum, super geek who know everything about everything and highly critical of Moodle. Persona testing will take place regularly during the implementation of the tracker items.