aruba-win-fix 0.14.2

data/features/steps/command/run.feature

@@ -0,0 +1,66 @@
+Feature: Run commands
+
+  There are several steps to run commands with `aruba`.
+
+  Background:
+    Given I use a fixture named "cli-app"
+
+  Scenario: Run command found in path
+    Given an executable named "bin/cli" with:
+    """
+    #!/bin/bash
+    exit 0
+    """
+    And a file named "features/run.feature" with:
+    """
+    Feature: Run it
+      Scenario: Run command
+        When I run `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:
+    """
+    #!/bin/bash
+    echo "Hello, I'm STDOUT"
+    exit 1
+    """
+    And a file named "features/run.feature" with:
+    """
+    Feature: Run it
+      Scenario: Run command
+        When I successfully run `cli`
+    """
+    And I append to "features/support/env.rb" with:
+    """
+    Before do
+      aruba.config.activate_announcer_on_command_failure = [:stdout]
+    end
+    """
+    When I run `cucumber`
+    Then the features should not pass
+    And the output should contain:
+    """
+    <<-STDOUT
+    Hello, I'm STDOUT
+
+    STDOUT
+    """
+
+  Scenario: Run command found in "bin"-directory which is found in the current directory
+    Given a file named "features/run.feature" with:
+    """
+    Feature: Run it
+      Scenario: Run command
+        Given an executable named "bin/local_cli" with:
+        \"\"\"
+        #!/bin/bash
+        exit 0
+        \"\"\"
+        And I look for executables in "bin" within the current directory
+        When I successfully run `local_cli`
+    """
+    When I run `cucumber`
+    Then the features should all pass

data/features/steps/command/send_signal.feature

@@ -0,0 +1,104 @@
+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"`
+
+  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:
+    """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:
+    """
+    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 started last
+        Then the exit status should be 0
+        And the output should contain:
+        \"\"\"
+        Got signal HUP.
+        \"\"\"
+    """
+    When I run `cucumber`
+    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:
+    """
+    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"
+        Then the exit status should be 0
+        And the output should contain:
+        \"\"\"
+        Got signal HUP.
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  @unsupported-on-platform-windows
+  @experimental
+  Scenario: Using the "kill"-command
+
+    `<pid-last-command-started>` in your command line will be replaced by the
+    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:
+    """
+    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 run `kill -HUP <pid-last-command-started>`
+        Then the output should contain:
+        \"\"\"
+        Got signal HUP.
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass

data/features/steps/command/shell.feature

