pio 0.30.0 → 0.30.2

data/features/icmp/icmp_reply.feature

@@ -0,0 +1,93 @@
+Feature: Icmp::Reply
+  Scenario: create an ICMP reply
+    When I create a packet with:
+      """
+      Pio::Icmp::Reply.new(
+        destination_mac: '11:22:33:44:55:66',
+        source_mac: '66:55:44:33:22:11',
+        source_ip_address: '192.168.83.254',
+        destination_ip_address: '192.168.83.3',
+        icmp_identifier: 256,
+        icmp_sequence_number: 111,
+        echo_data: 'hello world'
+      )
+      """
+    Then the packet has the following fields and values:
+      | field                  |             value |
+      | destination_mac        | 11:22:33:44:55:66 |
+      | source_mac             | 66:55:44:33:22:11 |
+      | ether_type.to_hex      |             0x800 |
+      | ip_total_length        |                50 |
+      | ip_protocol            |                 1 |
+      | source_ip_address      |    192.168.83.254 |
+      | destination_ip_address |      192.168.83.3 |
+      | icmp_type              |                 0 |
+      | icmp_code              |                 0 |
+      | icmp_checksum          |             53442 |
+      | icmp_identifier        |               256 |
+      | icmp_sequence_number   |               111 |
+      | echo_data              |       hello world |
+
+  Scenario: convert an ICMP reply to Ruby code
+    When I eval the following Ruby code:
+      """ruby
+      Pio::Icmp::Reply.new(
+        destination_mac: '11:22:33:44:55:66',
+        source_mac: '66:55:44:33:22:11',
+        source_ip_address: '192.168.83.254',
+        destination_ip_address: '192.168.83.3',
+        icmp_identifier: 256,
+        icmp_sequence_number: 0
+      ).to_ruby
+      """
+    Then the result of eval should be:
+      """ruby
+      [
+        0x11, 0x22, 0x33, 0x44, 0x55, 0x66, # destination_mac
+        0x66, 0x55, 0x44, 0x33, 0x22, 0x11, # source_mac
+        0x08, 0x00, # ether_type
+        0b0100_0101, # ip_version, ip_header_length
+        0x00, # ip_type_of_service
+        0x00, 0x32, # ip_total_length
+        0x00, 0x00, # ip_identifier
+        0b000_0000000000000, # ip_flag, ip_fragment
+        0x80, # ip_ttl
+        0x01, # ip_protocol
+        0x12, 0x79, # ip_header_checksum
+        0xc0, 0xa8, 0x53, 0xfe, # source_ip_address
+        0xc0, 0xa8, 0x53, 0x03, # destination_ip_address
+        0x00, # icmp_type
+        0x00, # icmp_code
+        0xfe, 0xff, # icmp_checksum
+        0x01, 0x00, # icmp_identifier
+        0x00, 0x00, # icmp_sequence_number
+        0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, # padding
+      ].pack('C20nC42')
+      """
+
+  Scenario: Icmp::Reply instance inspection
+    When I create a packet with:
+      """
+      Pio::Icmp::Reply.new(
+        destination_mac: '00:26:82:eb:ea:d1',
+        source_mac: '00:16:9d:1d:9c:c4',
+        source_ip_address: '1.2.3.4',
+        destination_ip_address: '4.3.2.1',
+        icmp_identifier: 256,
+        icmp_sequence_number: 0
+      ).inspect
+      """
+    Then the result of eval should be:
+      """
+      #<Pio::Icmp::Reply destination_mac: "00:26:82:eb:ea:d1", source_mac: "00:16:9d:1d:9c:c4", ether_type: 0x0800, ip_version: 4, ip_header_length: 5, ip_type_of_service: 0, ip_total_length: 50, ip_identifier: 0, ip_flag: 0, ip_fragment: 0, ip_ttl: 128, ip_protocol: 1, ip_header_checksum: 12482, source_ip_address: "1.2.3.4", destination_ip_address: "4.3.2.1", ip_option: "", icmp_type: 0, icmp_code: 0, icmp_checksum: 65279, icmp_identifier: 256, icmp_sequence_number: 0, echo_data: "">
+      """
+
+  Scenario: Icmp::Reply class inspection
+    When I eval the following Ruby code:
+      """ruby
+      Pio::Icmp::Reply.inspect
+      """
+    Then the result of eval should be:
+      """
+      Pio::Icmp::Reply(destination_mac: mac_address, source_mac: mac_address, ether_type: ether_type, vlan_pcp: bit3, vlan_cfi: bit1, vlan_vid: bit12, ether_type_vlan: uint16, ip_version: bit4, ip_header_length: bit4, ip_type_of_service: uint8, ip_total_length: uint16, ip_identifier: uint16, ip_flag: bit3, ip_fragment: bit13, ip_ttl: uint8, ip_protocol: uint8, ip_header_checksum: uint16, source_ip_address: ip_address, destination_ip_address: ip_address, ip_option: string, icmp_type: uint8, icmp_code: uint8, icmp_checksum: uint16, icmp_identifier: uint16, icmp_sequence_number: uint16, echo_data: string)
+      """

