aruba 0.14.9 → 0.14.10

data/features/{steps/command/exit_statuses.feature → 03_testing_frameworks/cucumber/steps/command/check_for_exit_statuses.feature}

@@ -7,7 +7,7 @@ Feature: Check exit status of commands
     Given I use a fixture named "cli-app"
 
   Scenario: Test for exit status of 0
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """
     #!/bin/bash
     exit 0
@@ -16,14 +16,14 @@ Feature: Check exit status of commands
     """
     Feature: Exit status
       Scenario: Run command
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the exit status should be 0
     """
     When I run `cucumber`
     Then the features should all pass
 
   Scenario: Test for exit status 1
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """
     #!/bin/bash
     exit 1
@@ -32,14 +32,14 @@ Feature: Check exit status of commands
     """
     Feature: Failing program
       Scenario: Run command
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the exit status should be 1
     """
     When I run `cucumber`
     Then the features should all pass
 
   Scenario: Test for non-zero exit status
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """
     #!/bin/bash
     exit 1
@@ -48,14 +48,14 @@ Feature: Check exit status of commands
     """
     Feature: Failing program
       Scenario: Run command
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the exit status should not be 0
     """
     When I run `cucumber`
     Then the features should all pass
 
   Scenario: Successfully run something
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """
     #!/bin/bash
     exit 0
@@ -64,13 +64,13 @@ Feature: Check exit status of commands
     """
     Feature: Failing program
       Scenario: Run command
-        When I successfully run `cli`
+        When I successfully run `aruba-test-cli`
     """
     When I run `cucumber`
     Then the features should all pass
 
   Scenario: Fail to run something successfully
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """
     #!/bin/bash
     exit 1
@@ -79,45 +79,45 @@ Feature: Check exit status of commands
     """
     Feature: Failing program
       Scenario: Run command
-        When I successfully run `cli`
+        When I successfully run `aruba-test-cli`
     """
     When I run `cucumber`
     Then the features should not all pass
 
   Scenario: Overwrite the default exit timeout via step
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """
     #!/bin/bash
-    sleep 1
+    sleep 0.1
     """
     And a file named "features/exit_status.feature" with:
     """
     Feature: Failing program
       Scenario: Run command
-        Given the default aruba exit timeout is 2 seconds
-        When I successfully run `cli`
+        Given the default aruba exit timeout is 0.2 seconds
+        When I successfully run `aruba-test-cli`
     """
     When I run `cucumber`
     Then the features should all pass
 
   Scenario: Successfully run something longer then the default time
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """
     #!/bin/bash
-    sleep 1
+    sleep 0.1
     """
     And a file named "features/exit_status.feature" with:
     """
     Feature: Failing program
       Scenario: Run command
         Given the default aruba exit timeout is 0 seconds
-        When I successfully run `cli` for up to 2 seconds
+        When I successfully run `aruba-test-cli` for up to 0.2 seconds
     """
     When I run `cucumber`
     Then the features should all pass
 
   Scenario: Unsuccessfully run something that takes too long
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """
     #!/bin/bash
     sleep 2
@@ -127,10 +127,10 @@ Feature: Check exit status of commands
     Feature: Failing program
       Scenario: Run command
         Given the default aruba exit timeout is 0 seconds
-        When I successfully run `cli` for up to 1 seconds
+        When I successfully run `aruba-test-cli` for up to 1 seconds
     """
     When I run `cucumber`
     Then the features should not all pass with:
     """
-    expected "cli" to have finished in time
+    expected "aruba-test-cli" to have finished in time
     """

data/features/{steps/command/output.feature → 03_testing_frameworks/cucumber/steps/command/check_output_of_command.feature}

@@ -8,7 +8,7 @@ Feature: All output of commands which were executed
     Given I use a fixture named "cli-app"
 
   Scenario: Detect subset of one-line output
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/usr/bin/env bash
 
@@ -18,14 +18,14 @@ Feature: All output of commands which were executed
     """cucumber
     Feature: Run command
       Scenario: Run command
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the output should contain "hello world"
     """
     When I run `cucumber`
     Then the features should all pass
 
   Scenario: Detect absence of one-line output
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/usr/bin/env bash
 
@@ -35,14 +35,14 @@ Feature: All output of commands which were executed
     """cucumber
     Feature: Run command
       Scenario: Run command
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the output should not contain "good-bye"
     """
     When I run `cucumber`
     Then the features should all pass
 
   Scenario: Detect subset of multiline output
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/usr/bin/env bash
 
@@ -52,7 +52,7 @@ Feature: All output of commands which were executed
     """cucumber
     Feature: Run command
       Scenario: Run command
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the output should contain:
         \"\"\"
         hello
@@ -62,7 +62,7 @@ Feature: All output of commands which were executed
     Then the features should all pass
 
   Scenario: Detect absence of subset of multiline output
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/usr/bin/env bash
 
