< User:Roshi | QA/Cloud Docs
For guidance on using this template, consult Template:QA/Test_Plan
Revision history
Created by Roshi on 22 April 2014
Introduction
With the advent of different Fedora Products for Fedora 21 there is a need for a specific test plan for each product. Historically, Release Validation and all Testing of Fedora releases was handled by QA - but now testing and release validation will be largely handled by the specific Working Group. This test plan is aimed at documenting the testing needs of the Cloud product.
Test Strategy
Testing and Release Validation for the Cloud product will follow the same pattern Fedora 20 followed. There will be three milestones - each milestone will have a related set of Release Criteria and Validation Matrix for the release.
Milestones
- Alpha
- Beta
- Final
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