aruba-win-fix 0.14.2

data/features/api/text/unescape_text.feature

@@ -0,0 +1,127 @@
+Feature: Unescape special characters in text
+
+  If have got some text include \n, \t and the like and need them to become
+  special characters again, you can use the `#unescape_text`-method for this.
+
+  Background:
+    Given I use a fixture named "cli-app"
+
+  Scenario: Output contains \n
+    Given an executable named "bin/cli" with:
+    """
+    #!/bin/bash
+    echo -n 'text\ntext'
+    """
+    And a file named "spec/unescape_text_spec.rb" with:
+    """
+    require 'spec_helper'
+
+    RSpec.describe 'Run command', :type => :aruba do
+      before(:each) { run('cli') }
+      before(:each) { stop_all_commands }
+
+      it { expect(unescape_text(last_command.output)).to eq "text\ntext" }
+    end
+    """
+    When I run `rspec`
+    Then the specs should all pass
+
+  Scenario: Output contains \e
+    Given an executable named "bin/cli" with:
+    """
+    #!/bin/bash
+    echo -n 'text\etext'
+    """
+    And a file named "spec/unescape_text_spec.rb" with:
+    """
+    require 'spec_helper'
+
+    RSpec.describe 'Run command', :type => :aruba do
+      before(:each) { run('cli') }
+      before(:each) { stop_all_commands }
+
+      it { expect(unescape_text(last_command.output)).to eq "texttext" }
+    end
+    """
+    When I run `rspec`
+    Then the specs should all pass
+
+  Scenario: Output contains \"
+    Given an executable named "bin/cli" with:
+    """
+    #!/bin/bash
+    echo -n 'text\"text'
+    """
+    And a file named "spec/unescape_text_spec.rb" with:
+    """
+    require 'spec_helper'
+
+    RSpec.describe 'Run command', :type => :aruba do
+      before(:each) { run('cli') }
+      before(:each) { stop_all_commands }
+
+      it { expect(unescape_text(last_command.output)).to eq "text\"text" }
+    end
+    """
+    When I run `rspec`
+    Then the specs should all pass
+
+  Scenario: Output contains \033
+    Given an executable named "bin/cli" with:
+    """
+    #!/bin/bash
+    echo -n 'text\033text'
+    """
+    And a file named "spec/unescape_text_spec.rb" with:
+    """
+    require 'spec_helper'
+
+    RSpec.describe 'Run command', :type => :aruba do
+      before(:each) { run('cli') }
+      before(:each) { stop_all_commands }
+
+      it { expect(unescape_text(last_command.output)).to eq "texttext" }
+    end
+    """
+    When I run `rspec`
+    Then the specs should all pass
+
+  Scenario: Output contains \017
+    Given an executable named "bin/cli" with:
+    """
+    #!/bin/bash
+    echo -n 'text\017text'
+    """
+    And a file named "spec/unescape_text_spec.rb" with:
+    """
+    require 'spec_helper'
+
+    RSpec.describe 'Run command', :type => :aruba do
+      before(:each) { run('cli') }
+      before(:each) { stop_all_commands }
+
+      it { expect(unescape_text(last_command.output)).to eq "texttext" }
+    end
+    """
+    When I run `rspec`
+    Then the specs should all pass
+
+  Scenario: Output contains \016
+    Given an executable named "bin/cli" with:
+    """
+    #!/bin/bash
+    echo -n 'text\016text'
+    """
+    And a file named "spec/unescape_text_spec.rb" with:
+    """
+    require 'spec_helper'
+
+    RSpec.describe 'Run command', :type => :aruba do
+      before(:each) { run('cli') }
+      before(:each) { stop_all_commands }
+
+      it { expect(unescape_text(last_command.output)).to eq "texttext" }
+    end
+    """
+    When I run `rspec`
+    Then the specs should all pass

data/features/cli/console.feature

@@ -0,0 +1,52 @@
+Feature: Aruba Console
+
+  Background:
+    Given a mocked home directory
+
+  Scenario: Start console
+    Given I run `aruba console` interactively
+    When I close the stdin stream
+    Then the output should contain:
+    """
+    aruba:001:0>
+    """
+
+  @unsupported-on-platform-java
+  Scenario: Show help
+    Given I run `aruba console` interactively
+    And I type "aruba_help"
+    When I close the stdin stream
+    Then the output should contain:
+    """
+    Version:
+    """
+    And the output should contain:
+    """
+    Issue Tracker:
+    """
+    And the output should contain:
+    """
+    Documentation:
+    """
+
+  @unsupported-on-platform-java
+  Scenario: Show methods
+    Given I run `aruba console` interactively
+    And I type "aruba_methods"
+    When I close the stdin stream
+    Then the output should contain:
+    """
+    Methods:
+    """
+    And the output should contain:
+    """
+    * setup_aruba
+    """
+
+  @unsupported-on-platform-java
+  Scenario: Has history
+    Given I run `aruba console` interactively
+    And I type "aruba_methods"
+    And I type "exit"
+    When I close the stdin stream
+    Then the file "~/.aruba_history" should exist

