Test Plan

Table of Contents

1.0 Purpose

This test plan is for [project] [release], [phases].

What milestones are important from a test perspective?
Basic definitions of criteria for those releases (high level).
List each release type and what our "ideal" quality level is for each. Be *very* specific.

This is the base line from which we make go/no-go decisions. If we're not at this quality level for a release, then either we document exceptions, or we don't release.

Release name (bl0, bl1, bl2, beta1, beta2, FCS)

definition
product installability
product completeness
test execution
product documentation
open defects
defect submission rate
source change rate
test coverage
purify'd
bug fix verification status
internal deployment

Overview of how we plan to attack the problem.
Map test groups to product functionality.
What's going to be automated?
What's going to be manual (code walkthroughs, doc checkout)?

Test activities by development
unit tests
performance analysis per module (i.e. Quantify if we've got it.)

Code reviews (both dev & qe)
Test development by QE
functional
perfomance
load/stress
security
I18N/L10N
network
standards
productization
recovery
interop

Release verifications (nightly builds, base levels, alpha, beta, FCS)
bug fix verification
platform combinatorics
what applies to each release type

5.0 Schedule

6.0 Resources

7.0 Risks/Concerns

Permission granted to use this document in whole or in part.