Note:

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

Testing strategy/Test Environments: Difference between revisions

From MoodleDocs
No edit summary
No edit summary
Line 82: Line 82:
<P>A master hub VM is required for Jenkins and the hub for the Selenium
<P>A master hub VM is required for Jenkins and the hub for the Selenium
grid.</P>
grid.</P>
<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>

Revision as of 03:02, 13 March 2012

Test Environments

Test environments for automation will be hosted on the VM server. These will include a CI server (the build machine), database servers, web servers and client PCs.

Requirements Gathering

As a task while provisioning the VM Server, two surveys have been run to determine popular Test Platforms. Survey 1 gathered metrics from the Moodle Community and Survey 2 gathered metrics from Moodle Partners. Limiting factors of these surveys are that both samples are relatively small. The results of the surveys are as follows:

Survey 1 The Moodle Community:

Fig. 4 Separate Database and Web Server Yes/No:

Fig. 2 user split system.png

Fig. 5 Operating System of Separate Web Server:

fig.3 user os separatewebserver.gif

Fig. 6 Operating System of Separate Database Server:

fig.6 user OS SeparateDB.gif

Fig. 7 What Databases are Used on a Split System:

Fig7 user dbs used split.png

Fig. 8 What Databases are Used on an all in one Database Server and Webserver:

fig8 user database combined.png

Fig. 9 What Web Server is Used on a Split System:

user webserver split.png

Fig. 10 What Web Server is Used on an all in one Database Server and Webserver:

user webserver combined.png

As Debian and Ubuntu are similar and Red Hat and Centos are similar that,based upon our sample data, our three main operating used by the Moodle community Debian/Ubuntu, Red Hat/Centos and MS Server 2008 with a weighting of almost 75% towards the two Linux operating systems.

Of the five supported databases, the majority of community users prefer MySQL with PostgreSQL and MSSQL a fairly equal but distant second and third.

The Majority of community users also use Apache with IIS a very distant second.

7.1.1Survey 2 The Moodle Partners:

Fig. 11 Separate Database and Web Server Yes/No:

partner split combine.png

Fig. 12 Partner OS Database Server (combining answers for fig 11):

partner OS DB.gif

Fig. 13 Partner OS Web Server (combining answers for fig 8):

partner OS Web.gif

Fig. 14 What Databases are Used on a Split System:

partner db split.png

Fig. 15 What Databases are Used on a Combined System:

partner db combine.png

Fig. 16 What Web Servers are used on a Split System:

partner webserver split.png

Fig. 17 What Web Servers are used on a Combined System:

partner webserver combined.png

This suggests that the majority of partners use Debian/Ubuntu or Centos/Rad Hat Linux, Apache and either a MySQL or PostgreSQL database.

VM Requirements

In true agile fashion and to promote flexibility, VM's for test environments will be modular i.e. they will be separate database servers and web servers. This will allow the mixing and matching of databases and their host OS to the web servers and their host OS as requirements change. At any time, any Web Server can connect to any Database Server. It should also reduce potential numbers of running VMs required for a particular platform.

A master hub VM is required for Jenkins and the hub for the Selenium grid.

Retrieved from "https://docs.moodle.org/dev/index.php?title=Testing_strategy/Test_Environments&oldid=32776"
Powered by MediaWiki