From Fedora Project Wiki
(Owner)
(Test Plan: Rename to How To Test, make it clearer that these instructions are for others)
Line 35: Line 35:
 
<!-- What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 
<!-- What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
  
== Test Plan ==
+
== How To Test ==
 
<!-- This does not need to be a full-fledged document.  Describe the dimensions of tests that this feature is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The QA team will turn this information into a more complete test plan.  The more specific you can be, the better the final test plan will be.  
 
<!-- This does not need to be a full-fledged document.  Describe the dimensions of tests that this feature is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The QA team will turn this information into a more complete test plan.  The more specific you can be, the better the final test plan will be.  
 +
 +
Remember that you are writing this test plan for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.
  
 
A good Test Plan should answer these four questions:
 
A good Test Plan should answer these four questions:
  
 
0. What special hardware / data / etc. is needed (if any)?
 
0. What special hardware / data / etc. is needed (if any)?
1. How do you prepare your system to test this feature? What packages
+
1. How do I prepare my system to test this feature? What packages
 
need to be installed, config files edited, etc.?
 
need to be installed, config files edited, etc.?
2. What specific actions do you perform to check that the feature is
+
2. What specific actions do I perform to check that the feature is
 
working like it's supposed to?
 
working like it's supposed to?
 
3. What are the expected results of those actions?
 
3. What are the expected results of those actions?

Revision as of 18:33, 12 November 2008

Important.png
Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR FEATURE.


Feature Name

Summary

Owner

  • email: <your email address so we can contact you>

Current status

  • Targeted release: Fedora 32
  • Last updated: (DATE)
  • Percentage of completion: XX%


Detailed Description

Benefit to Fedora

Scope

How To Test

User Experience

Dependencies

Contingency Plan

Documentation

Release Notes

Comments and Discussion