From Fedora Project Wiki
< Features
(→Scope) |
|||
Line 29: | Line 29: | ||
== Scope == | == Scope == | ||
<!-- 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 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? --> | ||
== Test Plan == | == Test Plan == | ||
<!-- 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. | ||
A good Test Plan should answer these four questions: | |||
0. What special hardware / data / etc. is needed (if any)? | |||
1. How do you prepare your system to test this feature? What packages | |||
need to be installed, config files edited, etc.? | |||
2. What specific actions do you perform to check that the feature is | |||
working like it's supposed to? | |||
3. What are the expected results of those actions? | |||
--> | |||
== User Experience == | == User Experience == |