data/features/icmp/icmp_request.feature

@@ -0,0 +1,89 @@
+Feature: Icmp::Request
+  Scenario: create an ICMP request
+    When I create a packet with:
+      """ruby
+      Pio::Icmp::Request.new(
+        source_mac: '11:22:33:44:55:66',
+        destination_mac: '66:55:44:33:22:11',
+        source_ip_address: '192.168.83.3',
+        destination_ip_address: '192.168.83.254',
+        icmp_identifier: 256,
+        icmp_sequence_number: 111,
+        echo_data: 'hello world'
+      )
+      """
+    Then the packet has the following fields and values:
+      | field                  |             value |
+      | source_mac             | 11:22:33:44:55:66 |
+      | destination_mac        | 66:55:44:33:22:11 |
+      | ether_type.to_hex      |             0x800 |
+      | ip_total_length        |                50 |
+      | ip_protocol            |                 1 |
+      | source_ip_address      |      192.168.83.3 |
+      | destination_ip_address |    192.168.83.254 |
+      | icmp_type              |                 8 |
+      | icmp_code              |                 0 |
+      | icmp_checksum          |             51394 |
+      | icmp_identifier        |               256 |
+      | icmp_sequence_number   |               111 |
+      | echo_data              |       hello world |
+
+  Scenario: convert an ICMP request to Ruby code
+    When I eval the following Ruby code:
+      """ruby
+      Pio::Icmp::Request.new(
+        destination_mac: '11:22:33:44:55:66',
+        source_mac: '66:55:44:33:22:11',
+        source_ip_address: '192.168.83.3',
+        destination_ip_address: '192.168.83.254'
+      ).to_ruby
+      """
+    Then the result of eval should be:
+      """ruby
+      [
+        0x11, 0x22, 0x33, 0x44, 0x55, 0x66, # destination_mac
+        0x66, 0x55, 0x44, 0x33, 0x22, 0x11, # source_mac
+        0x08, 0x00, # ether_type
+        0b0100_0101, # ip_version, ip_header_length
+        0x00, # ip_type_of_service
+        0x00, 0x32, # ip_total_length
+        0x00, 0x00, # ip_identifier
+        0b000_0000000000000, # ip_flag, ip_fragment
+        0x80, # ip_ttl
+        0x01, # ip_protocol
+        0x12, 0x79, # ip_header_checksum
+        0xc0, 0xa8, 0x53, 0x03, # source_ip_address
+        0xc0, 0xa8, 0x53, 0xfe, # destination_ip_address
+        0x08, # icmp_type
+        0x00, # icmp_code
+        0xf7, 0xff, # icmp_checksum
+        0x00, 0x00, # icmp_identifier
+        0x00, 0x00, # icmp_sequence_number
+        0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, # padding
+      ].pack('C20nC42')
+      """
+
+  Scenario: Icmp::Request instance inspection
+    When I create a packet with:
+      """ruby
+      Pio::Icmp::Request.new(
+        destination_mac: '00:26:82:eb:ea:d1',
+        source_mac: '00:16:9d:1d:9c:c4',
+        source_ip_address: '1.2.3.4',
+        destination_ip_address: '4.3.2.1'
+      ).inspect
+      """
+    Then the result of eval should be:
+      """
+      #<Pio::Icmp::Request destination_mac: "00:26:82:eb:ea:d1", source_mac: "00:16:9d:1d:9c:c4", ether_type: 0x0800, ip_version: 4, ip_header_length: 5, ip_type_of_service: 0, ip_total_length: 50, ip_identifier: 0, ip_flag: 0, ip_fragment: 0, ip_ttl: 128, ip_protocol: 1, ip_header_checksum: 12482, source_ip_address: "1.2.3.4", destination_ip_address: "4.3.2.1", ip_option: "", icmp_type: 8, icmp_code: 0, icmp_checksum: 63487, icmp_identifier: 0, icmp_sequence_number: 0, echo_data: "">
+      """
+
+  Scenario: Icmp::Request class inspection
+    When I eval the following Ruby code:
+      """ruby
+      Pio::Icmp::Request.inspect
+      """
+    Then the result of eval should be:
+      """
+      Pio::Icmp::Request(destination_mac: mac_address, source_mac: mac_address, ether_type: ether_type, vlan_pcp: bit3, vlan_cfi: bit1, vlan_vid: bit12, ether_type_vlan: uint16, ip_version: bit4, ip_header_length: bit4, ip_type_of_service: uint8, ip_total_length: uint16, ip_identifier: uint16, ip_flag: bit3, ip_fragment: bit13, ip_ttl: uint8, ip_protocol: uint8, ip_header_checksum: uint16, source_ip_address: ip_address, destination_ip_address: ip_address, ip_option: string, icmp_type: uint8, icmp_code: uint8, icmp_checksum: uint16, icmp_identifier: uint16, icmp_sequence_number: uint16, echo_data: string)
+      """

