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


Ignore:
Timestamp:
11/14/14 10:15:01 (9 years ago)
Author:
tupty@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • OpenFlow/Slicer/TestPlan

    v17 v18  
    22
    33= GENI OpenFlow Slicer Test Plan =
    4 This test plan is for validating software that implements the [wiki:OpenFlow/Slicer/Requirements GENI Slicer Requirements].  The focus of this test plan is testing that the requirements are satisfied in an environment that is close to how the slicer will be used in production.  In other words, it is not focused on unit testing.  This is also not a full blown integration test.  A lot of the data plane traffic is simple ICMP ping traffic.  Also, any of the limitations of the substrate will not be held against the slicer as part of this test plan.
     4This test plan is for validating software that implements the [wiki:OpenFlow/Slicer/Requirements GENI Slicer Requirements].  The focus of this test plan is testing that the requirements are satisfied in an environment that is close to how the slicer will be used in practice once it is deployed in GENI.  In other words, it is not focused on functional unit testing.  Tests may exercise specific functions defined in the requirements, but the tests themselves should focus on validating that the tests pass within the context of how they will be used in GENI.  With all of that said, this is also not a full blown integration test.  A lot of the data plane traffic is simple ICMP ping traffic, which is not necessarily indicative of all kinds of traffic one might see in GENI.  Also, any of the limitations of the substrate will not be held against the slicer as part of this test plan.
    55
    66== Expected test outcome ==
    … …  
    99 * 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.
    1010 * 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.
     11 * All test steps verifying something that doesn't map back directly to a requirement will be satisfied with special exceptions made only when they seem reasonable.
    1112
    1213== Tracking progress during testing ==