@@ -0,0 +1,155 @@
+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 (bash|zsh|...shell)? commands`
+  - `I run the following (bash|zsh|...shell)? commands (in|with) \`interpreter\``
+  - `I run the following (bash|zsh|...shell)? 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 exactly "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 bash commands
+    Given a file named "features/shell.feature" with:
+    """
+    Feature: Running scripts
+      Scenario: Running bash commands
+        When I run the following commands with `bash`:
+        \"\"\"bash
+        echo -n "Hello "
+        echo `echo bash` # subshell
+        \"\"\"
+        Then the output should contain exactly "Hello bash"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Running zsh commands
+    Given a file named "features/shell.feature" with:
+    """
+    Feature: Running zsh scripts
+      Scenario: Running zsh commands
+        When I run the following commands with `zsh`:
+        \"\"\"bash
+        echo "Hello \c"
+        echo $((2 + 2))
+        \"\"\"
+        Then the output should contain exactly "Hello 4"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Running ruby commands
+    Given a file named "features/shell.feature" with:
+    """
+    Feature: Running scripts
+      Scenario: Running ruby commands
+        When I run the following commands with `ruby`:
+        \"\"\"ruby
+        puts "Hello, Aruba!"
+        \"\"\"
+        Then the output should contain exactly "Hello, Aruba!"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Running python commands
+    Given a file named "features/shell.feature" with:
+    """
+    Feature: Running scripts
+      Scenario: Running ruby commands
+        When I run the following commands with `python`:
+        \"\"\"ruby
+        print("Hello, Aruba!")
+        \"\"\"
+        Then the output should contain exactly "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 zsh
+      Scenario: Running zsh commands #1
+        When I run the following commands with `/bin/zsh`:
+        \"\"\"bash
+        echo "Hello \c"
+        echo $((6 - 2))
+        \"\"\"
+        Then the output should contain exactly "Hello 4"
+
+      Scenario: Running zsh commands #1
+        When I run the following commands in `/bin/zsh`:
+        \"\"\"bash
+        echo "Hello \c"
+        echo $((6 - 2))
+        \"\"\"
+        Then the output should contain exactly "Hello 4"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Running commands if only the name of interpreter is given
+    Given a file named "features/shell.feature" with:
+    """
+    Feature: Running full path zsh
+      Scenario: Running zsh commands #1
+        When I run the following commands with `zsh`:
+        \"\"\"bash
+        echo "Hello \c"
+        echo $((6 - 2))
+        \"\"\"
+        Then the output should contain exactly "Hello 4"
+
+      Scenario: Running zsh commands #2
+        When I run the following commands in `zsh`:
+        \"\"\"bash
+        echo "Hello \c"
+        echo $((6 - 2))
+        \"\"\"
+        Then the output should contain exactly "Hello 4"
+    """
+    When I run `cucumber`
+    Then the features should all pass

data/features/steps/command/stderr.feature

@@ -0,0 +1,68 @@
+Feature: STDERR of commands which were executed
+
+  In order to specify expected output
+  As a developer using Cucumber
+  I want to use the "the stderr should contain" step
+
+  Background:
+    Given I use a fixture named "cli-app"
+
+  Scenario: Detect stderr from all processes
+    Given a file named "features/output.feature" with:
+    """
+    Feature: Run command
+      Scenario: Run command
+        When I run `bash -c 'printf "hello world!\n" >&2'`
+        And I run `bash -c 'cat >&2 '` interactively
+        And I type "hola"
+        And I type ""
+        Then the stderr should contain:
+        \"\"\"
+        hello world!
+        \"\"\"
+        And the stderr should contain:
+        \"\"\"
+        hola
+        \"\"\"
+        And the stdout should not contain anything
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Detect stderr from all processes (deprecated)
+    Given a file named "features/output.feature" with:
+    """
+    Feature: Run command
+      Scenario: Run command
+        When I run `bash -c 'printf "hello world!\n" >&2'`
+        And I run `bash -c 'cat >&2 '` interactively
+        And I type "hola"
+        And I type ""
+        Then the stderr should contain:
+        \"\"\"
+        hello world!
+        hola
+        \"\"\"
+        And the stdout should not contain anything
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Detect stderr from named source
+    Given a file named "features/output.feature" with:
+    """
+    Feature: Run command
+      Scenario: Run command
+        When I run `bash -c 'printf hello >&2'`
+        And I run `printf goodbye`
+        Then the stderr from "bash -c 'printf hello >&2'" should contain "hello"
+        And the stderr from "bash -c 'printf hello >&2'" should contain exactly "hello"
+        And the stderr from "bash -c 'printf hello >&2'" should contain exactly:
+        \"\"\"
+        hello
+        \"\"\"
+        And the stdout from "bash -c 'printf hello >&2'" should not contain "hello"
+        And the stderr from "printf goodbye" should not contain "hello"
+    """
+    When I run `cucumber`
+    Then the features should all pass

data/features/steps/command/stdout.feature

@@ -0,0 +1,109 @@
+Feature: STDOUT of commands which were executed
+
+  In order to specify expected output
+  As a developer using Cucumber
+  I want to use the "the stdout should contain" step
+
+  Background:
+    Given I use a fixture named "cli-app"
+
+  Scenario: Match output in stdout
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo -e "hello\nworld"
+    """
+    And a file named "features/output.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        When I run `cli`
+        Then the stdout should contain "hello"
+        Then the stderr should not contain "hello"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Match stdout on several lines
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo 'GET /'
+    """
+    And a file named "features/output.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        When I run `cli`
+        Then the stdout should contain:
+        \"\"\"
+        GET /
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Match output on several lines where stdout contains quotes
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    echo 'GET "/"'
+    """
+    And a file named "features/output.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        When I run `cli`
+        Then the stdout should contain:
+        \"\"\"
+        GET "/"
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Detect stdout from all processes including interactive ones
+    Given a file named "features/output.feature" with:
+    """
+    Feature: Run command
+      Scenario: Run command
+        When I run `printf "hello world!\n"`
+        And I run `cat` interactively
+        And I type "hola"
+        And I type ""
+        Then the stdout should contain:
+        \"\"\"
+        hello world!
+        \"\"\"
+        And the stdout should contain:
+        \"\"\"
+        hola
+        \"\"\"
+        And the stderr should not contain anything
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Detect stdout from named source
+    Given a file named "features/output.feature" with:
+    """
+    Feature: Run command
+      Scenario: Run command
+        When I run `printf 'hello'`
+        And I run `printf 'goodbye'`
+        Then the stdout from "printf 'hello'" should contain "hello"
+        And the stdout from "printf 'hello'" should contain exactly "hello"
+        And the stdout from "printf 'hello'" should contain exactly:
+        \"\"\"
+        hello
+        \"\"\"
+        And the stderr from "printf 'hello'" should not contain "hello"
+        And the stdout from "printf 'goodbye'" should not contain "hello"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+