Testing strategy/Implementation Plan: Difference between revisions
Tim Barker (talk | contribs) No edit summary |
Tim Barker (talk | contribs) No edit summary |
||
| Line 5: | Line 5: | ||
minimised by good planning, good coaching and a strong managerial | minimised by good planning, good coaching and a strong managerial | ||
support for the new processes.</P> | support for the new processes.</P> | ||
<H2 CLASS="western">Phase 1: Infrastructure | <H2 CLASS="western">Phase 1: Infrastructure: Currently in Progress</H2> | ||
<P>The infrastructure to maintain automated testing | <P>The infrastructure to maintain automated testing | ||
effort and new/revised processes must be implemented. This process will start with the | effort and new/revised processes must be implemented. This process will start with the | ||
| Line 13: | Line 12: | ||
<P>The integration process affects quality for the whole | <P>The integration process affects quality for the whole | ||
organisation as all code must go through the integration process to | organisation as all code must go through the integration process to | ||
become 'live' | become 'live'. Any changes to the existing processes | ||
will take place side-by-side with existing processes to manage risk. | will take place side-by-side with existing processes to manage risk. | ||
i.e. existing processes impacted by changes will be maintained in | i.e. existing processes impacted by changes will be maintained in | ||
their current state until implementation of changes becomes stable.</P> | their current state until implementation of changes becomes stable.</P> | ||
<P>Infrastructure includes the development of a functional test automation framework at Moodle.</P> | |||
<H2 CLASS="western">Agile Development of Testing | <H2 CLASS="western">Agile Development of Testing | ||
Practices</H2> | Practices</H2> | ||
Revision as of 07:01, 13 March 2012
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.
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.
Agile Development of Testing Practices
Modifications to the process should be made in an incremental manner based up scrum methodology. A series of 2 weekly sprints will be used to time-box test planning and implementation tasks.
