Changes between Version 20 and Version 21 of OpenFlow/Slicer/TestPlan

Timestamp:

11/14/14 10:49:36 (9 years ago)

Author:

tupty@bbn.com

Comment:

--

OpenFlow/Slicer/TestPlan

@@ -65 +65 @@
  a. Start a packet capture on the slicer facing both the switch and the controller.
  b. Push a flow_stats request from the controller.
- c. Stop the packet capture, and check for the following: the flow_stats reply only went to the controller that requested it. ''(004-g)''
- d. Run some OFTest checks to make sure that ''(004-f)'' and ''(009)'' are met.
+ c. Stop the packet capture, and check that the flow_stats reply only went to the controller that requested it. ''(004-g)''
+ d. Run some OFTest checks within the 'samevlan' slice to make sure that ''(004-f)'' and ''(009)'' are met.
+  i. Test OFPT_GET_CONFIG_REQUEST and make sure an OFPT_GET_CONFIG_REPLY comes back.  Use the OFTest GetConfigReply test.
+  ii. Run a test that verifies OFPT_FLOW_REMOVED messages are properly returned to the controller.  Use the OFTest FlowExpire test.
+  iii. Run a test that verifies that OFPT_BARRIER_REQUESTS send back an OFPT_BARRIER_REPLY.  Use the OFTest BarrierRequestReply test.
  e. Test a few synchronous messages using OFTest to make sure ''(006)'' is met.
- f. Test that ''(007-a)'', ''(007-b)'', and ''(007-c)'' all generate error messages.
+ f. Test that ''(007-a)'' and ''(007-b)'' both generate error messages if ''(007-c)'' is not met.
+  i. Test that sending an OFPT_PORT_MOD from the controller either generates an error, or at the very least doesn't go to the substrate.  Use the OFTest PortModPacketIn test.
+  ii. Test that sending an OFPT_SET_CONFIG message either generates an error, or at the very least doesn't go to the substrate.  Use the OFTest SetConfigRequest test.
 
 === Step 6: Test for stacked slicer support ===