data/features/cli/init.feature

@@ -0,0 +1,79 @@
+Feature: Initialize project with aruba
+
+  To add `aruba` to your project you can use the `aruba init`-command.
+
+  Background:
+    Given I use the fixture "empty-app"
+
+  Scenario: Create files for RSpec
+    When I successfully run `aruba init --test-framework rspec`
+    Then the following files should exist:
+      | spec/spec_helper.rb |
+    And the file "spec/support/aruba.rb" should contain:
+    """
+    require 'aruba/rspec'
+    """
+    And the file "Gemfile" should contain:
+    """
+    gem 'aruba'
+    """
+    When I successfully run `rspec`
+    Then the output should contain:
+    """
+    0 examples, 0 failures
+    """
+
+  Scenario: Create files for Cucumber
+    When I successfully run `aruba init --test-framework cucumber`
+    Then the file "features/support/aruba.rb" should contain:
+    """
+    require 'aruba/cucumber'
+    """
+    And the file "Gemfile" should contain:
+    """
+    gem 'aruba'
+    """
+    When I successfully run `cucumber`
+    Then the output should contain:
+    """
+    0 scenarios
+    0 steps
+    """
+
+  Scenario: Create files for Cucumber (Default)
+    When I successfully run `aruba init`
+    Then the file "features/support/aruba.rb" should contain:
+    """
+    require 'aruba/cucumber'
+    """
+    And the file "Gemfile" should contain:
+    """
+    gem 'aruba'
+    """
+    When I successfully run `cucumber`
+    Then the output should contain:
+    """
+    0 scenarios
+    0 steps
+    """
+
+  Scenario: Create files for Minitest
+    When I successfully run `aruba init --test-framework minitest`
+    Then the following files should exist:
+      | test/test_helper.rb |
+    And the file "Gemfile" should contain:
+    """
+    gem 'aruba'
+    """
+    When I successfully run `ruby -Ilib:test test/use_aruba_with_minitest.rb`
+    Then the output should contain:
+    """
+    0 runs, 0 assertions, 0 failures, 0 errors, 0 skips
+    """
+
+  Scenario: Unknown Test Framework
+    When I run `aruba init --test-framework unknown`
+    Then the output should contain:
+    """
+    got unknown
+    """

data/features/configuration/activate_announcer_on_command_failure.feature

@@ -0,0 +1,38 @@
+Feature: Configure announcer activation on command failure
+
+  As a developer
+  I want to configure which announcers should get activated on command failure
+  In order to understand what caused a command to fail
+
+  Background:
+    Given I use the fixture "cli-app"
+
+  Scenario: Default value
+    Given a file named "features/support/aruba.rb" with:
+    """ruby
+    Aruba.configure do |config|
+      puts %(The default value is "#{config.activate_announcer_on_command_failure.inspect}")
+    end
+    """
+    When I successfully run `cucumber`
+    Then the output should contain:
+    """ruby
+    The default value is "[]"
+    """
+
+  Scenario: Modify value
+    Given a file named "features/support/aruba.rb" with:
+    """ruby
+    Aruba.configure do |config|
+      config.activate_announcer_on_command_failure = [:foo, :bar]
+    end
+
+    Aruba.configure do |config|
+      puts %(The value is "#{config.activate_announcer_on_command_failure.inspect}")
+    end
+    """
+    Then I successfully run `cucumber`
+    Then the output should contain:
+    """
+    The value is "[:foo, :bar]"
+    """

data/features/configuration/command_runtime_environment.feature

@@ -0,0 +1,129 @@
+Feature: Define default process environment
+  Say you want to have a default set of environment variables, then use this
+  code.
+
+  ~~~ruby
+  Aruba.configure do |config|
+    config.command_runtime_environment = { 'MY_VARIABLE' => 'x' }
+  end
+  ~~~
+
+  This can be changed via `#set_environment_variable`,
+  `#append_environment_variable`, `#delete_environment_variable` or
+  `#prepend_environment_variable`.
+
+  Background:
+    Given I use the fixture "cli-app"
+
+  Scenario: Overwrite existing variable with new default value
+    Given a file named "spec/environment_spec.rb" with:
+    """ruby
+    require 'spec_helper'
+
+    ENV['LONG_LONG_VARIABLE'] = 'y'
+
+    Aruba.configure do |config|
+      config.command_runtime_environment = { 'LONG_LONG_VARIABLE' => 'x' } 
+    end
+
+    RSpec.describe 'Environment command', :type => :aruba do
+      before(:each) { run('env') }
+      before(:each) { stop_all_commands }
+
+      it { expect(last_command_started.output).to include 'LONG_LONG_VARIABLE=x' }
+    end
+    """
+    When I run `rspec`
+    Then the specs should all pass
+
+  Scenario: Overwrite default value for variable
+    Given a file named "spec/environment_spec.rb" with:
+    """ruby
+    require 'spec_helper'
+
+    ENV['LONG_LONG_VARIABLE'] = 'y'
+
+    Aruba.configure do |config|
+      config.command_runtime_environment = { 'LONG_LONG_VARIABLE' => 'x' } 
+    end
+
+    RSpec.describe 'Environment command', :type => :aruba do
+      before(:each) { set_environment_variable 'LONG_LONG_VARIABLE', 'z' }
+
+      before(:each) { run('env') }
+      before(:each) { stop_all_commands }
+
+      it { expect(last_command_started.output).to include 'LONG_LONG_VARIABLE=z' }
+    end
+    """
+    When I run `rspec`
+    Then the specs should all pass
+
+  Scenario: Append value to default value
+    Given a file named "spec/environment_spec.rb" with:
+    """ruby
+    require 'spec_helper'
+
+    ENV['LONG_LONG_VARIABLE'] = 'y'
+
+    Aruba.configure do |config|
+      config.command_runtime_environment = { 'LONG_LONG_VARIABLE' => 'x' } 
+    end
+
+    RSpec.describe 'Environment command', :type => :aruba do
+      before(:each) { append_environment_variable 'LONG_LONG_VARIABLE', 'z' }
+
+      before(:each) { run('env') }
+      before(:each) { stop_all_commands }
+
+      it { expect(last_command_started.output).to include 'LONG_LONG_VARIABLE=xz' }
+    end
+    """
+    When I run `rspec`
+    Then the specs should all pass
+
+  Scenario: Prepend value
+    Given a file named "spec/environment_spec.rb" with:
+    """ruby
+    require 'spec_helper'
+
+    ENV['LONG_LONG_VARIABLE'] = 'y'
+
+    Aruba.configure do |config|
+      config.command_runtime_environment = { 'LONG_LONG_VARIABLE' => 'x' } 
+    end
+
+    RSpec.describe 'Environment command', :type => :aruba do
+      before(:each) { prepend_environment_variable 'LONG_LONG_VARIABLE', 'z' }
+
+      before(:each) { run('env') }
+      before(:each) { stop_all_commands }
+
+      it { expect(last_command_started.output).to include 'LONG_LONG_VARIABLE=zx' }
+    end
+    """
+    When I run `rspec`
+    Then the specs should all pass
+
+  Scenario: Remove variable from default set of variables
+    Given a file named "spec/environment_spec.rb" with:
+    """ruby
+    require 'spec_helper'
+
+    ENV['LONG_LONG_VARIABLE'] = 'y'
+
+    Aruba.configure do |config|
+      config.command_runtime_environment = { 'LONG_LONG_VARIABLE' => 'x' } 
+    end
+
+    RSpec.describe 'Environment command', :type => :aruba do
+      before(:each) { delete_environment_variable 'LONG_LONG_VARIABLE' }
+
+      before(:each) { run('env') }
+      before(:each) { stop_all_commands }
+
+      it { expect(last_command_started.output).not_to include 'LONG_LONG_VARIABLE' }
+    end
+    """
+    When I run `rspec`
+    Then the specs should all pass

data/features/configuration/console_history_file.feature

@@ -0,0 +1,38 @@
+Feature: Configure the aruba console history file
+
+  As a developer
+  I want to configure the history file of aruba console
+  In order to have a better isolation of tests
+
+  Background:
+    Given I use the fixture "cli-app"
+
+  Scenario: Default value
+    Given a file named "features/support/aruba.rb" with:
+    """
+    Aruba.configure do |config|
+      puts %(The default value is "#{config.console_history_file}")
+    end
+    """
+    When I successfully run `cucumber`
+    Then the output should contain:
+    """
+    The default value is "~/.aruba_history"
+    """
+
+  Scenario: Set some value
+    Given a file named "features/support/aruba.rb" with:
+    """
+    Aruba.configure do |config|
+      config.console_history_file = '~/.config/aruba/history.txt'
+    end
+
+    Aruba.configure do |config|
+      puts %(The value is "#{config.console_history_file}")
+    end
+    """
+    Then I successfully run `cucumber`
+    Then the output should contain:
+    """
+    The value is "~/.config/aruba/history.txt"
+    """