@@ -72,7 +72,7 @@ Feature: All output of commands which were executed
     """cucumber
     Feature: Run command
       Scenario: Run command
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the output should not contain:
         \"\"\"
         good-bye
@@ -96,7 +96,7 @@ Feature: All output of commands which were executed
     Then the features should all pass
 
   Scenario: Detect exact one-line output with ANSI output
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/usr/bin/env bash
 
@@ -107,7 +107,7 @@ Feature: All output of commands which were executed
     Feature: Run command
       @keep-ansi-escape-sequences
       Scenario: Run command
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the output should contain exactly:
         \"\"\"
         \e[36mhello world\e[0m
@@ -118,7 +118,7 @@ Feature: All output of commands which were executed
 
   Scenario: Detect exact one-line output with ANSI output stripped by default
     Given the default aruba exit timeout is 12 seconds
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/usr/bin/env bash
 
@@ -128,7 +128,7 @@ Feature: All output of commands which were executed
     """cucumber
     Feature: Run command
       Scenario: Run command
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the output should contain exactly:
         \"\"\"
         hello world
@@ -138,7 +138,7 @@ Feature: All output of commands which were executed
     Then the features should all pass
 
   Scenario: Detect exact multiline output
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/usr/bin/env bash
 
@@ -148,7 +148,7 @@ Feature: All output of commands which were executed
     """cucumber
     Feature: Run command
       Scenario: Run command
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the output should contain exactly:
         \"\"\"
         hello
@@ -158,25 +158,8 @@ Feature: All output of commands which were executed
     When I run `cucumber`
     Then the features should all pass
 
-  Scenario: Detect subset of one-line output
-    Given an executable named "bin/cli" with:
-    """bash
-    #!/usr/bin/env bash
-
-    echo 'hello world'
-    """
-    And a file named "features/output.feature" with:
-    """cucumber
-    Feature: Run command
-      Scenario: Run command
-        When I run `cli`
-        Then the output should contain "hello world"
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
   Scenario: Detect subset of one-line output with regex
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/usr/bin/env bash
 
@@ -186,14 +169,14 @@ Feature: All output of commands which were executed
     """cucumber
     Feature: Run command
       Scenario: Run command
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the output should match /^hello(, world)?/
     """
     When I run `cucumber`
     Then the features should all pass
 
   Scenario: Detect subset of multiline output with regex
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/usr/bin/env bash
 
@@ -203,7 +186,7 @@ Feature: All output of commands which were executed
     """cucumber
     Feature: Run command
       Scenario: Run command
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the output should match:
         \"\"\"
         he..o
@@ -216,7 +199,7 @@ Feature: All output of commands which were executed
     Then the features should all pass
 
   Scenario: Negative matching of one-line output with regex
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/usr/bin/env bash
 
@@ -226,14 +209,14 @@ Feature: All output of commands which were executed
     """cucumber
     Feature: Run command
       Scenario: Run command
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the output should not match /ruby is a better perl$/
     """
     When I run `cucumber`
     Then the features should all pass
 
   Scenario: Negative matching of multiline output with regex
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/usr/bin/env bash
 
@@ -243,7 +226,7 @@ Feature: All output of commands which were executed
     """cucumber
     Feature: Run command
       Scenario: Run command
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the output should not match:
         \"\"\"
         ruby
@@ -257,7 +240,7 @@ Feature: All output of commands which were executed
     Then the features should all pass
 
   Scenario: Match passing exit status and partial output
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/usr/bin/env bash
 
@@ -268,7 +251,7 @@ Feature: All output of commands which were executed
     """cucumber
     Feature: Run command
       Scenario: Run command
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then it should pass with:
         \"\"\"
         hello
@@ -278,7 +261,7 @@ Feature: All output of commands which were executed
     Then the features should all pass
 
   Scenario: Match passing exit status and exact output
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/usr/bin/env bash
 
@@ -289,7 +272,7 @@ Feature: All output of commands which were executed
     """cucumber
     Feature: Run command
       Scenario: Run command
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then it should pass with exactly:
         \"\"\"
         hello
@@ -300,7 +283,7 @@ Feature: All output of commands which were executed
     Then the features should all pass
 
   Scenario: Match failing exit status and partial output
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/usr/bin/env bash
 
@@ -311,7 +294,7 @@ Feature: All output of commands which were executed
     """cucumber
     Feature: Run command
       Scenario: Run command
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then it should fail with:
         \"\"\"
         hello
@@ -322,7 +305,7 @@ Feature: All output of commands which were executed
 
 
   Scenario: Match failing exit status and exact output
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/usr/bin/env bash
 
@@ -333,7 +316,7 @@ Feature: All output of commands which were executed
     """cucumber
     Feature: Run command
       Scenario: Run command
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then it should fail with:
         \"\"\"
         hello
@@ -344,7 +327,7 @@ Feature: All output of commands which were executed
     Then the features should all pass
 
   Scenario: Match failing exit status and output with regex
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/usr/bin/env bash
 
