Systematic testing: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
| Line 17: | Line 17: | ||
# Draft [[Profiles|other people]] as needed in order to reach our desired confidence in our information. |
# Draft [[Profiles|other people]] as needed in order to reach our desired confidence in our information. |
||
# When feasible, contribute patches to the [[Tinderbox]]! |
# When feasible, contribute patches to the [[Tinderbox]]! |
||
== Bibliography == |
|||
Never having performed a large-scale systematic software test myself, I went looking for reference works and found: |
|||
* ISO/IEC 12207.0, |
|||
* IEEE STD 829-1998, |
|||
* MIL-STD-498, and |
|||
* ISO/IEC TR 19759:2005(E) (which has a nice bibliography) |
|||
[[Category:Testing]] |
[[Category:Testing]] |
||
Revision as of 01:37, 23 August 2008
For Developers
|
NOTE: The contents of this page are not set in stone, and are subject to change! This page is a draft in active flux ... |
|
Purpose
The purpose of this systematic testing effort is to achieve test coverage sufficient to make good ship/no-ship decisions about and to write accurate and timely release notes for the 8.2.0 release.
Battle Plan
- Convert one of our lists of features into a priority-tree of of "we-must", "we-hope", and "we-wish" test cases.
- Write the "must"-priority test cases and finalize the exact procedures for recording test results.
- When documented, the procedures for recording test results should be cited above.
- Modify our call for volunteer test labor to request help writing and executing our test cases.
- Draft other people as needed in order to reach our desired confidence in our information.
- When feasible, contribute patches to the Tinderbox!