Testing strategy/Implementation Plan: Difference between revisions
Tim Barker (talk | contribs) (Created page with "<H1 CLASS="western" STYLE="page-break-before: always">Implementation</H1> <P>Agile testing guru and automation expert Brian Marick coined the term “Hump of Pain” to describe ...") |
Tim Barker (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
<H1 CLASS="western" STYLE="page-break-before: always">Implementation</H1> | <H1 CLASS="western" STYLE="page-break-before: always">Implementation</H1> | ||
<P> | <P>It is a well known fact that 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 | minimised by good planning, good coaching and a strong managerial | ||
support for the new processes | support for the new processes.</P> | ||
<H2 CLASS="western">Phase 1: Infrastructure and the | <H2 CLASS="western">Phase 1: Infrastructure and the | ||
Integration Process</H2> | Integration Process</H2> | ||
| Line 30: | Line 22: | ||
automation process, particularly test cases, can be developed | automation process, particularly test cases, can be developed | ||
incrementally.</P> | incrementally.</P> | ||
<H2 CLASS="western">Agile Development of Testing | |||
Practices</H2> | |||
<P>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.</P> | |||
Revision as of 06:28, 13 March 2012
Implementation
It is a well known fact that 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 and the Integration Process
The infrastructure to maintain automated testing effort 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'. The processes described above will will be initially implemented at integration. 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.
The setup of test environments will initially start with a restricted number of high risk test environments so that the automation process, particularly test cases, can be developed incrementally.
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.