@@ -355,7 +338,7 @@ Feature: All output of commands which were executed
     """cucumber
     Feature: Run command
       Scenario: Run command
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then it should fail with regex:
         \"\"\"
         hello\s*world
@@ -364,15 +347,14 @@ Feature: All output of commands which were executed
     When I run `cucumber`
     Then the features should all pass
 
-  @requires-aruba-version-1
   Scenario: Detect output from all processes
-    Given an executable named "bin/cli1" with:
+    Given an executable named "bin/aruba-test-cli1" with:
     """bash
     #!/usr/bin/env bash
 
     echo 'This is cli1'
     """
-    And an executable named "bin/cli2" with:
+    And an executable named "bin/aruba-test-cli2" with:
     """bash
     #!/usr/bin/env bash
 
@@ -382,39 +364,40 @@ Feature: All output of commands which were executed
     """cucumber
     Feature: Run command
       Scenario: Run command
-        When I run `cli1`
-        When I run `cli2`
+        When I run `aruba-test-cli1`
+        When I run `aruba-test-cli2`
         Then the stdout should contain exactly:
         \"\"\"
         This is cli1
-        \"\"\"
-        And the stdout should contain exactly:
-        \"\"\"
         This is cli2
         \"\"\"
     """
     When I run `cucumber`
     Then the features should all pass
 
-  Scenario: Detect output from all processes (deprecated)
-    Given an executable named "bin/cli1" with:
-    """bash
+  Scenario: Detect combined output from normal and interactive processes
+    Given an executable named "bin/aruba-test-cli1" with:
+    """
     #!/usr/bin/env bash
-
     echo 'This is cli1'
     """
-    And an executable named "bin/cli2" with:
-    """bash
-    #!/usr/bin/env bash
+    And an executable named "bin/aruba-test-cli2" with:
+    """
+    #!/usr/bin/env ruby
 
-    echo 'This is cli2'
+    while input = gets do
+      break if "" == input
+      puts input
+    end
     """
     And a file named "features/output.feature" with:
-    """cucumber
+    """
     Feature: Run command
       Scenario: Run command
-        When I run `cli1`
-        When I run `cli2`
+        When I run `aruba-test-cli1`
+        When I run `aruba-test-cli2` interactively
+        And I type "This is cli2"
+        And I type ""
         Then the stdout should contain exactly:
         \"\"\"
         This is cli1
@@ -425,11 +408,11 @@ Feature: All output of commands which were executed
     Then the features should all pass
 
   Scenario: Handle little output
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/usr/bin/env bash
 
-    for ((c=0; c<256; c = c+1)); do 
+    for ((c=0; c<256; c = c+1)); do
       echo -n "a"
     done
     """
@@ -437,7 +420,7 @@ Feature: All output of commands which were executed
     """cucumber
     Feature: Flushing output
       Scenario: Run command
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the output should contain "a"
         And the output should be 256 bytes long
         And the exit status should be 0
@@ -452,7 +435,7 @@ Feature: All output of commands which were executed
     I want to make sure that large amounts of output aren't buffered
 
     Given the default aruba exit timeout is 10 seconds
-    And an executable named "bin/cli" with:
+    And an executable named "bin/aruba-test-cli" with:
     """bash
     #!/usr/bin/env bash
 
@@ -464,7 +447,7 @@ Feature: All output of commands which were executed
     """cucumber
     Feature: Flushing output
       Scenario: Run command
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the output should contain "a"
         And the output should be 65536 bytes long
         And the exit status should be 0
@@ -474,7 +457,7 @@ Feature: All output of commands which were executed
 
   Scenario: Handle tons of interactive output
     Given the default aruba exit timeout is 10 seconds
-    And an executable named "bin/cli" with:
+    And an executable named "bin/aruba-test-cli" with:
     """bash
     #!/usr/bin/env bash
 
@@ -486,7 +469,7 @@ Feature: All output of commands which were executed
     """cucumber
     Feature: Flushing output
       Scenario: Run command
-        When I run `cli` interactively
+        When I run `aruba-test-cli` interactively
         And I type "65536"
         Then the output should contain "a"
         And the output should be 65536 bytes long
@@ -495,42 +478,6 @@ Feature: All output of commands which were executed
     When I run `cucumber`
     Then the features should all pass
 
-  @requires-aruba-version-1
-  Scenario: Detect output from all processes normal and interactive ones
-    Given an executable named "bin/cli1" with:
-    """
-    #!/usr/bin/env bash
-    echo 'This is cli1'
-    """
-    And an executable named "bin/cli2" with:
-    """
-    #!/usr/bin/env ruby
-
-    while input = gets do
-      break if "" == input
-      puts input
-    end
-    """
-    And a file named "features/output.feature" with:
-    """
-    Feature: Run command
-      Scenario: Run command
-        When I run `cli1`
-        When I run `cli2` interactively
-        And I type "This is cli2"
-        And I type ""
-        Then the stdout should contain exactly:
-        \"\"\"
-        This is cli1
-        \"\"\"
-        And the stdout should contain exactly:
-        \"\"\"
-        This is cli2
-        \"\"\"
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
   Scenario: Detect output from named source
     Given a file named "features/output.feature" with:
     """