Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

Testing strategy/Implementation Plan: Difference between revisions

From MoodleDocs
(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 ...")
 
(Blanked the page)
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
<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 the initial phase of
implementing test automation. The impact of this hump can be
minimised by good planning, good coaching and a strong managerial
support for the new processes. As time progresses, particularly as
infrastructure becomes implemented, the test cases in the automated
suite are completed and the introduced practices become second
nature; the hump disappears.</P>
<H2 CLASS="western">Agile Implementation 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>
<H2 CLASS="western">Phase 1: Infrastructure and the
Integration Process</H2>
<P>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.</P>
<P>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.</P>
<P>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.</P>

Latest revision as of 06:14, 14 September 2012