data/features/ipv4_header.feature

@@ -0,0 +1,89 @@
+Feature: IPv4Header
+  Scenario: create an IPv4 header
+    When I create a packet with:
+      """ruby
+      IPv4Header.new(source_ip_address: '1.2.3.4',
+                     destination_ip_address: '4.3.2.1')
+      """
+    Then the packet has the following fields and values:
+      | field                  |           value |
+      | class                  | Pio::IPv4Header |
+      | ip_version             |               4 |
+      | ip_header_length       |               5 |
+      | ip_type_of_service     |               0 |
+      | ip_total_length        |              20 |
+      | ip_identifier          |               0 |
+      | ip_flag                |               0 |
+      | ip_fragment            |               0 |
+      | ip_ttl                 |             128 |
+      | ip_protocol            |               0 |
+      | ip_header_checksum     |           12513 |
+      | source_ip_address      |         1.2.3.4 |
+      | destination_ip_address |         4.3.2.1 |
+      | ip_option              |                 |
+
+  Scenario: read an IPv4 header
+    Given I use the fixture "ipv4_header"
+    When I create a packet with:
+      """ruby
+      Pio::IPv4Header.read(eval(IO.read('ipv4_header.rb')))
+      """
+    Then the packet has the following fields and values:
+      | field                  |           value |
+      | class                  | Pio::IPv4Header |
+      | ip_version             |               4 |
+      | ip_header_length       |               5 |
+      | ip_type_of_service     |               0 |
+      | ip_total_length        |              20 |
+      | ip_identifier          |               0 |
+      | ip_flag                |               0 |
+      | ip_fragment            |               0 |
+      | ip_ttl                 |             128 |
+      | ip_protocol            |               0 |
+      | ip_header_checksum     |           12513 |
+      | source_ip_address      |         1.2.3.4 |
+      | destination_ip_address |         4.3.2.1 |
+      | ip_option              |                 |
+
+  Scenario: convert IPv4 header to Ruby code
+    When I eval the following Ruby code:
+      """ruby
+      IPv4Header.new(source_ip_address: '1.2.3.4',
+                     destination_ip_address: '4.3.2.1').to_ruby
+      """
+    Then the result of eval should be:
+      """ruby
+      [
+        0b0100_0101, # ip_version, ip_header_length
+        0x00, # ip_type_of_service
+        0x00, 0x14, # ip_total_length
+        0x00, 0x00, # ip_identifier
+        0b000_0000000000000, # ip_flag, ip_fragment
+        0x80, # ip_ttl
+        0x00, # ip_protocol
+        0x30, 0xe1, # ip_header_checksum
+        0x01, 0x02, 0x03, 0x04, # source_ip_address
+        0x04, 0x03, 0x02, 0x01, # destination_ip_address
+      ].pack('C6nC12')
+      """
+
+  Scenario: IPv4Header instance inspection
+    When I eval the following Ruby code:
+      """ruby
+      IPv4Header.new(source_ip_address: '1.2.3.4',
+                     destination_ip_address: '4.3.2.1').inspect
+      """
+    Then the result of eval should be:
+      """
+      #<Pio::IPv4Header ip_version: 4, ip_header_length: 5, ip_type_of_service: 0, ip_total_length: 20, ip_identifier: 0, ip_flag: 0, ip_fragment: 0, ip_ttl: 128, ip_protocol: 0, ip_header_checksum: 12513, source_ip_address: "1.2.3.4", destination_ip_address: "4.3.2.1", ip_option: "">
+      """
+
+  Scenario: IPv4Header class inspection
+    When I eval the following Ruby code:
+      """ruby
+      Pio::IPv4Header.inspect
+      """
+    Then the result of eval should be:
+      """
+      IPv4Header(ip_version: bit4, ip_header_length: bit4, ip_type_of_service: uint8, ip_total_length: uint16, ip_identifier: uint16, ip_flag: bit3, ip_fragment: bit13, ip_ttl: uint8, ip_protocol: uint8, ip_header_checksum: uint16, source_ip_address: ip_address, destination_ip_address: ip_address, ip_option: string)
+      """

