aruba 0.14.9 → 0.14.10

data/features/{steps/command/stderr.feature → 03_testing_frameworks/cucumber/steps/command/check_stderr_of_command.feature}

@@ -29,7 +29,7 @@ Feature: STDERR of commands which were executed
     When I run `cucumber`
     Then the features should all pass
 
-  Scenario: Detect stderr from all processes (deprecated)
+  Scenario: Detect stderr from all processes
     Given a file named "features/output.feature" with:
     """
     Feature: Run command

data/features/{steps/command/stdout.feature → 03_testing_frameworks/cucumber/steps/command/check_stdout_of_command.feature}

@@ -8,7 +8,7 @@ Feature: STDOUT of commands which were executed
     Given I use a fixture named "cli-app"
 
   Scenario: Match output in stdout
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/usr/bin/env bash
 
@@ -18,7 +18,7 @@ Feature: STDOUT of commands which were executed
     """cucumber
     Feature: Run command
       Scenario: Run command
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the stdout should contain "hello"
         Then the stderr should not contain "hello"
     """
@@ -26,7 +26,7 @@ Feature: STDOUT of commands which were executed
     Then the features should all pass
 
   Scenario: Match stdout on several lines
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/usr/bin/env bash
 
@@ -36,7 +36,7 @@ Feature: STDOUT of commands which were executed
     """cucumber
     Feature: Run command
       Scenario: Run command
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the stdout should contain:
         \"\"\"
         GET /
@@ -46,7 +46,7 @@ Feature: STDOUT of commands which were executed
     Then the features should all pass
 
   Scenario: Match output on several lines where stdout contains quotes
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/usr/bin/env bash
 
@@ -56,7 +56,7 @@ Feature: STDOUT of commands which were executed
     """cucumber
     Feature: Run command
       Scenario: Run command
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the stdout should contain:
         \"\"\"
         GET "/"

data/features/{steps/command/debug.feature → 03_testing_frameworks/cucumber/steps/command/debug_your_command_in_aruba.feature}

@@ -9,7 +9,7 @@ Feature: Debug your command in cucumber-test-run
     And the default aruba exit timeout is 60 seconds
 
   Scenario: Can handle exit status 0
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/usr/bin/env bash
 
@@ -21,14 +21,14 @@ Feature: Debug your command in cucumber-test-run
 
       @debug
       Scenario: Run program with debug code
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the exit status should be 0
     """
     When I successfully run `cucumber`
     Then the features should all pass
 
   Scenario: Can handle exit status 1
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/usr/bin/env bash
 
@@ -40,7 +40,7 @@ Feature: Debug your command in cucumber-test-run
 
       @debug
       Scenario: Run program with debug code
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the exit status should be 1
     """
     When I successfully run `cucumber`
@@ -60,7 +60,7 @@ Feature: Debug your command in cucumber-test-run
     We are going to demonstrate this using `pry`, but any other interactive
     debugger for any other programming language should also work.
 
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """ruby
     #!/usr/bin/env ruby
 
@@ -78,7 +78,7 @@ Feature: Debug your command in cucumber-test-run
 
       @debug
       Scenario: Run program with debug code
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the exit status should be 0
     """
     When I run `cucumber` interactively

data/features/{steps/command/run.feature → 03_testing_frameworks/cucumber/steps/command/run_a_command.feature}

@@ -6,7 +6,7 @@ Feature: Run commands
     Given I use a fixture named "cli-app"
 
   Scenario: Run command found in path
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """
     #!/bin/bash
     exit 0
@@ -15,13 +15,13 @@ Feature: Run commands
     """
     Feature: Run it
       Scenario: Run command
-        When I run `cli`
+        When I run `aruba-test-cli`
     """
     When I run `cucumber`
     Then the features should all pass
 
   Scenario: Activate desired announcers when running command fails
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """
     #!/bin/bash
     echo "Hello, I'm STDOUT"
@@ -31,7 +31,7 @@ Feature: Run commands
     """
     Feature: Run it
       Scenario: Run command
-        When I successfully run `cli`
+        When I successfully run `aruba-test-cli`
     """
     And I append to "features/support/env.rb" with:
     """

data/features/{steps/command/in_process.feature → 03_testing_frameworks/cucumber/steps/command/run_command_in_process.feature}

@@ -103,7 +103,7 @@ Feature: Run commands in ruby process
     Then the features should all pass
 
   Scenario: Mixing custom code and normal cli
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """
     #!/bin/bash
     echo $*
@@ -140,7 +140,7 @@ Feature: Run commands in ruby process
         \"\"\"
 
       Scenario: Run command
-        When I run `cli Hello World`
+        When I run `aruba-test-cli Hello World`
         Then the output should contain:
         \"\"\"
         Hello World

data/features/{steps/command/interactive.feature → 03_testing_frameworks/cucumber/steps/command/run_command_interactively.feature}

@@ -9,7 +9,7 @@ Feature: Running an interactive command
 
   @wip-jruby-java-1.6
   Scenario: Running ruby interactively
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/usr/bin/env ruby
 
@@ -22,7 +22,7 @@ Feature: Running an interactive command
     """cucumber
     Feature: Run command
       Scenario: Run command
-        When I run `cli` interactively
+        When I run `aruba-test-cli` interactively
         And I type "hello, world"
         And I type "quit"
         Then it should pass with "dlrow ,olleh"

data/features/03_testing_frameworks/cucumber/steps/command/run_commands_which_require_a_shell.feature

@@ -0,0 +1,79 @@
+Feature: Running shell commands
+
+  You can run an *ad hoc* script with the following steps:
+  - `When I run the following script:`
+
+  Or you can run shell commands with:
+  - `I run the following commands`
+  - `I run the following commands (in|with) \`interpreter\``
+  - `I run the following commands (in|with) \`/path/to/interpreter\``
+
+  Background:
+    Given I use a fixture named "cli-app"
+
+  Scenario: Creating and running scripts
+    Given a file named "features/shell.feature" with:
+    """
+    Feature: Running scripts
+      Scenario: Running ruby script
+        When I run the following script:
+        \"\"\"bash
+        #!/usr/bin/env ruby
+
+        puts "Hello"
+        \"\"\"
+        Then the output should contain "Hello"
+
+      Scenario: Running python script
+        When I run the following script:
+        \"\"\"bash
+        #!/usr/bin/env python
+
+        print("Hello")
+        \"\"\"
+        Then the output should contain exactly "Hello"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Running shell commands
+    Given a file named "features/shell.feature" with:
+    """
+    Feature: Running scripts
+      Scenario: Running shell commands
+        When I run the following commands:
+        \"\"\"bash
+        echo "Hello shell"
+        \"\"\"
+        Then the output should contain exactly "Hello shell"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Running commands with a named interpreter
+    Given a file named "features/shell.feature" with:
+    """
+    Feature: Running scripts
+      Scenario: Running ruby commands
+        When I run the following commands with `ruby`:
+        \"\"\"
+        puts "Hello, Aruba!"
+        \"\"\"
+        Then the output should contain "Hello, Aruba!"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Running commands if full path to interpreter is given
+    Given a file named "features/shell.feature" with:
+    """
+    Feature: Running full path
+      Scenario: Running full path bash
+        When I run the following commands with `/bin/bash`:
+        \"\"\"bash
+        echo "Hello Aruba!"
+        \"\"\"
+        Then the output should contain "Hello Aruba!"
+    """
+    When I run `cucumber`
+    Then the features should all pass

data/features/{steps/command/send_signal.feature → 03_testing_frameworks/cucumber/steps/command/send_signal_to_command.feature}

@@ -3,15 +3,13 @@ Feature: Send a signal to command
   You can send a command a signal with the following steps:
 
   - `When I send the signal "HUP" to the command started last`
-  - `When I send the signal "HUP" to the command "bin/cli"`
+  - `When I send the signal "HUP" to the command "bin/aruba-test-cli"`
 
   Or just use `kill` on compatible platforms.
 
   Background:
     Given I use a fixture named "cli-app"
-
-  Scenario: Sending signal to the command started last
-    Given an executable named "bin/cli" with:
+    And an executable named "bin/aruba-test-cli" with:
     """bash
     #!/usr/bin/env bash
     function hup {
@@ -20,15 +18,22 @@ Feature: Send a signal to command
     }
 
     trap hup HUP
-    while [ true ]; do sleep 1; done
+    while [ true ]; do sleep 0.1; done
+    """
+    And a file named "features/support/aruba_config.rb" with:
+    """ruby
+    Aruba.configure do |config|
+      config.startup_wait_time = 0.1
+      config.exit_timeout = 0.2
+    end
     """
-    And a file named "features/run.feature" with:
+
+  Scenario: Sending signal to the command started last
+    Given a file named "features/run.feature" with:
     """
     Feature: Run it
       Scenario: Run command
-        Given the default aruba exit timeout is 5 seconds
-        And I wait 5 seconds for a command to start up
-        When I run `cli` in background
+        When I run `aruba-test-cli` in background
         And I send the signal "HUP" to the command started last
         Then the exit status should be 0
         And the output should contain:
@@ -40,25 +45,12 @@ Feature: Send a signal to command
     Then the features should all pass
 
   Scenario: Sending signal to a command given by command line
-    Given an executable named "bin/cli" with:
-    """bash
-    #!/usr/bin/env bash
-    function hup {
-      echo "Got signal HUP."
-      exit 0
-    }
-
-    trap hup HUP
-    while [ true ]; do sleep 1; done
-    """
-    And a file named "features/run.feature" with:
+    Given a file named "features/run.feature" with:
     """
     Feature: Run it
       Scenario: Run command
-        Given the default aruba exit timeout is 5 seconds
-        And I wait 5 seconds for a command to start up
-        When I run `cli` in background
-        And I send the signal "HUP" to the command "cli"
+        When I run `aruba-test-cli` in background
+        And I send the signal "HUP" to the command "aruba-test-cli"
         Then the exit status should be 0
         And the output should contain:
         \"\"\"
@@ -76,24 +68,11 @@ Feature: Send a signal to command
     PID of the last command started. Please note, this feature is experimental.
     The name of the variable may change without further notice.
 
-    Given an executable named "bin/cli" with:
-    """bash
-    #!/usr/bin/env bash
-    function hup {
-      echo "Got signal HUP."
-      exit 0
-    }
-
-    trap hup HUP
-    while [ true ]; do sleep 1; done
-    """
-    And a file named "features/run.feature" with:
+    Given a file named "features/run.feature" with:
     """
     Feature: Run it
       Scenario: Run command
-        Given the default aruba exit timeout is 5 seconds
-        And I wait 5 seconds for a command to start up
-        When I run `cli` in background
+        When I run `aruba-test-cli` in background
         And I run `kill -HUP <pid-last-command-started>`
         Then the output should contain:
         \"\"\"

data/features/{steps/command/stop.feature → 03_testing_frameworks/cucumber/steps/command/stop_command.feature}

@@ -15,7 +15,7 @@ Feature: Stop commands
 
     Terminating a command will send `SIGTERM` to the command.
 
-    Given an executable named "bin/cli1" with:
+    Given an executable named "bin/aruba-test-cli1" with:
     """bash
     #!/bin/bash
 
@@ -25,10 +25,10 @@ Feature: Stop commands
 
     trap term TERM
     echo "Hello, Aruba!"
-    while [ true ]; do sleep 1; done
+    while [ true ]; do sleep 0.1; done
     exit 1
     """
-    And an executable named "bin/cli2" with:
+    And an executable named "bin/aruba-test-cli2" with:
     """bash
     #!/bin/bash
 
@@ -38,17 +38,17 @@ Feature: Stop commands
 
     trap term TERM
     echo "Hello, Aruba!"
-    while [ true ]; do sleep 1; done
+    while [ true ]; do sleep 0.1; done
     exit 1
     """
     And a file named "features/stop.feature" with:
     """
     Feature: Run it
       Scenario: Run command
-        Given the default aruba exit timeout is 1 second
-        And I wait 2 seconds for a command to start up
-        When I run `cli1` in background
-        And I run `cli2` in background
+        Given the default aruba exit timeout is 0.2 seconds
+        And I wait 0.1 seconds for a command to start up
+        When I run `aruba-test-cli1` in background
+        And I run `aruba-test-cli2` in background
         And I terminate the command started last
         Then the exit status should be 155
         And the output should contain:
@@ -65,7 +65,7 @@ Feature: Stop commands
     send `SIGTERM` to the command. Normally "n" is defined by the default exit
     timeout of aruba.
 
-    Given an executable named "bin/cli1" with:
+    Given an executable named "bin/aruba-test-cli1" with:
     """bash
     #!/bin/bash
 
@@ -75,10 +75,10 @@ Feature: Stop commands
 
     trap term TERM
     echo "Hello, Aruba!"
-    while [ true ]; do sleep 1; done
+    while [ true ]; do sleep 0.1; done
     exit 1
     """
-    And an executable named "bin/cli2" with:
+    And an executable named "bin/aruba-test-cli2" with:
     """bash
     #!/bin/bash
 
@@ -88,7 +88,7 @@ Feature: Stop commands
 
     trap term TERM
     echo "Hello, Aruba!"
-    while [ true ]; do sleep 1; done
+    while [ true ]; do sleep 0.1; done
     exit 1
     """
     And a file named "features/stop.feature" with:
@@ -97,10 +97,10 @@ Feature: Stop commands
       Background:
 
       Scenario: Run command
-        Given the default aruba exit timeout is 5 seconds
-        And I wait 2 seconds for a command to start up
-        When I run `cli1` in background
-        And I run `cli2` in background
+        Given the default aruba exit timeout is 0.2 seconds
+        And I wait 0.1 seconds for a command to start up
+        When I run `aruba-test-cli1` in background
+        And I run `aruba-test-cli2` in background
         And I stop the command started last
         Then the exit status should be 155
         And the output should contain:
@@ -116,7 +116,7 @@ Feature: Stop commands
     Pass the commandline to the step to find the command, which should be
     stopped.
 
-    Given an executable named "bin/cli1" with:
+    Given an executable named "bin/aruba-test-cli1" with:
     """bash
     #!/bin/bash
 
@@ -126,9 +126,9 @@ Feature: Stop commands
 
     trap term TERM
     echo "Hello, Aruba!"
-    while [ true ]; do sleep 1; done
+    while [ true ]; do sleep 0.1; done
     """
-    And an executable named "bin/cli2" with:
+    And an executable named "bin/aruba-test-cli2" with:
     """bash
     #!/bin/bash
 
@@ -138,20 +138,20 @@ Feature: Stop commands
 
     trap term TERM
     echo "Hello, Aruba!"
-    while [ true ]; do sleep 1; done
+    while [ true ]; do sleep 0.1; done
     exit 2
     """
     And a file named "features/stop.feature" with:
     """
     Feature: Run it
       Background:
-        Given the default aruba exit timeout is 5 seconds
+        Given the default aruba exit timeout is 0.2 seconds
 
       Scenario: Run command
-        Given I wait 2 seconds for a command to start up
-        When I run `cli1` in background
-        When I run `cli2` in background
-        And I terminate the command "cli1"
+        Given I wait 0.1 seconds for a command to start up
+        When I run `aruba-test-cli1` in background
+        When I run `aruba-test-cli2` in background
+        And I terminate the command "aruba-test-cli1"
         Then the exit status should be 100
         And the output should contain:
         \"\"\"
@@ -167,7 +167,7 @@ Feature: Stop commands
     send `SIGTERM` to the command. Normally "n" is defined by the default exit
     timeout of aruba.
 
-    Given an executable named "bin/cli1" with:
+    Given an executable named "bin/aruba-test-cli1" with:
     """bash
     #!/bin/bash
 
@@ -177,10 +177,10 @@ Feature: Stop commands
 
     trap term TERM
     echo "Hello, Aruba!"
-    while [ true ]; do sleep 1; done
+    while [ true ]; do sleep 0.1; done
     exit 1
     """
-    And an executable named "bin/cli2" with:
+    And an executable named "bin/aruba-test-cli2" with:
     """bash
     #!/bin/bash
 
@@ -190,20 +190,20 @@ Feature: Stop commands
 
     trap term TERM
     echo "Hello, Aruba!"
-    while [ true ]; do sleep 1; done
+    while [ true ]; do sleep 0.1; done
     exit 1
     """
     And a file named "features/stop.feature" with:
     """
     Feature: Run it
       Background:
-        Given the default aruba exit timeout is 5 seconds
+        Given the default aruba exit timeout is 0.2 seconds
 
       Scenario: Run command
-        Given I wait 2 seconds for a command to start up
-        When I run `cli1` in background
-        And I run `cli2` in background
-        When I stop the command "cli1"
+        Given I wait 0.1 seconds for a command to start up
+        When I run `aruba-test-cli1` in background
+        And I run `aruba-test-cli2` in background
+        When I stop the command "aruba-test-cli1"
         Then the exit status should be 155
         And the output should contain:
         \"\"\"
@@ -217,7 +217,7 @@ Feature: Stop commands
 
     You can define a default signal which is used to stop all commands.
 
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/bin/bash
     function hup {
@@ -231,7 +231,7 @@ Feature: Stop commands
     trap hup HUP
     trap term TERM
     echo "Hello, Aruba!"
-    while [ true ]; do sleep 1; done
+    while [ true ]; do sleep 0.1; done
     exit 1
     """
     And a file named "features/run.feature" with:
@@ -239,49 +239,21 @@ Feature: Stop commands
     Feature: Run it
       Scenario: Run command
         Given the default aruba stop signal is "HUP"
-        And the default aruba exit timeout is 5 seconds
-        When I run `cli`
+        And the default aruba exit timeout is 0.2 seconds
+        When I run `aruba-test-cli`
         Then the exit status should be 155
     """
     When I run `cucumber`
     Then the features should all pass
 
-  @requires-ruby-platform-java
-  Scenario: STDERR/STDOUT is empty on JRUBY if output was written in "signal"-handler
-    Given an executable named "bin/cli1" with:
-    """bash
-    #!/bin/bash
+  @requires-ruby-platform-mri
+  Scenario: STDERR/STDOUT is captured from signal handlers
 
-    function term {
-      echo 'Hello, TERM'
-      exit 100
-    }
+     STDERR/STDOUT is written normally on MRI if output was written in "signal"-handler
 
-    trap term TERM
-    echo "Hello, Aruba!"
-    while [ true ]; do sleep 1; done
-    exit 1
-    """
-    And a file named "features/stop.feature" with:
-    """
-    Feature: Run it
-      Scenario: Run command
-        Given the default aruba exit timeout is 1 second
-        And I wait 2 seconds for a command to start up
-        When I run `cli1` in background
-        And I terminate the command started last
-        Then the exit status should be 100
-        And the output should not contain:
-        \"\"\"
-        Hello, TERM
-        \"\"\"
-    """
-    When I run `cucumber`
-    Then the features should all pass
+     This is currently broken on JRuby.
 
-  @requires-ruby-platform-mri
-  Scenario: STDERR/STDOUT is written normally with MRI-Ruby if output was written in "signal"-handler
-    Given an executable named "bin/cli1" with:
+    Given an executable named "bin/aruba-test-cli1" with:
     """bash
     #!/bin/bash
 
@@ -292,16 +264,16 @@ Feature: Stop commands
 
     trap term TERM
     echo "Hello, Aruba!"
-    while [ true ]; do sleep 1; done
+    while [ true ]; do sleep 0.1; done
     exit 1
     """
     And a file named "features/stop.feature" with:
     """
     Feature: Run it
       Scenario: Run command
-        Given the default aruba exit timeout is 1 second
-        And I wait 2 seconds for a command to start up
-        When I run `cli1` in background
+        Given the default aruba exit timeout is 0.2 seconds
+        And I wait 0.1 seconds for a command to start up
+        When I run `aruba-test-cli1` in background
         And I terminate the command started last
         Then the exit status should be 100
         And the output should contain: