Testing Roadmap

Note: This page is a work-in-progress. Feedback and suggested improvements are welcome. Please join the discussion on moodle.org or use the page comments.

Introduction

This page documents the current work being performed as a process of continuous improvement and testing planned at Moodle. Testing fulfils multiple roles within Moodle, from actually assisting Moodle developers to create a high quality product and mitigating risks during projects to providing user confidence in the product through reporting, feedback and visibility.

Areas of the Testing Process Improvement Currently Under Development

Due to dependencies such as the QA test cycle, testing is aligned with Moodle's 6 monthly times release cycle. Version 2.4 of Moodle is scheduled for release in December 2012.

Test Environments

Implement Oracle and MSSQL test databases for test automation. Issue to be added

Test Automation

• MDLTEST-240 Create the nightly build machine. A Jenkins server is required to run an automated nightly build of Moodle.
• MDLTEST-246 Add performance testing comparison tool and performance tests to the nightly build.
• MDLTEST-274 Implement Behat Behavioural Driven Development (BDD) framework with Selenium in PHP. We already have a suite of tests running in Selenium against core modules in Moodle on a nightly basis. This project adds usability to the tool allowing the community to implement automated tests easily using a ubiquitous, domain specific language.
• MDLTEST-256 This implements our selenium tests on the nightly build machine against a Selenium 2 Grid.
• MDLTEST-284 Implement Unit tests on the nightly build machine against Postgres database. The plan is to increase the coverage of tests against the different supported database drivers. We already run continuous integration against the MySQL database driver at every checkin.