data/features/lldp.feature

@@ -1,11 +1,10 @@
-Feature: Pio::Lldp
+Feature: Lldp
   Scenario: create
-    When I try to create an OpenFlow message with:
+    When I create an OpenFlow message with:
       """
       Pio::Lldp.new(dpid: 0x123, port_number: 12, source_mac: '11:22:33:44:55:66')
       """
-    Then it should finish successfully
-    And the message has the following fields and values:
+    Then the message has the following fields and values:
       | field                     |             value |
       | class                     |         Pio::Lldp |
       | destination_mac           | 01:80:c2:00:00:0e |
@@ -23,8 +22,7 @@ Feature: Pio::Lldp
       | organizationally_specific |                   |
 
   Scenario: parse lldp.minimal.pcap
-    When I try to parse a file named "lldp.minimal.pcap" with "Pio::Lldp" class
-    Then it should finish successfully
+    When I parse a file named "lldp.minimal.pcap" with "Pio::Lldp" class
     Then the message #1 have the following fields and values:
       | field                     | value             |
       | class                     | Pio::Lldp         |
@@ -43,5 +41,4 @@ Feature: Pio::Lldp
       | organizationally_specific |                   |
 
   Scenario: parse lldp.detailed.pcap
-    When I try to parse a file named "lldp.detailed.pcap" with "Pio::Lldp" class
-    Then it should finish successfully
+    Then I parse a file named "lldp.detailed.pcap" with "Pio::Lldp" class

data/features/open_flow/header.feature

