From 91997ced013c99811b299f1d749337e98f0adac5 Mon Sep 17 00:00:00 2001 From: Victor Woeltjen Date: Tue, 24 Nov 2015 17:08:59 -0800 Subject: [PATCH] [Documentation] Define test levels --- docs/src/process/testing/plan.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/docs/src/process/testing/plan.md b/docs/src/process/testing/plan.md index e69de29bb2..8bedd01172 100644 --- a/docs/src/process/testing/plan.md +++ b/docs/src/process/testing/plan.md @@ -0,0 +1,19 @@ +# Test Plan + +## Test Levels + +Testing occurs regularly during development, with varying levels of +completeness. + +In order of decreasing frequency and increasing completeness, these +are: + +1. __Pre-merge testing__: Performed before changes are integrated + into the software. +2. __Partial acceptance testing__: A subset of acceptance testing + performed at regular intervals. +3. __Acceptance testing__: Performed before a new release is considered + stable. + +Each level of testing is inclusive of the levels which proceed it. +