From Fedora Project Wiki
(fix markup and add category) |
m (Clean up for mediawiki) |
||
| Line 1: | Line 1: | ||
= Revision history = | |||
{| border="1" | {| border="1" | ||
|- style="color: white; background-color: #3074c2; font-weight: bold" | |- style="color: white; background-color: #3074c2; font-weight: bold" | ||
| Line 9: | Line 7: | ||
|} | |} | ||
= Introduction = | |||
* Brief description of this document | * Brief description of this document | ||
| Line 17: | Line 15: | ||
* Serve as a base for the test planning for future Fedora releases | * 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. | * 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). | * 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. | * 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? | * When do you consider testing completed or stopped? How do you know when to stop? | ||
= Test Deliverables = | |||
* This test plan | * This test plan | ||
* A test summary document for each major milestone | * A test summary document for each major milestone | ||
| Line 36: | Line 34: | ||
* Any test scripts used for automation or verification | * Any test scripts used for automation or verification | ||
= Test Cases (Functional) = | |||
* List of test cases by feature | * List of test cases by feature | ||
= Test Cases (Non-Functional) = | |||
{| border="1" | {| border="1" | ||
| Line 51: | Line 49: | ||
|} | |} | ||
== 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 | * Describe the environment tests will be executed in | ||
= Responsibilities = | |||
* who's doing what | * who's doing what | ||
= Schedule/Milestones = | |||
* when are they doing it | * when are they doing it | ||
= Risks and Contingencies = | |||
* what might go wrong and how we'll handle it | * what might go wrong and how we'll handle it | ||
= Approvals = | |||
* Name and date of authors and interested parties who have reviewed this plan | * Name and date of authors and interested parties who have reviewed this plan | ||
= References = | |||
* reference any documentation | * reference any documentation | ||
= Appendices = | |||
* extra info related to this test plan | * extra info related to this test plan | ||
[[Category:QA Templates]] | [[Category:QA Templates]] | ||
Revision as of 15:42, 28 April 2009
Revision history
| 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)
| environment 1 | environment 2 | environment 3 |
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
- 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