trema 0.4.6 → 0.4.7

data/features/dsl/switch_port_specifier.feature

@@ -1,4 +1,4 @@
-@wip
+@wip @ruby
 Feature: Switch Port Specifier
   By adding a postfix (`:port#`) to the switch's name found in the `link` directive you can specify the exact port number to be used when the link is created.
 

data/features/examples/dumper.feature

@@ -16,16 +16,7 @@ Feature: "Dumper" sample application
       link "dumper", "host2"
       """
 
-  @slow_process
-  Scenario: Run "Dumper" C example
-    Given I run `trema run ../../objects/examples/dumper/dumper -c dumper.conf -d`
-     And wait until "dumper" is up
-    When I send 1 packet from host1 to host2
-    Then the file "../../tmp/log/dumper.log" should contain "[switch_ready]"
-     And the file "../../tmp/log/dumper.log" should contain "[packet_in]"
-     And the file "../../tmp/log/dumper.log" should contain "datapath_id: 0xabc"
-
-  @slow_process
+  @slow_process @critical @ruby
   Scenario: Run "Dumper" Ruby example
     Given I run `trema run ../../src/examples/dumper/dumper.rb -c dumper.conf -d`
      And wait until "Dumper" is up
@@ -34,34 +25,11 @@ Feature: "Dumper" sample application
      And the file "../../tmp/log/Dumper.log" should contain "[packet_in]"
      And the file "../../tmp/log/Dumper.log" should contain "datapath_id: 0xabc"
 
-  Scenario: "dumper --help"
-    When I run `../../objects/examples/dumper/dumper --help`
-    Then the output should contain exactly:
-      """
-      OpenFlow Event Dumper.
-      Usage: dumper [OPTION]...
-
-        -n, --name=SERVICE_NAME         service name
-        -d, --daemonize                 run in the background
-        -l, --logging_level=LEVEL       set logging level
-        -g, --syslog                    output log messages to syslog
-        -f, --logging_facility=FACILITY set syslog facility
-        -h, --help                      display this help and exit
-
-      """
-
-  Scenario: "dumper -h"
-    When I run `../../objects/examples/dumper/dumper -h`
-    Then the output should contain exactly:
-      """
-      OpenFlow Event Dumper.
-      Usage: dumper [OPTION]...
-
-        -n, --name=SERVICE_NAME         service name
-        -d, --daemonize                 run in the background
-        -l, --logging_level=LEVEL       set logging level
-        -g, --syslog                    output log messages to syslog
-        -f, --logging_facility=FACILITY set syslog facility
-        -h, --help                      display this help and exit
-
-      """
+  @slow_process
+  Scenario: Run "Dumper" C example
+    Given I run `trema run ../../objects/examples/dumper/dumper -c dumper.conf -d`
+     And wait until "dumper" is up
+    When I send 1 packet from host1 to host2
+    Then the file "../../tmp/log/dumper.log" should contain "[switch_ready]"
+     And the file "../../tmp/log/dumper.log" should contain "[packet_in]"
+     And the file "../../tmp/log/dumper.log" should contain "datapath_id: 0xabc"

data/features/examples/hello_trema.feature

@@ -11,7 +11,7 @@ Feature: "Hello Trema!" example
   Background:
     Given I cd to "../../src/examples/hello_trema/"
 
-  @slow_process
+  @slow_process @critical @ruby
   Scenario: Run the Ruby example
     When I run `trema run ./hello-trema.rb -c sample.conf` interactively
     Then the output should contain "Hello 0xabc!" within the timeout period

data/features/examples/learning_switch.feature

@@ -16,10 +16,10 @@ Feature: "Learning Switch" sample application
       link "learning", "host2"
       """
 
-  @slow_process
-  Scenario: Run "Learning Switch" C example
-    Given I run `trema run ../../objects/examples/learning_switch/learning_switch -c learning_switch.conf -d`
-     And wait until "learning_switch" is up
+  @slow_process @ruby
+  Scenario: Run "Learning Switch" Ruby example
+    Given I run `trema run ../../src/examples/learning_switch/learning-switch.rb -c learning_switch.conf -d`
+     And wait until "LearningSwitch" is up
     When I send 1 packet from host1 to host2
      And I run `trema show_stats host1 --tx`
      And I run `trema show_stats host2 --rx`
