Testing strategy/Implementation Plan

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.

Implementation

Implementing test automation can initially be time-consuming and require a lot of effort. Evidence also exists to suggest that this effort reduces over time as the new processes become common practice. The impact of the initial implementation period can be minimised by good planning, good coaching and a strong managerial support for the new processes.

Agile Development of Testing Practices

Development of testing tasks and processes are made in an incremental manner based up scrum methodology. A series of 2 weekly sprints are used to time-box test planning and implementation tasks. Details of the dev stories and timeboxes relating to this are stored in tracker under the Moodle Testing project

Phase 1: Infrastructure: Currently in Progress

The infrastructure to maintain automated testing effort and new/revised processes must be implemented. This process will start with the installation of cloud based hardware at Moodle HQ and the setup of VM's to support the required test environments.

The integration process affects quality for the whole organisation as all code must go through the integration process to become 'live'. Any changes to the existing processes will take place side-by-side with existing processes to manage risk. i.e. existing processes impacted by changes will be maintained in their current state until implementation of changes becomes stable.

Infrastructure includes the development of a functional test automation framework at Moodle.