Changes between Version 16 and Version 17 of OpenFlow/Slicer/TestPlan


Ignore:
Timestamp:
11/12/14 15:02:30 (5 years ago)
Author:
tupty@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OpenFlow/Slicer/TestPlan

    v16 v17  
    77 * All test steps verifying a MUST requirement will be satisfied.
    88 * All test steps verifying a SHOULD requirement will be satisfied with special exceptions made only when they seem reasonable.
    9  * Any test steps that verify a MAY will have the results documented as features that operators can consider, but they will not count against the test plan.
    10  * Any test steps that verify an item from the wish list will have the results documented as features that operators can consider, but they will not count against the test plan.
     9 * Any test steps that verify a MAY will have the results documented as features that operators can consider, but failing these steps they will not count against the test plan.
     10 * Any test steps that verify an item from the wishlist will have the results documented as features that operators can consider, but failing these steps will not count against the test plan.
    1111
    1212== Tracking progress during testing ==
     
    114114
    115115== Wishlist Testing ==
    116 Define test cases that capture supplementary test cases for the [wiki:OpenFlow/Slicer/Requirements#Wishlist Wishlist Functionality] that may be delivered.
     116=== Step 1: Check documentation ===
     117 * Does the software come in a package?  If so, are there instructions for installing the software as a package?
     118 * Is untagged traffic supported in the slicer?  If so, does the documentation show how to reserve the untagged space on a port?
     119 * Is data plane isolation supported (unlikely until future OpenFlow versions are supported)?
     120 
     121=== Step 2: Set up the environment ===
     122 * Create a slice that uses two ports that connect two hosts in a slice.  Use untagged space on those ports if possible.
     123 * Run Floodlight static flow pusher, and push down a set of flows that will forward traffic between the two ports.
     124 * Make sure that you can exchange traffic between the hosts.
    117125
     126=== Step 3: Test that priority setting works ===
     127 * Install an identical set of flows with a higher priority and no actions.  When doing this, do not remove the old rules.
     128 * If possible, check the flow table and ensure that all four of the flows are in the flow table.
     129 * Ensure that traffic is not exchanged between the hosts.
     130 * Remove the higher-priority flows and make sure that traffic flows again.
    118131
    119132= Test Methodology =
     
    121134Describe how test cases are named.
    122135
    123 = Glossary = 
    124 (if needed)
    125