@@ -27,9 +27,9 @@ Feature: "Learning Switch" sample application
      And the output from "trema show_stats host2 --rx" should contain "192.168.0.2,1,192.168.0.1,1,1,50"
 
   @slow_process
-  Scenario: Run "Learning Switch" Ruby example
-    Given I run `trema run ../../src/examples/learning_switch/learning-switch.rb -c learning_switch.conf -d`
-     And wait until "LearningSwitch" is up
+  Scenario: Run "Learning Switch" C example
+    Given I run `trema run ../../objects/examples/learning_switch/learning_switch -c learning_switch.conf -d`
+     And wait until "learning_switch" is up
     When I send 1 packet from host1 to host2
      And I run `trema show_stats host1 --tx`
      And I run `trema show_stats host2 --rx`

data/features/examples/list_switches.feature

@@ -13,12 +13,12 @@ Feature: "List Switches" sample application
       vswitch { datapath_id 0x4 }
       """
 
+  @slow_process @ruby
+  Scenario: Run "List Switches" Ruby example
+    Given I run `trema run ../../src/examples/list_switches/list-switches.rb -c list_switches.conf`
+    Then the file "../../tmp/log/ListSwitches.log" should contain "switches = 0x1, 0x2, 0x3, 0x4"
+
   @slow_process
   Scenario: Run "List Switches" C example
     Given I run `trema run ../../objects/examples/list_switches/list_switches -c list_switches.conf`
     Then the file "../../tmp/log/list_switches.log" should contain "switches = 0x1, 0x2, 0x3, 0x4"
-
-  @slow_process
-  Scenario: Run "List Switches" Ruby example
-    Given I run `trema run ../../src/examples/list_switches/list-switches.rb -c list_switches.conf`
-    Then the file "../../tmp/log/ListSwitches.log" should contain "switches = 0x1, 0x2, 0x3, 0x4"

data/features/examples/message.set_config.feature

@@ -4,24 +4,24 @@ Feature: Send set config messages
   I want to send set config messages to openflow switches
   So that I can set configuration parameters of openflow switches
 
-  @wip
-  Scenario: set config x 10
-    When I try trema run "./objects/examples/openflow_message/set_config 10" with following configuration (backgrounded):
+  @wip @ruby
+  Scenario: set config x 10 in Ruby
+    When I try trema run "./src/examples/openflow_message/set-config.rb 0xabc, 10" with following configuration (backgrounded):
       """
-      vswitch("set_config") { datapath_id "0xabc" }
+      vswitch("set-config") { datapath_id "0xabc" }
       """
-      And wait until "set_config" is up
+      And wait until "SetConfigController" is up
       And *** sleep 2 ***
       And I run `trema killall`
-    Then the log file "openflowd.set_config.log" should include "received: OFPT_SET_CONFIG" x 11
+    Then the log file "openflowd.set-config.log" should include "received: OFPT_SET_CONFIG" x 11
 
   @wip
-  Scenario: set config x 10 in Ruby
-    When I try trema run "./src/examples/openflow_message/set-config.rb 0xabc, 10" with following configuration (backgrounded):
+  Scenario: set config x 10
+    When I try trema run "./objects/examples/openflow_message/set_config 10" with following configuration (backgrounded):
       """
-      vswitch("set-config") { datapath_id "0xabc" }
+      vswitch("set_config") { datapath_id "0xabc" }
       """
-      And wait until "SetConfigController" is up
+      And wait until "set_config" is up
       And *** sleep 2 ***
       And I run `trema killall`
-    Then the log file "openflowd.set-config.log" should include "received: OFPT_SET_CONFIG" x 11
+    Then the log file "openflowd.set_config.log" should include "received: OFPT_SET_CONFIG" x 11

data/features/examples/message.vendor-action.feature

@@ -10,16 +10,16 @@ Feature: "Vendor Action" sample application
       vswitch( "vendor_action" ) { datapath_id "0xabc" }
       """
 
-  @slow_process
-  Scenario: Vendor Action message in C
-  Given I run `trema run ../../objects/examples/openflow_message/vendor_action -c vendor_action.conf -d`
-   And wait until "vendor_action" is up
+  @slow_process @ruby
+  Scenario: Vendor Action message in Ruby
+  Given I run `trema run ../../src/examples/openflow_message/vendor-action.rb -c vendor_action.conf -d`
+   And wait until "VendorActionSampleController" is up
    And *** sleep 2 ***
   Then the file "../../tmp/log/openflowd.vendor_action.log" should contain "actions=note:54.72.65.6d.61.00"
 
   @slow_process
-  Scenario: Vendor Action message in Ruby
-  Given I run `trema run ../../src/examples/openflow_message/vendor-action.rb -c vendor_action.conf -d`
-   And wait until "VendorActionSampleController" is up
+  Scenario: Vendor Action message in C
+  Given I run `trema run ../../objects/examples/openflow_message/vendor_action -c vendor_action.conf -d`
+   And wait until "vendor_action" is up
    And *** sleep 2 ***
   Then the file "../../tmp/log/openflowd.vendor_action.log" should contain "actions=note:54.72.65.6d.61.00"

data/features/examples/message.vendor-stats-request.feature

@@ -10,7 +10,7 @@ Feature: "Vendor Stats Request" sample application
       vswitch( "vendor_stats" ) { datapath_id "0xabc" }
       """
 
-  @slow_process
+  @slow_process @ruby
   Scenario: Vendor Stats Request message in Ruby
   Given I run `trema run ../../src/examples/openflow_message/vendor-stats-request.rb -c vendor_stats.conf -d`
    And wait until "VendorStatsRequestSample" is up

data/features/examples/multi_learning_switch.feature

@@ -26,10 +26,10 @@ Feature: "Multi Learning Switch" sample application
       link "multi_learning3", "multi_learning4"
       """
 
-  @slow_process
-  Scenario: Run "Multi Learning Switch" C example
-    Given I run `trema run ../../objects/examples/multi_learning_switch/multi_learning_switch -c multi_learning_switch.conf -d`
-     And wait until "multi_learning_switch" is up
+  @slow_process @ruby
+  Scenario: Run "Multi Learning Switch" Ruby example
+    Given I run `trema run ../../src/examples/multi_learning_switch/multi-learning-switch.rb -c multi_learning_switch.conf -d`
+     And wait until "MultiLearningSwitch" is up
     When I send 2 packets from host1 to host2
     Then the total number of tx packets should be:
       | host1 | host2 | host3 | host4 |
@@ -67,9 +67,9 @@ Feature: "Multi Learning Switch" sample application
       |     2 |     2 |     4 |     4 |
 
   @slow_process
-  Scenario: Run "Multi Learning Switch" Ruby example
-    Given I run `trema run ../../src/examples/multi_learning_switch/multi-learning-switch.rb -c multi_learning_switch.conf -d`
-     And wait until "MultiLearningSwitch" is up
+  Scenario: Run "Multi Learning Switch" C example
+    Given I run `trema run ../../objects/examples/multi_learning_switch/multi_learning_switch -c multi_learning_switch.conf -d`
+     And wait until "multi_learning_switch" is up
     When I send 2 packets from host1 to host2
     Then the total number of tx packets should be:
       | host1 | host2 | host3 | host4 |

data/features/examples/openflow_message.echo.feature

@@ -4,19 +4,19 @@ Feature: Send echo request and receive echo reply messages
   As a Trema user
   I want to send echo request messages to openflow switches and receive echo replies
 
-  @slow_process
-  Scenario: Echo request and reply in C
-    Given a file named "echo.conf" with:
+  @slow_process @ruby
+  Scenario: Echo request and reply in Ruby
+    Given a file named "echo.ruby.conf" with:
       """
-      custom_switch("echo") { 
+      custom_switch("echo.ruby") { 
         datapath_id "0xabc" 
         path "./objects/examples/openflow_switch/echo_switch"
       }
       """
-    When I run `trema run "../../objects/examples/openflow_message/echo 10" -c echo.conf -d`
-      And wait until "echo" is up
+    When I run `trema run "../../src/examples/openflow_message/echo.rb 0xabc, 10" -c echo.ruby.conf -d`
+      And wait until "EchoController" is up
       And I run `trema killall`
-    Then the file "../../tmp/log/customswitch.echo.log" should contain:
+    Then the file "../../tmp/log/customswitch.echo.ruby.log" should contain:
       """
       received: OFPT_ECHO_REQUEST
       received: OFPT_ECHO_REQUEST
@@ -29,21 +29,21 @@ Feature: Send echo request and receive echo reply messages
       received: OFPT_ECHO_REQUEST
       received: OFPT_ECHO_REQUEST
       """
