| | 1 | [[Page Outline]] |
| | 2 | |
| | 3 | = GENI OpenFlow Slicer Test Plan = |
| | 4 | |
| | 5 | Intro describing: |
| | 6 | - goals of testing |
| | 7 | |
| | 8 | Provide a link to the [wiki:OpenFlow/Slicer/Requirements Slicer Requirements] that the plan is based on. |
| | 9 | |
| | 10 | Describe the expected outcome: |
| | 11 | - status pages |
| | 12 | - test reports |
| | 13 | |
| | 14 | == Assumptions and Dependencies == |
| | 15 | |
| | 16 | Describe any assumptions, for example: |
| | 17 | - slicer software must interact with OF v1.0 |
| | 18 | - slicer software should interact with OF v1.3 |
| | 19 | - Slicer must interact with specific OF switches: x, y, z... |
| | 20 | - Slicer must interact with service abstraction layer: x, y, z.... |
| | 21 | - Documentation must is available describing configuration and usage. |
| | 22 | |
| | 23 | = Slicer Test Cases = |
| | 24 | |
| | 25 | == Functional Test Cases == |
| | 26 | |
| | 27 | == Operational Test Cases == |
| | 28 | |
| | 29 | == Software Test Cases == |
| | 30 | |
| | 31 | == Supplementary Test Cases == |
| | 32 | Define test cases that capture the [wiki:OpenFlow/Slicer/Requirements#Wishlist Wishlist Functionality] that may be delivered. |
| | 33 | |
| | 34 | |
| | 35 | = Test Methodology = |
| | 36 | Describe how testing is to be conducted, how issues are to be tracked, how status will be made available. |
| | 37 | Describe how test cases are named. |
| | 38 | |
| | 39 | = Glossary = |
| | 40 | (if needed) |
| | 41 | |