@@ -0,0 +1,13 @@
+Feature: OpenFlow::Header
+
+  Scenario: OpenFlow::Header#to_hex
+    When I create an OpenFlow message with:
+      """
+      Pio::OpenFlow::Header.new(version: :OpenFlow10,
+                                type: 10,
+                                message_length: 18,
+                                transaction_id: 0xff)
+      """
+    Then the message has the following fields and values:
+      | field    | value                                          |
+      | to_bytes | 0x01, 0x0a, 0x00, 0x12, 0x00, 0x00, 0x00, 0xff |

data/features/open_flow/nicira_resubmit.feature

@@ -1,29 +1,11 @@
-Feature: Pio::NiciraResubmit
+@open_flow13
+Feature: NiciraResubmit
 
   Scenario: new(1)
-    When I try to create an OpenFlow action with:
+    When I create an OpenFlow action with:
       """
       Pio::NiciraResubmit.new(1)
       """
-    Then it should finish successfully
-    And the action has the following fields and values:
+    Then the action has the following fields and values:
       | field              |  value |
-      | action_type.to_hex | 0xffff |
-      | action_length      |     16 |
-      | vendor.to_hex      | 0x2320 |
-      | subtype            |      1 |
       | in_port            |      1 |
-
-  Scenario: new(:in_port)
-    When I try to create an OpenFlow action with:
-      """
-      Pio::NiciraResubmit.new(:in_port)
-      """
-    Then it should finish successfully
-    And the action has the following fields and values:
-      | field              |    value |
-      | action_type.to_hex |   0xffff |
-      | action_length      |       16 |
-      | vendor.to_hex      |   0x2320 |
-      | subtype            |        1 |
-      | in_port            | :in_port |

data/features/open_flow/nicira_resubmit_table.feature

@@ -1,31 +1,21 @@
-Feature: Pio::NiciraResubmitTable
+Feature: NiciraResubmitTable
 
   Scenario: new(in_port: 1, table: 1)
-    When I try to create an OpenFlow action with:
+    When I create an OpenFlow action with:
       """
       Pio::NiciraResubmitTable.new(in_port: 1, table: 1)
       """
-    Then it should finish successfully
-    And the action has the following fields and values:
+    Then the action has the following fields and values:
       | field              |  value |
-      | action_type.to_hex | 0xffff |
-      | action_length      |     16 |
-      | vendor.to_hex      | 0x2320 |
-      | subtype            |     14 |
       | in_port            |      1 |
       | table              |      1 |
 
-  Scenario: new(:in_port)
-    When I try to create an OpenFlow action with:
+  Scenario: new(in_port: 1)
+    When I create an OpenFlow action with:
       """
       Pio::NiciraResubmitTable.new(in_port: 1)
       """
-    Then it should finish successfully
-    And the action has the following fields and values:
+    Then the action has the following fields and values:
       | field              |  value |
-      | action_type.to_hex | 0xffff |
-      | action_length      |     16 |
-      | vendor.to_hex      | 0x2320 |
-      | subtype            |     14 |
       | in_port            |      1 |
       | table.to_hex       |   0xff |

data/features/open_flow10/aggregate_stats_reply.feature

@@ -1,13 +1,11 @@
 @open_flow10
-Feature: Pio::AggregateStats::Reply
+Feature: AggregateStats::Reply
+
   Scenario: read
-    When I try to parse a file named "open_flow10/aggregate_stats_reply.raw" with "AggregateStats::Reply" class
-    Then it should finish successfully
-    And the message has the following fields and values:
+    When I parse a file named "open_flow10/aggregate_stats_reply.raw" with "AggregateStats::Reply" class
+    Then the message has the following fields and values:
       | field          |      value |
-      | ofp_version    |          1 |
-      | message_type   |         17 |
-      | message_length |         36 |
+      | version        |          1 |
       | transaction_id |         15 |
       | xid            |         15 |
       | stats_type     | :aggregate |

data/features/open_flow10/aggregate_stats_request.feature

@@ -1,16 +1,17 @@
 @open_flow10
