aruba 0.14.9 → 0.14.10

data/features/{steps → 03_testing_frameworks/cucumber/steps}/environment/append_environment_variable.feature

@@ -8,7 +8,7 @@ Feature: Append environment variable via "cucumber"-step
 
   Background:
     Given I use the fixture "cli-app"
-    And an executable named "bin/cli" with:
+    And an executable named "bin/aruba-test-cli" with:
     """
     #!/bin/bash
 
@@ -27,7 +27,7 @@ Feature: Append environment variable via "cucumber"-step
         Given I append the values to the environment variables:
           | variable           | value      |
           | LONG_LONG_VARIABLE | long_value |
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the output should contain:
         \"\"\"
         1long_value
@@ -42,7 +42,7 @@ Feature: Append environment variable via "cucumber"-step
     Feature: Environment Variable
       Scenario: Run command
         Given I append "long_value" to the environment variable "LONG_LONG_VARIABLE"
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the output should contain:
         \"\"\"
         1long_value

data/features/{steps/environment/home_variable.feature → 03_testing_frameworks/cucumber/steps/environment/modify_home_variable_for_testing.feature}

@@ -11,7 +11,7 @@ Feature: Mock the HOME variable
 
   Background:
     Given I use the fixture "cli-app"
-    And an executable named "bin/cli" with:
+    And an executable named "bin/aruba-test-cli" with:
     """
     #!/bin/bash
 
@@ -24,7 +24,7 @@ Feature: Mock the HOME variable
     Feature: Home Variable
       Scenario: Run command
         Given a mocked home directory
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the output should match %r<HOME:.*tmp/aruba$>
     """
     When I run `cucumber`
@@ -36,7 +36,7 @@ Feature: Mock the HOME variable
     Feature: Home Variable
       @mocked-home-directory
       Scenario: Run command
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the output should match %r<HOME:.*tmp/aruba$>
     """
     When I run `cucumber`
@@ -55,7 +55,7 @@ Feature: Mock the HOME variable
     """
     Feature: Home Variable
       Scenario: Run command
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the output should match %r<HOME:.*tmp/aruba$>
     """
     When I run `cucumber`

data/features/{steps → 03_testing_frameworks/cucumber/steps}/environment/prepend_environment_variable.feature

@@ -8,7 +8,7 @@ Feature: Prepend environment variable via "cucumber"-step
 
   Background:
     Given I use the fixture "cli-app"
-    And an executable named "bin/cli" with:
+    And an executable named "bin/aruba-test-cli" with:
     """
     #!/bin/bash
 
@@ -27,7 +27,7 @@ Feature: Prepend environment variable via "cucumber"-step
         Given I prepend the values to the environment variables:
           | variable           | value      |
           | LONG_LONG_VARIABLE | long_value |
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the output should contain:
         \"\"\"
         long_value1
@@ -42,7 +42,7 @@ Feature: Prepend environment variable via "cucumber"-step
     Feature: Environment Variable
       Scenario: Run command
         Given I prepend "long_value" to the environment variable "LONG_LONG_VARIABLE"
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the output should contain:
         \"\"\"
         long_value1

data/features/{steps → 03_testing_frameworks/cucumber/steps}/environment/set_environment_variable.feature

@@ -9,7 +9,7 @@ Feature: Set environment variable via "cucumber"-step
 
   Background:
     Given I use the fixture "cli-app"
-    And an executable named "bin/cli" with:
+    And an executable named "bin/aruba-test-cli" with:
     """
     #!/bin/bash
 
@@ -24,7 +24,7 @@ Feature: Set environment variable via "cucumber"-step
         Given I set the environment variables to:
           | variable           | value      |
           | LONG_LONG_VARIABLE | long_value |
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the output should contain:
         \"\"\"
         long_value
@@ -39,7 +39,7 @@ Feature: Set environment variable via "cucumber"-step
     Feature: Environment Variable
       Scenario: Run command
         Given I set the environment variable "LONG_LONG_VARIABLE" to "long_value"
-        When I run `cli`
+        When I run `aruba-test-cli`
         Then the output should contain:
         \"\"\"
         long_value

data/features/{steps/filesystem/file_content.feature → 03_testing_frameworks/cucumber/steps/filesystem/check_file_content.feature}

@@ -3,6 +3,63 @@ Feature: Check file content
   Background:
     Given I use a fixture named "cli-app"
 
+  Scenario: Check file contents with plain text
+    Given a file named "features/non-existence.feature" with:
+    """
+    Feature: Check
+      Scenario: Check
+        Given a file named "foo" with:
+        \"\"\"
+        hello world
+        \"\"\"
+        Then the file "foo" should contain "hello world"
+        And the file "foo" should not contain "HELLO WORLD"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Check file contents with regular expression
+    Given a file named "features/non-existence.feature" with:
+    """
+    Feature: Check
+      Background:
+        Given a file named "foo" with:
+        \"\"\"
+        hello world
+        \"\"\"
+
+      Scenario: Check #1
+        Then the file "foo" should match /hel.o world/
+        And the file "foo" should not match /HELLO WORLD/
+
+      Scenario: Check #2
+        Then the file "foo" should match %r<hel.o world>
+        And the file "foo" should not match %r<HELLO WORLD>
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario:  Check file contents with cucumber doc string
+    Given a file named "features/non-existence.feature" with:
+    """
+    Feature: Existence
+      Scenario: Existence
+        Given a file named "foo" with:
+        \"\"\"
+        foo
+        bar
+        baz
+        foobar
+        \"\"\"
+        Then the file "foo" should contain:
+        \"\"\"
+        bar
+        baz
+        \"\"\"
+        """
+    When I run `cucumber`
+    Then the features should all pass
+
   Scenario: Existing file having content
     Given a file named "features/file_content.feature" with:
     """

data/features/{steps/filesystem/move.feature → 03_testing_frameworks/cucumber/steps/filesystem/move_file_or_directory.feature}

@@ -42,4 +42,3 @@ Feature: Move file or directory
     """
     When I run `cucumber`
     Then the features should all pass
-

data/features/{hooks/after/command.feature → 03_testing_frameworks/rspec/hooks/define_after_hook_for_commands.feature}

@@ -17,10 +17,8 @@ Feature: After command hooks
     Given I use a fixture named "cli-app"
 
   Scenario: Run a simple command with an "after(:command)"-hook
-    Given a file named "spec/support/hooks.rb" with:
+    Given a file named "spec/support/aruba_config.rb" with:
     """
-    require 'aruba'
-
     Aruba.configure do |config|
       config.after :command do |cmd|
         puts "after the run of `#{cmd.commandline}`"
@@ -43,4 +41,3 @@ Feature: After command hooks
     """
     after the run of `echo running`
     """
-

data/features/{hooks/before/command.feature → 03_testing_frameworks/rspec/hooks/define_before_hook_for_commands.feature}

@@ -19,10 +19,8 @@ Feature: before_cmd hooks
     Given I use a fixture named "cli-app"
 
   Scenario: Run a simple command with a "before(:command)"-hook
-    Given a file named "spec/support/hooks.rb" with:
+    Given a file named "spec/support/aruba_config.rb" with:
     """
-    require 'aruba'
-
     Aruba.configure do |config|
       config.before :command do |cmd|
         puts "before the run of `#{cmd.commandline}`"
@@ -49,8 +47,6 @@ Feature: before_cmd hooks
   Scenario: Run a simple command with a "before(:cmd)"-hook (deprecated)
     Given a file named "spec/support/hooks.rb" with:
     """
-    require 'aruba'
-
     Aruba.configure do |config|
       config.before :cmd do |cmd|
         puts "before the run of `#{cmd}`"

data/features/{rspec/integration.feature → 03_testing_frameworks/rspec/setup_aruba_for_rspec.feature}

@@ -9,17 +9,17 @@ Feature: Getting started with RSpec and aruba
     `spec_helper.rb`. After that you only need to flag your tests with `type:
     :aruba` and some things are set up for.
 
-    The simple integration adds some `before(:each)`-hooks for you:
+    The simple integration adds some `before(:each)` hooks for you:
 
       \* Setup Aruba Test directory
       \* Clear environment (ENV)
-      \* Make HOME-variable configarable via `arub.config.home_directory`
-      \* Configure `aruba` via `RSpec`-metadata
-      \* Activate announcers based on `RSpec`-metadata
+      \* Make HOME variable configurable via `arub.config.home_directory`
+      \* Configure `aruba` via `RSpec` metadata
+      \* Activate announcers based on `RSpec` metadata
 
-    Be careful, if you are going to use a `before(:all)`-hook to set up
-    files/directories. Those will be deleted by the `setup_aruba`-call within
-    the `before(:each)`-hook. Look for some custom integration further down the
+    Be careful, if you are going to use a `before(:all)` hook to set up
+    files/directories. Those will be deleted by the `setup_aruba` call within
+    the `before(:each)` hook. Look for some custom integration further down the
     documentation for a solution.
 
     Given a file named "spec/spec_helper.rb" with:
@@ -82,18 +82,18 @@ Feature: Getting started with RSpec and aruba
     When I run `rspec`
     Then the specs should all pass
 
-  Scenario: Custom Integration using before(:all)-hook
+  Scenario: Custom Integration using before(:all) hook
 
-    You can even use `aruba` within a `before(:all)`-hook. But again, make sure
+    You can even use `aruba` within a `before(:all)` hook. But again, make sure
     that `setup_aruba` is run before you use any method of `aruba`. Using
-    `setup_aruba` both in `before(:all)`- and `before(:each)`-hook is not
-    possible and therefor not supported:
-
-    Running `setup_aruba` removes `tmp/aruba`, creates a new one `tmp/aruba`
-    and make it the working directory. Running it within a `before(:all)`-hook,
-    run some `aruba`-method and then run `setup_arub` again within a
-    `before(:each)`-hook, will remove the files/directories created within the
-    `before(:all)`-hook.
+    `setup_aruba` both in a `before(:all)` and a `before(:each)` hook is not
+    possible and therefore not supported:
+
+    Running `setup_aruba` removes `tmp/aruba`, creates a new `tmp/aruba`, and
+    makes that the working directory. Running it within a `before(:all)` hook,
+    running some `aruba` method and, then running `setup_aruba` again within a
+    `before(:each)` hook, will remove the files and directories created within
+    the `before(:all)` hook.
 
     Given a file named "spec/spec_helper.rb" with:
     """

data/features/{api/command/which.feature → 04_aruba_api/command/find_command_in_PATH.feature}

@@ -7,7 +7,7 @@ Feature: Get path to command
     Given I use a fixture named "cli-app"
 
   Scenario: Existing executable
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/bin/bash
     exit 0
@@ -17,20 +17,20 @@ Feature: Get path to command
     require 'spec_helper'
 
     RSpec.describe 'Find path for command', :type => :aruba do
-      it { expect(which('cli')).to match %r{tmp/aruba/cli-app/bin/cli} }
+      it { expect(which('aruba-test-cli')).to match %r{tmp/aruba/cli-app/bin/aruba-test-cli} }
     end
     """
     When I run `rspec`
     Then the specs should all pass
 
   Scenario: Non-existing executable
-    Given a file named "bin/cli" does not exist
+    Given a file named "bin/aruba-test-cli" does not exist
     And a file named "spec/which_spec.rb" with:
     """ruby
     require 'spec_helper'
 
     RSpec.describe 'Find path for command', :type => :aruba do
-      it { expect(which('cli')).to be_nil }
+      it { expect(which('aruba-test-cli')).to be_nil }
     end
     """
     When I run `rspec`

data/features/{api/command/stderr.feature → 04_aruba_api/command/read_stderr_of_command.feature}

@@ -5,10 +5,10 @@ Feature: Access STDERR of command
 
   Background:
     Given I use a fixture named "cli-app"
-    And the default aruba io wait timeout is 1 seconds
+    And the default aruba io wait timeout is 0.1 seconds
 
   Scenario: Existing executable
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/bin/bash
     echo 'Hello, Aruba!' >&2
@@ -18,7 +18,7 @@ Feature: Access STDERR of command
     require 'spec_helper'
 
     RSpec.describe 'Run command', :type => :aruba do
-      before(:each) { run_command('cli') }
+      before(:each) { run_command('aruba-test-cli') }
       before(:each) { stop_all_commands }
       it { expect(last_command_started.stderr).to start_with  'Hello' }
     end
@@ -26,19 +26,19 @@ Feature: Access STDERR of command
     When I run `rspec`
     Then the specs should all pass
 
-  Scenario: Waiting for output to "appear" after 2 seconds
-    Given an executable named "bin/cli" with:
+  Scenario: Waiting for output to appear
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/bin/bash
-    sleep 1
+    sleep 0.1
     echo 'Hello, Aruba' >&2
     """
     And a file named "spec/run_spec.rb" with:
     """ruby
     require 'spec_helper'
 
-    RSpec.describe 'Run command', :type => :aruba, :io_wait_timeout => 2 do
-      before(:each) { run_command('cli') }
+    RSpec.describe 'Run command', :type => :aruba, :io_wait_timeout => 0.2 do
+      before(:each) { run_command('aruba-test-cli') }
       it { expect(last_command_started.stderr).to start_with 'Hello' }
     end
     """

data/features/{api/command/stdout.feature → 04_aruba_api/command/read_stdout_of_command.feature}

@@ -8,7 +8,7 @@ Feature: Access STDOUT of command
     And the default aruba io wait timeout is 1 seconds
 
   Scenario: Existing executable
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/bin/bash
     echo 'Hello, Aruba!'
@@ -18,7 +18,7 @@ Feature: Access STDOUT of command
     require 'spec_helper'
 
     RSpec.describe 'Run command', :type => :aruba do
-      before(:each) { run_command('cli') }
+      before(:each) { run_command('aruba-test-cli') }
       before(:each) { stop_all_commands }
       it { expect(last_command_started.stdout).to start_with  'Hello' }
     end
@@ -26,19 +26,19 @@ Feature: Access STDOUT of command
     When I run `rspec`
     Then the specs should all pass
 
-  Scenario: Waiting for output to "appear" after 2 seconds
-    Given an executable named "bin/cli" with:
+  Scenario: Waiting for output to appear
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/bin/bash
-    sleep 1
+    sleep 0.1
     echo 'Hello, Aruba'
     """
     And a file named "spec/run_spec.rb" with:
     """ruby
     require 'spec_helper'
 
-    RSpec.describe 'Run command', :type => :aruba, :io_wait_timeout => 2 do
-      before(:each) { run_command('cli') }
+    RSpec.describe 'Run command', :type => :aruba, :io_wait_timeout => 0.2 do
+      before(:each) { run_command('aruba-test-cli') }
       it { expect(last_command_started.stdout).to start_with 'Hello' }
     end
     """

data/features/{api/command/run.feature → 04_aruba_api/command/run_command.feature}

@@ -1,6 +1,6 @@
 Feature: Run command
 
-  To run a command use the `#run_command`-method. There are some configuration options
+  To run a command use the `#run_command` method. There are some configuration options
   which are relevant here:
 
   - `startup_wait_time`:
@@ -24,7 +24,7 @@ Feature: Run command
     Given I use a fixture named "cli-app"
 
   Scenario: Existing executable
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/bin/bash
     exit 0
@@ -34,7 +34,7 @@ Feature: Run command
     require 'spec_helper'
 
     RSpec.describe 'Run command', :type => :aruba do
-      before(:each) { run_command('cli') }
+      before(:each) { run_command('aruba-test-cli') }
       it { expect(last_command_started).to be_successfully_executed }
     end
     """
@@ -42,7 +42,7 @@ Feature: Run command
     Then the specs should all pass
 
   Scenario: Relative path to executable
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/bin/bash
     exit 0
@@ -52,7 +52,7 @@ Feature: Run command
     require 'spec_helper'
 
     RSpec.describe 'Run command', :type => :aruba do
-      before(:each) { run_command('bin/cli') }
+      before(:each) { run_command('bin/aruba-test-cli') }
       it { expect(last_command_started).to be_successfully_executed }
     end
     """
@@ -60,13 +60,13 @@ Feature: Run command
     Then the specs should all pass
 
   Scenario: Non-existing executable
-    Given a file named "bin/cli" does not exist
+    Given a file named "bin/aruba-test-cli" does not exist
     And a file named "spec/run_spec.rb" with:
     """ruby
     require 'spec_helper'
 
     RSpec.describe 'Find path for command', :type => :aruba do
-      it { expect { run_command('cli') }.to raise_error Aruba::LaunchError, /Command "cli" not found in PATH-variable/ }
+      it { expect { run_command('aruba-test-cli') }.to raise_error Aruba::LaunchError, /Command "aruba-test-cli" not found in PATH-variable/ }
     end
     """
     When I run `rspec`
@@ -79,12 +79,12 @@ Feature: Run command
     Otherwise methods like `#send_signal` don't work since they require the
     command to be running and have setup it's signal handler.
 
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/usr/bin/env bash
- 
+
     function initialize_script {
-      sleep 2
+      sleep 0.2
     }
 
     function do_some_work {
@@ -105,20 +105,25 @@ Feature: Run command
     initialize_script
     do_some_work
 
-    while [ true ]; do sleep 1; done
+    while [ true ]; do sleep 0.1; done
     """
     And a file named "spec/run_spec.rb" with:
     """ruby
     require 'spec_helper'
 
-    RSpec.describe 'Run command', :type => :aruba, :exit_timeout => 1, :startup_wait_time => 2 do
-      before(:each) { run_command('cli') }
-      before(:each) { last_command_started.send_signal 'HUP' }
-
-      it { expect(last_command_started).to be_successfully_executed }
-      it { expect(last_command_started).to have_output /Hello, Aruba is working/ }
-      it { expect(last_command_started).to have_output /Hello, Aruba here/ }
-
+    RSpec.describe 'Run command', :type => :aruba, :exit_timeout => 0.1, :startup_wait_time => 0.2 do
+      before do
+        run_command('aruba-test-cli')
+        last_command_started.send_signal 'HUP'
+      end
+
+      it 'runs the command with the expected results' do
+        aggregate_failures do
+          expect(last_command_started).to be_successfully_executed
+          expect(last_command_started).to have_output /Hello, Aruba is working/
+          expect(last_command_started).to have_output /Hello, Aruba here/
+        end
+      end
     end
     """
     When I run `rspec`
@@ -129,12 +134,12 @@ Feature: Run command
     If you have got a "long running" command, you should consider using the
     `exit_timeout`-option.
 
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/usr/bin/env bash
 
     function do_some_work {
-      sleep 2
+      sleep 0.2
       echo "Hello, Aruba here"
     }
 
@@ -144,11 +149,15 @@ Feature: Run command
     """ruby
     require 'spec_helper'
 
-    RSpec.describe 'Run command', :type => :aruba, :exit_timeout => 3 do
-      before(:each) { run_command('cli') }
+    RSpec.describe 'Run command', :type => :aruba, :exit_timeout => 0.3 do
+      before { run_command('aruba-test-cli') }
 
-      it { expect(last_command_started).to be_successfully_executed }
-      it { expect(last_command_started).to have_output /Hello, Aruba here/ }
+      it 'runs the command with the expected results' do
+        aggregate_failures do
+          expect(last_command_started).to be_successfully_executed
+          expect(last_command_started).to have_output /Hello, Aruba here/
+        end
+      end
     end
     """
     When I run `rspec`
@@ -159,7 +168,7 @@ Feature: Run command
     If you commands with a long and short startup phases, you should consider
     using the `startup_wait_time`-option local to the `#run_command`-call.
 
-    Given an executable named "bin/cli1" with:
+    Given an executable named "bin/aruba-test-cli1" with:
     """bash
     #!/usr/bin/env bash
  
@@ -187,7 +196,7 @@ Feature: Run command
 
     while [ true ]; do sleep 0.2; done
     """
-    And an executable named "bin/cli2" with:
+    And an executable named "bin/aruba-test-cli2" with:
     """bash
     #!/usr/bin/env bash
 
@@ -220,8 +229,8 @@ Feature: Run command
     require 'spec_helper'
 
     RSpec.describe 'Run command', :type => :aruba, :exit_timeout => 1 do
-      before(:each) { run_command('cli1', 3, 0.1, 'TERM', 2) }
-      before(:each) { run_command('cli2', 3, 0.1, 'TERM', 1) }
+      before(:each) { run_command('aruba-test-cli1', 3, 0.1, 'TERM', 2) }
+      before(:each) { run_command('aruba-test-cli2', 3, 0.1, 'TERM', 1) }
       before(:each) { last_command_started.send_signal 'HUP' }
 
       it { expect(last_command_started).to be_successfully_executed }
@@ -238,7 +247,7 @@ Feature: Run command
     If you commands with a long and short startup phases, you should consider
     using the `startup_wait_time`-option local to the `#run_command`-call.
 
-    Given an executable named "bin/cli1" with:
+    Given an executable named "bin/aruba-test-cli1" with:
     """bash
     #!/usr/bin/env bash
  
@@ -266,7 +275,7 @@ Feature: Run command
 
     while [ true ]; do sleep 0.2; done
     """
-    And an executable named "bin/cli2" with:
+    And an executable named "bin/aruba-test-cli2" with:
     """bash
     #!/usr/bin/env bash
 
@@ -299,8 +308,8 @@ Feature: Run command
     require 'spec_helper'
 
     RSpec.describe 'Run command', :type => :aruba, :exit_timeout => 1 do
-      before(:each) { run_command('cli1', :startup_wait_time => 2) }
-      before(:each) { run_command('cli2', :startup_wait_time => 1) }
+      before(:each) { run_command('aruba-test-cli1', :startup_wait_time => 2) }
+      before(:each) { run_command('aruba-test-cli2', :startup_wait_time => 1) }
       before(:each) { last_command_started.send_signal 'HUP' }
 
       it { expect(last_command_started).to be_successfully_executed }
@@ -317,7 +326,7 @@ Feature: Run command
     If need to mix "long running" and "short running" commands, you should consider using the
     `exit_timeout`-option local to the `#run_command`-method.
 
-    Given an executable named "bin/cli1" with:
+    Given an executable named "bin/aruba-test-cli1" with:
     """bash
     #!/usr/bin/env bash
 
@@ -328,7 +337,7 @@ Feature: Run command
 
     do_some_work
     """
-    And an executable named "bin/cli2" with:
+    And an executable named "bin/aruba-test-cli2" with:
     """bash
     #!/usr/bin/env bash
 
@@ -343,8 +352,8 @@ Feature: Run command
     require 'spec_helper'
 
     RSpec.describe 'Run command', :type => :aruba do
-      before(:each) { run_command('cli1', 3) }
-      before(:each) { run_command('cli2', 1) }
+      before(:each) { run_command('aruba-test-cli1', 3) }
+      before(:each) { run_command('aruba-test-cli2', 1) }
 
       it { expect(last_command_started).to be_successfully_executed }
       it { expect(last_command_started).to have_output /Hello, Aruba here/ }
@@ -358,7 +367,7 @@ Feature: Run command
     If need to mix "long running" and "short running" commands, you should consider using the
     `exit_timeout`-option local to the `#run_command`-method.
 
-    Given an executable named "bin/cli1" with:
+    Given an executable named "bin/aruba-test-cli1" with:
     """bash
     #!/usr/bin/env bash
 
@@ -369,7 +378,7 @@ Feature: Run command
 
     do_some_work
     """
-    And an executable named "bin/cli2" with:
+    And an executable named "bin/aruba-test-cli2" with:
     """bash
     #!/usr/bin/env bash
 
@@ -384,8 +393,8 @@ Feature: Run command
     require 'spec_helper'
 
     RSpec.describe 'Run command', :type => :aruba do
-      before(:each) { run_command('cli1', :exit_timeout => 3) }
-      before(:each) { run_command('cli2', :exit_timeout => 1) }
+      before(:each) { run_command('aruba-test-cli1', :exit_timeout => 3) }
+      before(:each) { run_command('aruba-test-cli2', :exit_timeout => 1) }
 
       it { expect(last_command_started).to be_successfully_executed }
       it { expect(last_command_started).to have_output /Hello, Aruba here/ }
@@ -395,7 +404,7 @@ Feature: Run command
     Then the specs should all pass
 
   Scenario: Starting command twice fails
-    Given an executable named "bin/cli" with:
+    Given an executable named "bin/aruba-test-cli" with:
     """bash
     #!/bin/bash
     exit 0
@@ -405,8 +414,8 @@ Feature: Run command
     require 'spec_helper'
 
     RSpec.describe 'Run command', :type => :aruba do
-      before(:each) { run_command('cli') }
-      let!(:found_command) { find_command('cli') }
+      before(:each) { run_command('aruba-test-cli') }
+      let!(:found_command) { find_command('aruba-test-cli') }
       it { expect { found_command.start }.to raise_error Aruba::CommandAlreadyStartedError }
     end
     """