features/trema_commands/run.feature in trema-0.4.5 vs features/trema_commands/run.feature in trema-0.4.6

@@ -21,14 +21,33 @@
   Scenario: trema run launches switch_manager and an application with proper options
     When I run `trema -v run ../../objects/examples/learning_switch/learning_switch -c network.conf -d`
      And wait until "learning_switch" is up
     Then the output should contain:
      """
-     switch_manager --daemonize --port=6633 -- port_status::learning_switch packet_in::learning_switch state_notify::learning_switch vendor::learning_switch
+     switch_manager --daemonize --port=6653 -- port_status::learning_switch packet_in::learning_switch state_notify::learning_switch vendor::learning_switch
      """
      And the output should contain:
      """
      learning_switch --name learning_switch -d
+     """
+
+  @slow_process
+  Scenario: The --port option can override the default openflow channel port
+    When I run `which trema`
+    When I run `trema -v run ../../objects/examples/learning_switch/learning_switch -c network.conf --port 6633 -d`
+     And wait until "learning_switch" is up
+    Then the output should contain:
+     """
+     switch_manager --daemonize --port=6633 -- port_status::learning_switch packet_in::learning_switch state_notify::learning_switch vendor::learning_switch
+     """
+
+  @slow_process
+  Scenario: The -p option can override the default openflow channel port
+    When I run `trema -v run ../../objects/examples/learning_switch/learning_switch -c network.conf -p 6633 -d`
+     And wait until "learning_switch" is up
+    Then the output should contain:
+     """
+     switch_manager --daemonize --port=6633 -- port_status::learning_switch packet_in::learning_switch state_notify::learning_switch vendor::learning_switch
      """
 
   @slow_process
   Scenario: switch_manager is killed when trema session is closed
     When I run `trema -v run /bin/true -c network.conf`