-      And the file "../../tmp/log/echo.log" should match /received: OFPT_ECHO_REPLY/
+      # And the file "../../tmp/log/EchoController.log" should match /received: OFPT_ECHO_REPLY/
 
   @slow_process
-  Scenario: Echo request and reply in Ruby
-    Given a file named "echo.ruby.conf" with:
+  Scenario: Echo request and reply in C
+    Given a file named "echo.conf" with:
       """
-      custom_switch("echo.ruby") { 
+      custom_switch("echo") { 
         datapath_id "0xabc" 
         path "./objects/examples/openflow_switch/echo_switch"
       }
       """
-    When I run `trema run "../../src/examples/openflow_message/echo.rb 0xabc, 10" -c echo.ruby.conf -d`
-      And wait until "EchoController" is up
+    When I run `trema run "../../objects/examples/openflow_message/echo 10" -c echo.conf -d`
+      And wait until "echo" is up
       And I run `trema killall`
-    Then the file "../../tmp/log/customswitch.echo.ruby.log" should contain:
+    Then the file "../../tmp/log/customswitch.echo.log" should contain:
       """
       received: OFPT_ECHO_REQUEST
       received: OFPT_ECHO_REQUEST
@@ -56,4 +56,4 @@ Feature: Send echo request and receive echo reply messages
       received: OFPT_ECHO_REQUEST
       received: OFPT_ECHO_REQUEST
       """
-      # And the file "../../tmp/log/EchoController.log" should match /received: OFPT_ECHO_REPLY/
+      And the file "../../tmp/log/echo.log" should match /received: OFPT_ECHO_REPLY/

data/features/examples/openflow_message.features_request.feature

@@ -10,6 +10,18 @@ Feature: Send a features request message
      vswitch( "features_request" ) { datapath_id "0xabc" }
      """
 
+  @slow_process @ruby
+  Scenario: Feature Request message in Ruby
+    When I run `trema run ../../src/examples/openflow_message/features-request.rb -c features_request.conf -d`
+     And wait until "FeaturesRequestController" is up
+     And I run `trema killall`
+    Then the file "../../tmp/log/FeaturesRequestController.log" should match /datapath_id: 0xabc/
+     And the file "../../tmp/log/FeaturesRequestController.log" should match /n_buffers:/
+     And the file "../../tmp/log/FeaturesRequestController.log" should match /n_tables:/
+     And the file "../../tmp/log/FeaturesRequestController.log" should match /capabilities:/
+     And the file "../../tmp/log/FeaturesRequestController.log" should match /actions:/
+     And the file "../../tmp/log/FeaturesRequestController.log" should match /ports:/
+
   @slow_process
   Scenario: Features Request message in C
     When I run `trema run ../../objects/examples/openflow_message/features_request -c features_request.conf -d`
@@ -21,15 +33,3 @@ Feature: Send a features request message
      And the file "../../tmp/log/features_request.log" should match /capabilities:/
      And the file "../../tmp/log/features_request.log" should match /actions:/
      And the file "../../tmp/log/features_request.log" should match /ports:/
-
-  @slow_process
-  Scenario: Feature Request message in Ruby
-    When I run `trema run ../../src/examples/openflow_message/features-request.rb -c features_request.conf -d`
-     And wait until "FeaturesRequestController" is up
-     And I run `trema killall`
-    Then the file "../../tmp/log/FeaturesRequestController.log" should match /datapath_id: 0xabc/
-     And the file "../../tmp/log/FeaturesRequestController.log" should match /n_buffers:/
-     And the file "../../tmp/log/FeaturesRequestController.log" should match /n_tables:/
-     And the file "../../tmp/log/FeaturesRequestController.log" should match /capabilities:/
-     And the file "../../tmp/log/FeaturesRequestController.log" should match /actions:/
-     And the file "../../tmp/log/FeaturesRequestController.log" should match /ports:/

data/features/examples/openflow_message.hello.feature

@@ -4,19 +4,19 @@ Feature: Send hello messages
   As a Trema user
   I want to send hello messages to openflow switches
 
-  @slow_process
-  Scenario: Hello message in C
-    Given a file named "hello.conf" with:
+  @slow_process @ruby
+  Scenario: Hello message in Ruby
+    Given a file named "hello-r.conf" with:
       """
-      custom_switch("hello") { 
+      custom_switch("hello-r") { 
         datapath_id "0xabc" 
         path "./objects/examples/openflow_switch/hello_switch"
       }
       """
-    When I run `trema run "../../objects/examples/openflow_message/hello 10" -c hello.conf -d`
-      And wait until "hello" is up
+    When I run `trema run "../../src/examples/openflow_message/hello.rb 10" -c hello-r.conf -d`
+      And wait until "HelloController" is up
       And I run `trema killall`
-    Then the file "../../tmp/log/customswitch.hello.log" should contain:
+    Then the file "../../tmp/log/customswitch.hello-r.log" should contain:
       """
       received: OFPT_HELLO
       received: OFPT_HELLO
@@ -32,18 +32,18 @@ Feature: Send hello messages
       """
 
   @slow_process
-  Scenario: Hello message in Ruby
-    Given a file named "hello-r.conf" with:
+  Scenario: Hello message in C
+    Given a file named "hello.conf" with:
       """
-      custom_switch("hello-r") { 
+      custom_switch("hello") { 
         datapath_id "0xabc" 
         path "./objects/examples/openflow_switch/hello_switch"
       }
       """
-    When I run `trema run "../../src/examples/openflow_message/hello.rb 10" -c hello-r.conf -d`
-      And wait until "HelloController" is up
+    When I run `trema run "../../objects/examples/openflow_message/hello 10" -c hello.conf -d`
+      And wait until "hello" is up
       And I run `trema killall`
-    Then the file "../../tmp/log/customswitch.hello-r.log" should contain:
+    Then the file "../../tmp/log/customswitch.hello.log" should contain:
       """
       received: OFPT_HELLO
       received: OFPT_HELLO

data/features/examples/packet_in.feature

@@ -16,6 +16,14 @@ Feature: "Packet In" sample application
       link "packet_in", "host2"
       """
 
+  @slow_process @ruby
+  Scenario: Run "Packet In" Ruby example
+    Given I run `trema run ../../src/examples/packet_in/packet-in.rb -c packet_in.conf -d`
+     And wait until "PacketInDumper" is up
+    When I send 1 packet from host1 to host2
+     And *** sleep 1 ***
+    Then the file "../../tmp/log/PacketInDumper.log" should contain "received a packet_in"
+
   @slow_process
   Scenario: Run "Packet In" C example
     Given I run `trema run ../../objects/examples/packet_in/packet_in -c packet_in.conf -d`
@@ -23,11 +31,3 @@ Feature: "Packet In" sample application
     When I send 1 packet from host1 to host2
      And *** sleep 1 ***
     Then the file "../../tmp/log/packet_in.log" should contain "received a packet_in"
-
-  @slow_process
-  Scenario: Run "Packet In" Ruby example
-    Given I run `trema run ../../src/examples/packet_in/packet-in.rb -c packet_in.conf -d`
-     And wait until "PacketInDumper" is up
-    When I send 1 packet from host1 to host2
-     And *** sleep 1 ***
-    Then the file "../../tmp/log/PacketInDumper.log" should contain "received a packet_in"

data/features/examples/patch_panel.feature

@@ -4,7 +4,7 @@ Feature: "Patch Panel" sample application
   As a developer using Trema
   I want to execute "Patch Panel" sample application
 
-  @slow_process
+  @slow_process @ruby
   Scenario: Run "Patch Panel" Ruby example
     Given a file named "patch-panel.conf" with:
       """

data/features/examples/repeater_hub.feature

@@ -27,10 +27,10 @@ Feature: "Repeater Hub" sample application
       link "repeater_hub", "host3"
       """
 
-  @slow_process
-  Scenario: Run "Repeater Hub" C example
-    Given I run `trema run ../../objects/examples/repeater_hub/repeater_hub -c repeater_hub.conf -d`
-     And wait until "repeater_hub" is up
+  @slow_process @ruby
+  Scenario: Run "Repeater Hub" Ruby example
+    Given I run `trema run ../../src/examples/repeater_hub/repeater-hub.rb -c repeater_hub.conf -d`
+     And wait until "RepeaterHub" is up
     When I send 1 packet from host1 to host2
      And I run `trema show_stats host1 --tx`
      And I run `trema show_stats host2 --rx`
@@ -40,9 +40,9 @@ Feature: "Repeater Hub" sample application
      And the output from "trema show_stats host3 --rx" should contain "192.168.0.2,1,192.168.0.1,1,1,50"
 
   @slow_process
-  Scenario: Run "Repeater Hub" Ruby example
-    Given I run `trema run ../../src/examples/repeater_hub/repeater-hub.rb -c repeater_hub.conf -d`
-     And wait until "RepeaterHub" is up
+  Scenario: Run "Repeater Hub" C example
+    Given I run `trema run ../../objects/examples/repeater_hub/repeater_hub -c repeater_hub.conf -d`
+     And wait until "repeater_hub" is up
     When I send 1 packet from host1 to host2
      And I run `trema show_stats host1 --tx`
      And I run `trema show_stats host2 --rx`

data/features/examples/switch_info.feature

@@ -4,48 +4,48 @@ Feature: "Switch Info" sample application
   As a developer using Trema
   I want to execute "Switch Info" sample application
 
-  @slow_process
-  Scenario: Run "Switch Info" C example
+  @slow_process @ruby
+  Scenario: Run "Switch Info" Ruby example
     Given a file named "switch_info.conf" with:
       """
       vswitch { datapath_id 0xabc }
       """
-     And I run `trema run ../../objects/examples/switch_info/switch_info -c switch_info.conf -d`
+     And I run `trema run ../../src/examples/switch_info/switch-info.rb -c switch_info.conf -d`
      And *** sleep 2 ***
-    Then the file "../../tmp/log/switch_info.log" should contain "datapath_id: 0xabc"
-     And the file "../../tmp/log/switch_info.log" should contain "#ports: 1"
+    Then the file "../../tmp/log/SwitchInfo.log" should contain "datapath_id: 0xabc"
+     And the file "../../tmp/log/SwitchInfo.log" should contain "#ports: 1"
 
-  @slow_process
-  Scenario: Run "Switch Info" C example with two switches
+  @slow_process @ruby
+  Scenario: Run "Switch Info" Ruby example with two switches
    Given a file named "switch_info.conf" with:
       """
       vswitch { datapath_id 0xabc }
       vswitch { datapath_id 0xdef }
       link "0xabc", "0xdef"
       """
-     And I run `trema run ../../objects/examples/switch_info/switch_info -c switch_info.conf -d`
+     And I run `trema run ../../src/examples/switch_info/switch-info.rb -c switch_info.conf -d`
      And *** sleep 2 ***
-    Then the file "../../tmp/log/switch_info.log" should contain "#ports: 2"
+    Then the file "../../tmp/log/SwitchInfo.log" should contain "#ports: 2"
 
   @slow_process
-  Scenario: Run "Switch Info" Ruby example
+  Scenario: Run "Switch Info" C example
     Given a file named "switch_info.conf" with:
       """
       vswitch { datapath_id 0xabc }
       """
-     And I run `trema run ../../src/examples/switch_info/switch-info.rb -c switch_info.conf -d`
+     And I run `trema run ../../objects/examples/switch_info/switch_info -c switch_info.conf -d`
      And *** sleep 2 ***
-    Then the file "../../tmp/log/SwitchInfo.log" should contain "datapath_id: 0xabc"
-     And the file "../../tmp/log/SwitchInfo.log" should contain "#ports: 1"
+    Then the file "../../tmp/log/switch_info.log" should contain "datapath_id: 0xabc"
+     And the file "../../tmp/log/switch_info.log" should contain "#ports: 1"
 
   @slow_process
-  Scenario: Run "Switch Info" Ruby example with two switches
+  Scenario: Run "Switch Info" C example with two switches
    Given a file named "switch_info.conf" with:
       """
       vswitch { datapath_id 0xabc }
       vswitch { datapath_id 0xdef }
       link "0xabc", "0xdef"
       """
-     And I run `trema run ../../src/examples/switch_info/switch-info.rb -c switch_info.conf -d`
+     And I run `trema run ../../objects/examples/switch_info/switch_info -c switch_info.conf -d`
      And *** sleep 2 ***
-    Then the file "../../tmp/log/SwitchInfo.log" should contain "#ports: 2"
+    Then the file "../../tmp/log/switch_info.log" should contain "#ports: 2"