-Feature: Pio::AggregateStats::Request
+Feature: AggregateStats::Request
+
+  Aggregate information about multiple flows is requested with the
+  Aggregate Stats Request message
+
   Scenario: new
-    When I try to create an OpenFlow message with:
+    When I create an OpenFlow message with:
       """
-      Pio::AggregateStats::Request.new(match: Match.new(in_port: 1))
+      Pio::AggregateStats::Request.new(match: Pio::Match.new(in_port: 1))
       """
-    Then it should finish successfully
-    And the message has the following fields and values:
+    Then the message has the following fields and values:
       | field                                              | value      |
-      | ofp_version                                        | 1          |
-      | message_type                                       | 16         |
-      | message_length                                     | 56         |
+      | version                                            | 1          |
       | transaction_id                                     | 0          |
       | xid                                                | 0          |
       | stats_type                                         | :aggregate |
@@ -32,13 +33,10 @@ Feature: Pio::AggregateStats::Request
 
 
   Scenario: read
-    When I try to parse a file named "open_flow10/aggregate_stats_request.raw" with "AggregateStats::Request" class
-    Then it should finish successfully
-    And the message has the following fields and values:
+    When I parse a file named "open_flow10/aggregate_stats_request.raw" with "Pio::AggregateStats::Request" class
+    Then the message has the following fields and values:
       | field                                              | value      |
-      | ofp_version                                        | 1          |
-      | message_type                                       | 16         |
-      | message_length                                     | 56         |
+      | version                                            | 1          |
       | transaction_id                                     | 14         |
       | xid                                                | 14         |
       | stats_type                                         | :aggregate |

data/features/open_flow10/bad_request.feature

@@ -1,33 +1,16 @@
 @open_flow10
-Feature: Pio::Error::BadRequest
+Feature: Error::BadRequest
 
-  Request was not understood error.
+  Request was not understood error
 
-  Scenario: new (raw_data = Echo request 1.3)
-    When I try to create an OpenFlow message with:
+  Scenario: new (error_code: :bad_version, raw_data: EchoRequest 1.3)
+    When I create an OpenFlow message with:
       """
-      Pio::Error::BadRequest.new(raw_data: Pio::OpenFlow13::Echo::Request.new.to_binary)
+      Pio::Error::BadRequest.new(error_code: :bad_version,
+                                 raw_data: Pio::OpenFlow13::Echo::Request.new.to_binary)
       """
-    Then it should finish successfully
-    And the message has the following fields and values:
+    Then the message has the following fields and values:
       | field           |        value |
-      | ofp_version     |            1 |
-      | message_type    |            1 |
-      | message_length  |           20 |
-      | transaction_id  |            0 |
-      | xid             |            0 |
-      | error_type      | :bad_request |
-      | error_code      | :bad_version |
-      | raw_data.length |            8 |
-
-  Scenario: read
-    When I try to parse a file named "open_flow10/bad_request.raw" with "Pio::Error::BadRequest" class
-    Then it should finish successfully
-    And the message has the following fields and values:
-      | field           |        value |
-      | ofp_version     |            1 |
-      | message_type    |            1 |
-      | message_length  |           20 |
       | transaction_id  |            0 |
       | xid             |            0 |
       | error_type      | :bad_request |

data/features/open_flow10/barrier_reply.feature

@@ -1,43 +1,32 @@
 @open_flow10
-Feature: Pio::Barrier::Reply
+Feature: Barrier::Reply
+
+  When the switch received a Barrier Request message, the switch must
+  finish processing all previously-received messages before executing
+  any messages beyond the Barrier Request. When such processing is
+  complete, the switch must send an Barrier Reply message with the xid
+  of the original request.
+
   Scenario: new
-    When I try to create an OpenFlow message with:
+    When I create an OpenFlow message with:
       """
       Pio::Barrier::Reply.new
       """
-    Then it should finish successfully
-    And the message has the following fields and values:
+    Then the message has the following fields and values:
       | field          | value |
-      | ofp_version    |     1 |
-      | message_type   |    19 |
-      | message_length |     8 |
+      | version        |     1 |
       | transaction_id |     0 |
       | xid            |     0 |
       | body           |       |
 
   Scenario: new(transaction_id: 123)
-    When I try to create an OpenFlow message with:
+    When I create an OpenFlow message with:
       """
       Pio::Barrier::Reply.new(transaction_id: 123)
       """
-    Then it should finish successfully
-    And the message has the following fields and values:
+    Then the message has the following fields and values:
       | field          | value |
-      | ofp_version    |     1 |
-      | message_type   |    19 |
-      | message_length |     8 |
+      | version        |     1 |
       | transaction_id |   123 |
       | xid            |   123 |
       | body           |       |
-
-  Scenario: read
-    When I try to parse a file named "open_flow10/barrier_reply.raw" with "Barrier::Reply" class
-    Then it should finish successfully
-    And the message has the following fields and values:
-      | field          | value |
-      | ofp_version    |     1 |
-      | message_type   |    19 |
-      | message_length |     8 |
-      | transaction_id |     0 |
-      | xid            |     0 |
-      | body           |       |

data/features/open_flow10/barrier_request.feature

@@ -1,43 +1,30 @@
 @open_flow10
-Feature: Pio::Barrier::Request
+Feature: Barrier::Request
+
+  When the controller wants to ensure message dependencies have been
+  met or wants to receive notifications for completed operations, it
+  may use an Barrier Request message. This message has no body.
+
   Scenario: new
-    When I try to create an OpenFlow message with:
+    When I create an OpenFlow message with:
       """
       Pio::Barrier::Request.new
       """
-    Then it should finish successfully
-    And the message has the following fields and values:
+    Then the message has the following fields and values:
       | field          | value |
-      | ofp_version    |     1 |
-      | message_type   |    18 |
-      | message_length |     8 |
+      | version        |     1 |
       | transaction_id |     0 |
       | xid            |     0 |
       | body           |       |
 
   Scenario: new(transaction_id: 123)
-    When I try to create an OpenFlow message with:
+    When I create an OpenFlow message with:
       """
       Pio::Barrier::Request.new(transaction_id: 123)
       """
-    Then it should finish successfully
-    And the message has the following fields and values:
+    Then the message has the following fields and values:
       | field          | value |
-      | ofp_version    |     1 |
-      | message_type   |    18 |
-      | message_length |     8 |
+      | version        |     1 |
       | transaction_id |   123 |
       | xid            |   123 |
       | body           |       |
-      
-  Scenario: read
-    When I try to parse a file named "open_flow10/barrier_request.raw" with "Barrier::Request" class
-    Then it should finish successfully
-    And the message has the following fields and values:
-      | field          | value |
-      | ofp_version    |     1 |
-      | message_type   |    18 |
-      | message_length |     8 |
-      | transaction_id |     0 |
-      | xid            |     0 |
-      | body           |       |

data/features/open_flow10/description_stats_reply.feature

@@ -1,13 +1,15 @@
 @open_flow10
-Feature: Pio::DescriptionStats::Reply
+Feature: DescriptionStats::Reply
+
+  Information about the switch manufacturer, hardware revision,
+  software revision, serial number, and a description field is
+  available from a Description Stats Reply.
+
   Scenario: read
-    When I try to parse a file named "open_flow10/description_stats_reply.raw" with "DescriptionStats::Reply" class
-    Then it should finish successfully
-    And the message has the following fields and values:
+    When I parse a file named "open_flow10/description_stats_reply.raw" with "DescriptionStats::Reply" class
+    Then the message has the following fields and values:
       | field          |        value |
-      | ofp_version    |            1 |
-      | message_type   |           17 |
-      | message_length |         1068 |
+      | version        |            1 |
       | transaction_id |           12 |
       | xid            |           12 |
       | stats_type     | :description |