Testing strategy: Difference between revisions
Tim Barker (talk | contribs) No edit summary |
Tim Barker (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{Work in progress}} | {{Work in progress}} | ||
=Introduction= | |||
==Purpose== | |||
The purpose of this document is to define a high level QA strategy | |||
at Moodle and communicate that process to the relevant stakeholders. | at Moodle and communicate that process to the relevant stakeholders. | ||
This document is loosely based upon the IEEE829 standard for software | This document is loosely based upon the IEEE829 standard for software | ||
| Line 8: | Line 8: | ||
make the document more lightweight, suitable for use in an agile | make the document more lightweight, suitable for use in an agile | ||
process and relevant to the organization. | process and relevant to the organization. | ||
This document is test centric, only explaining the development | |||
process from a testing point of view. The scope of this document does | process from a testing point of view. The scope of this document does | ||
not cover the details of the entire development process at Moodle but | not cover the details of the entire development process at Moodle but | ||
how testing is applied to it. This document also discusses potential | how testing is applied to it. This document also discusses potential | ||
benefits to the organization of the processes discussed. | benefits to the organization of the processes discussed. | ||
Currently the processes that are documented here are under development. Progress can be viewed via the [https://docs.moodle.org/dev/Testing_strategy/Implementation_Plan Implementation Plan] | |||
==Scope== | |||
<P STYLE="margin-bottom: 0cm">This document encompasses all testing | <P STYLE="margin-bottom: 0cm">This document encompasses all testing | ||
activities at Moodle and how they will be performed. This includes:</P> | activities at Moodle and how they will be performed. This includes:</P> | ||
| Line 24: | Line 24: | ||
<LI><P STYLE="margin-bottom: 0cm">[https://docs.moodle.org/dev/Testing_strategy/Hardware_Requirements Hardware requirements]</P> | <LI><P STYLE="margin-bottom: 0cm">[https://docs.moodle.org/dev/Testing_strategy/Hardware_Requirements Hardware requirements]</P> | ||
<LI><P STYLE="margin-bottom: 0cm">[https://docs.moodle.org/dev/Testing_strategy/Testing_Tools_and_Their_Use Testing Tools and Their Use]</P> | <LI><P STYLE="margin-bottom: 0cm">[https://docs.moodle.org/dev/Testing_strategy/Testing_Tools_and_Their_Use Testing Tools and Their Use]</P> | ||
<LI><P STYLE="margin-bottom: 0cm">[https://docs.moodle.org/dev/Testing_strategy/Test_Environments Test Environments]</P> | |||
<LI><P STYLE="margin-bottom: 0cm">[https://docs.moodle.org/dev/Testing_strategy/Implementation_Plan Implementation Plan]</P> | <LI><P STYLE="margin-bottom: 0cm">[https://docs.moodle.org/dev/Testing_strategy/Implementation_Plan Implementation Plan]</P> | ||
<LI><P STYLE="margin-bottom: 0cm">[https://docs.moodle.org/dev/Testing_strategy/Training Training]</P> | <LI><P STYLE="margin-bottom: 0cm">[https://docs.moodle.org/dev/Testing_strategy/Training Training]</P> | ||
<LI><P STYLE="margin-bottom: 0cm">[https://docs.moodle.org/dev/Testing_strategy/Useful_Resources Useful Resources]</P> | <LI><P STYLE="margin-bottom: 0cm">[https://docs.moodle.org/dev/Testing_strategy/Useful_Resources Useful Resources]</P> | ||
</UL> | </UL> | ||
Revision as of 08:22, 29 August 2012
Note: This page is a work-in-progress. Feedback and suggested improvements are welcome. Please join the discussion on moodle.org or use the page comments.
Introduction
Purpose
The purpose of this document is to define a high level QA strategy at Moodle and communicate that process to the relevant stakeholders. This document is loosely based upon the IEEE829 standard for software testing documentation; adaptations have been made to this standard to make the document more lightweight, suitable for use in an agile process and relevant to the organization.
This document is test centric, only explaining the development process from a testing point of view. The scope of this document does not cover the details of the entire development process at Moodle but how testing is applied to it. This document also discusses potential benefits to the organization of the processes discussed. Currently the processes that are documented here are under development. Progress can be viewed via the Implementation Plan
Scope
This document encompasses all testing activities at Moodle and how they will be performed. This includes:
