aruba-win-fix 0.14.2

data/features/steps/command/stop.feature

@@ -0,0 +1,313 @@
+Feature: Stop commands
+
+  After you've started a command, you might want to stop a command. To do that
+  you've got multiple possibilities.
+
+  On "JRuby" it's not possible to read the output of command which `echo`s a
+  string in a `signal`-handler - `TERM`, `HUP` etc. So please don't write
+  tests, which check on this, if your script needs to run on "JRuby". All other
+  output is logged to `STDERR` and/or `STDOUT` as normal.
+
+  Background:
+    Given I use a fixture named "cli-app"
+
+  Scenario: Terminate last command started
+
+    Terminating a command will send `SIGTERM` to the command.
+
+    Given an executable named "bin/cli1" with:
+    """bash
+    #!/bin/bash
+
+    function term {
+      exit 100
+    }
+
+    trap term TERM
+    echo "Hello, Aruba!"
+    while [ true ]; do sleep 1; done
+    exit 1
+    """
+    And an executable named "bin/cli2" with:
+    """bash
+    #!/bin/bash
+
+    function term {
+      exit 155
+    }
+
+    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 run `cli2` in background
+        And I terminate the command started last
+        Then the exit status should be 155
+        And the output should contain:
+        \"\"\"
+        Hello, Aruba!
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Stop last command started
+
+    Stopping a command will wait n seconds for the command to stop and then
+    send `SIGTERM` to the command. Normally "n" is defined by the default exit
+    timeout of aruba.
+
+    Given an executable named "bin/cli1" with:
+    """bash
+    #!/bin/bash
+
+    function term {
+      exit 100
+    }
+
+    trap term TERM
+    echo "Hello, Aruba!"
+    while [ true ]; do sleep 1; done
+    exit 1
+    """
+    And an executable named "bin/cli2" with:
+    """bash
+    #!/bin/bash
+
+    function term {
+      exit 155
+    }
+
+    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
+      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
+        And I stop the command started last
+        Then the exit status should be 155
+        And the output should contain:
+        \"\"\"
+        Hello, Aruba!
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Terminate command given by commandline
+
+    Pass the commandline to the step to find the command, which should be
+    stopped.
+
+    Given an executable named "bin/cli1" with:
+    """bash
+    #!/bin/bash
+
+    function term {
+      exit 100
+    }
+
+    trap term TERM
+    echo "Hello, Aruba!"
+    while [ true ]; do sleep 1; done
+    """
+    And an executable named "bin/cli2" with:
+    """bash
+    #!/bin/bash
+
+    function term {
+      exit 155
+    }
+
+    trap term TERM
+    echo "Hello, Aruba!"
+    while [ true ]; do sleep 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
+
+      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"
+        Then the exit status should be 100
+        And the output should contain:
+        \"\"\"
+        Hello, Aruba!
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Stop command given by commandline
+
+    Stopping a command will wait n seconds for the command to stop and then
+    send `SIGTERM` to the command. Normally "n" is defined by the default exit
+    timeout of aruba.
+
+    Given an executable named "bin/cli1" with:
+    """bash
+    #!/bin/bash
+
+    function term {
+      exit 155
+    }
+
+    trap term TERM
+    echo "Hello, Aruba!"
+    while [ true ]; do sleep 1; done
+    exit 1
+    """
+    And an executable named "bin/cli2" with:
+    """bash
+    #!/bin/bash
+
+    function term {
+      exit 100
+    }
+
+    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
+      Background:
+        Given the default aruba exit timeout is 5 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"
+        Then the exit status should be 155
+        And the output should contain:
+        \"\"\"
+        Hello, Aruba!
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Stop command with configured signal
+
+    You can define a default signal which is used to stop all commands.
+
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/bin/bash
+    function hup {
+      exit 155
+    }
+
+    function term {
+      exit 100
+    }
+
+    trap hup HUP
+    trap term TERM
+    echo "Hello, Aruba!"
+    while [ true ]; do sleep 1; done
+    exit 1
+    """
+    And a file named "features/run.feature" with:
+    """
+    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`
+        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
+
+    function term {
+      echo 'Hello, TERM'
+      exit 100
+    }
+
+    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
+
+  @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:
+    """bash
+    #!/bin/bash
+
+    function term {
+      echo 'Hello, TERM'
+      exit 100
+    }
+
+    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 contain:
+        \"\"\"
+        Hello, TERM
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass

data/features/steps/core/announce.feature

@@ -0,0 +1,283 @@
+Feature: Announce output during test run
+
+  In order to specify expected output
+  As a developer using Cucumber
+  I want to use the "the output should contain" step
+
+  Background:
+    Given I use a fixture named "cli-app"
+
+  Scenario: Announce change of directory (deprecated)
+    Given a file named "features/exit_status.feature" with:
+    """cucumber
+    Feature: Announce
+      @announce-dir
+      Scenario: Run command
+        Given a directory named "dir.d"
+        When I cd to "dir.d"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+    And the output should contain:
+    """
+    $ cd /
+    """
+    And the output should contain:
+    """
+    tmp/aruba/dir.d
+    """
+
+  Scenario: Announce change of directory
+    Given a file named "features/exit_status.feature" with:
+    """cucumber
+    Feature: Announce
+      @announce-directory
+      Scenario: Run command
+        Given a directory named "dir.d"
+        When I cd to "dir.d"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+    And the output should contain:
+    """
+    $ cd /
+    """
+    And the output should contain:
+    """
+    tmp/aruba/dir.d
+    """
+
+  Scenario: Announce stdout
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo 'Hello World'
+    """
+    And a file named "features/exit_status.feature" with:
+    """cucumber
+    Feature: Announce
+      @announce-stdout
+      Scenario: Run command
+        When I run `cli`
+        Then the exit status should be 0
+    """
+    When I run `cucumber`
+    Then the features should all pass
+    And the output should contain:
+    """
+    <<-STDOUT
+    Hello World
+
+    STDOUT
+    """
+
+  Scenario: Announce stderr
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo 'Hello World' >&2
+    """
+    And a file named "features/exit_status.feature" with:
+    """cucumber
+    Feature: Announce
+      @announce-stderr
+      Scenario: Run command
+        When I run `cli`
+        Then the exit status should be 0
+    """
+    When I run `cucumber`
+    Then the features should all pass
+    And the output should contain:
+    """
+    <<-STDERR
+    Hello World
+
+    STDERR
+    """
+
+  Scenario: Announce both stderr and stdout
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo 'Hello' >&2
+    echo 'World'
+    """
+    And a file named "features/exit_status.feature" with:
+    """cucumber
+    Feature: Announce
+      @announce-output
+      Scenario: Run command
+        When I run `cli`
+        Then the exit status should be 0
+    """
+    When I run `cucumber`
+    Then the features should all pass
+    And the output should contain:
+    """
+    <<-STDERR
+    Hello
+
+    STDERR
+    """
+    And the output should contain:
+    """
+    <<-STDOUT
+    World
+
+    STDOUT
+    """
+
+  Scenario: Announce command
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo 'Hello World'
+    """
+    And a file named "features/exit_status.feature" with:
+    """cucumber
+    Feature: Announce
+      @announce-cmd
+      Scenario: Run command
+        When I run `cli`
+        Then the exit status should be 0
+    """
+    When I run `cucumber`
+    Then the features should all pass
+    And the output should contain:
+    """
+    $ cli
+    """
+
+  Scenario: Announce change of environment variable
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo 'Hello World'
+    """
+    And a file named "features/exit_status.feature" with:
+    """cucumber
+    Feature: Announce
+      @announce-env
+      Scenario: Run command
+        When I set the environment variables to:
+          | variable | value    |
+          | MY_VAR   | my_value |
+        And I run `cli`
+        Then the exit status should be 0
+    """
+    When I run `cucumber`
+    Then the features should all pass
+    And the output should contain:
+    """
+    $ export MY_VAR=my_value
+    """
+
+  Scenario: Announce change of environment variable which contains special characters
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo 'Hello World'
+    """
+    And a file named "features/exit_status.feature" with:
+    """cucumber
+    Feature: Announce
+      @announce-env
+      Scenario: Run command
+        When I set the environment variables to:
+          | variable | value      |
+          | MY_VAR   | my value ! |
+        And I run `cli`
+        Then the exit status should be 0
+    """
+    When I run `cucumber`
+    Then the features should all pass
+    And the output should contain:
+    """
+    $ export MY_VAR=my\ value\ \
+    """
+
+  Scenario: Announce file system status of command
+    This will output information like owner, group, atime, mtime, ctime, size,
+    mode and if command is executable.
+
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo 'Hello World'
+    """
+    And a file named "features/exit_status.feature" with:
+    """cucumber
+    Feature: Announce
+      @announce-command-filesystem-status
+      Scenario: Run command
+        And I run `cli`
+        Then the exit status should be 0
+    """
+    When I run `cucumber`
+    Then the features should all pass
+    And the output should contain:
+    """
+    # mode       => 755
+    """
+    And the output should contain:
+    """
+    # owner
+    """
+    And the output should contain:
+    """
+    # group
+    """
+    And the output should contain:
+    """
+    # ctime
+    """
+    And the output should contain:
+    """
+    # mtime
+    """
+    And the output should contain:
+    """
+    # atime
+    """
+    And the output should contain:
+    """
+    # size
+    """
+    And the output should contain:
+    """
+    # executable
+    """
+
+  Scenario: Announce content of command
+    This will output the content of the executable command. Be careful doing
+    this with binary executables. This hook should be used with scripts only.
+
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo 'Hello World'
+    """
+    And a file named "features/exit_status.feature" with:
+    """cucumber
+    Feature: Announce
+      @announce-command-content
+      Scenario: Run command
+        And I run `cli`
+        Then the exit status should be 0
+    """
+    When I run `cucumber`
+    Then the features should all pass
+    And the output should contain:
+    """
+    #!/usr/bin/env bash
+
+    echo 'Hello World'
+    """