Testing strategy: Difference between revisions
Tim Barker (talk | contribs) No edit summary |
No edit summary |
||
| (8 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{Work in progress}} | {{Work in progress}} | ||
=Introduction= | =Introduction= | ||
==Purpose== | ==Purpose== | ||
The purpose of this document is to define a high level QA strategy | 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 test centric, only explaining the development | This document is test centric, only explaining the development | ||
| Line 14: | Line 13: | ||
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 [ | Currently the processes that are documented here are under development. Progress can be viewed via the [[Testing Roadmap]] | ||
==Scope== | ==Scope== | ||
This document encompasses all testing activities at Moodle and how they will be performed. This includes: | This document encompasses all testing activities at Moodle and how they will be performed. This includes: | ||
[ | * [[Testing strategy/Testing Methodology At Moodle|Testing Methodology at Moodle]] | ||
[ | * [[Testing strategy/The Moodle Testing Process|The Moodle Testing Process]] | ||
[ | * [[Testing strategy/Hardware Requirements|Hardware requirements]] | ||
[ | * [[Testing strategy/Testing Tools and Their Use|Testing Tools and Their Use]] | ||
[ | * [[Testing strategy/Test Automation Process|Test Automation Process]] | ||
[ | * [[Testing strategy/Test Environments|Test Environments]] | ||
[ | * [[Testing strategy/Useful Resources|Useful Resources]] | ||
[ | |||
[ | |||
Latest revision as of 16:56, 25 September 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 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 Testing Roadmap
Scope
This document encompasses all testing activities at Moodle and how they will be performed. This includes:
