|
|
| (2 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| <H1 CLASS="western" STYLE="page-break-before: always">Implementation</H1>
| | |
| <P>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.</P>
| |
| <H2 CLASS="western">Phase 1: Infrastructure: Currently in Progress</H2>
| |
| <P>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.</P>
| |
| <P>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.</P>
| |
| <P>Infrastructure includes the development of a functional test automation framework at Moodle.</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>
| |
