From Fedora Project Wiki

m (Update includes)
m (Use the built-in template)
 
Line 1: Line 1:
= Revision history =
<noinclude>
{| border="1"
For guidance on using this template, consult [[Template:QA/Test_Plan]]
|- style="color: white; background-color: #3074c2; font-weight: bold"
</noinclude>
| Date || Revision || Comment
|-
| @DATE@ || 0.1 || Initial version
|}
 
= Introduction =
* Brief description of this document
 
* The goals of this plan are to:
* ''Organize'' the test effort
* ''Communicate'' the strategy, scope and priorities of the planned tests to all relevant stake-holders for their input and approval
* Serve as a base for the test planning for future Fedora releases
 
= Test Strategy =
 
* Describe how the testing will be organized and executed.  Is there any special order or sequence to perform actions.
 
= Test Priority =
* Often used to outline tiers of tests arranged from most important (tier#1) to infrequently used tests (tier#3).
 
= Scope =
* What will and won't be tested.
 
= Test Pass/Fail Criteria =
* When do you consider testing completed or stopped?  How do you know when to stop?
 
= Test Deliverables =
* This test plan
* A test summary document for each major milestone
* A list of defects filed
* Any test scripts used for automation or verification
 
= Test Cases (Functional) =
* List of test cases by feature
 
= Test Cases (Non-Functional) =
 
{| border="1"
|- |<|2 rowstyle="color: white; background-color: #3074c2; font-weight: bold"> Test Case ||<-5 :> Environment
|- style="color: white; background-color: #3074c2; font-weight: bold"
| environment 1 || environment 2 || environment 3
|-
|  ||  ||
|- style="background-color: #EEEFF1;"
|  ||  ||
|}
 
== Compatibility testing ==
== Compliance testing ==
== Documentation testing ==
== Endurance testing ==
== Load testing ==
== Localization testing and Internationalization testing ==
== Performance testing ==
== Resilience testing ==
== Security testing ==
== Scalability testing ==
== Stress testing ==
== Usability testing ==
== Volume testing ==
= Test Environment/Configs =
* Describe the environment tests will be executed in
 
= Responsibilities =
* who's doing what
 
= Schedule/Milestones =
* when are they doing it
 
= Risks and Contingencies =
* what might go wrong and how we'll handle it


= Approvals =
{{Template:QA/Test_Plan}}
* Name and date of authors and interested parties who have reviewed this plan
 
= References =
* reference any documentation
 
= Appendices =
* extra info related to this test plan
 
<noinclude>
[[Category:Test_Plans]]
[[Category:QA Templates]]
</noinclude>

Latest revision as of 17:58, 28 April 2009

For guidance on using this template, consult Template:QA/Test_Plan



Revision history

Detail key dates with respect to this document. Including it's creation date and significant updates since then.

Introduction

Brief description of this document.

  • The goals of this plan are to:
  • Organize the test effort
  • Communicate the strategy, scope and priorities of the planned tests to all relevant stake-holders for their input and approval
  • Serve as a base for the test planning for future Fedora releases


Test Strategy

Describe how the testing will be organized and executed. Is there any special order or sequence to perform actions.

Test Priority

Often used to outline tiers of tests arranged from most important (tier#1) to infrequently used tests (tier#3).

Scope

What will and won't be tested.

Test Pass/Fail Criteria

When do you consider testing completed or stopped? How do you know when to stop?

Test Deliverables

Describe what the consumables will be from testing. Examples include:

  • This test plan
  • A test summary document for each major milestone
  • A list of defects filed
  • Any test scripts used for automation or verification

Test Cases

Using the level of detail required by this test plan, outline test areas and test cases to be exercised.

Test Environment

Describe the environment tests will be executed in

Responsibilities

High-level detail of who is accountable for different phases of testing.

Schedule

Outline the scheduled milestones.

Risks

Given the current scope and test priority, what are some potential risks. Are there any other contingencies should problems arrise? How will issues be dealt with when they surface.

Reviewers

References