aruba 0.14.14 → 1.0.0.pre.alpha.1

data/features/03_testing_frameworks/cucumber/steps/filesystem/overwrite_file.feature

@@ -1,72 +0,0 @@
-Feature: Overwrite a file
-
-  As a user of aruba
-  I want to overwrite a file
-
-  Background:
-    Given I use a fixture named "cli-app"
-
-  Scenario: Overwrite an existing file
-    Given a file named "features/create_file.feature" with:
-    """
-    Feature: Overwrite file
-      Scenario: Overwrite file
-        Given a file named "file1.txt" with:
-        \"\"\"
-        Hello World
-        \"\"\"
-        And a file named "file2.txt" with:
-        \"\"\"
-        Hello World
-        \"\"\"
-        And a file named "file3.txt" with:
-        \"\"\"
-        Hello World
-        \"\"\"
-        When I overwrite "file1.txt" with:
-        \"\"\"
-        Hello Universe
-        \"\"\"
-        When I overwrite the file "file2.txt" with:
-        \"\"\"
-        Hello Universe
-        \"\"\"
-        When I overwrite a file named "file3.txt" with:
-        \"\"\"
-        Hello Universe
-        \"\"\"
-        Then the file named "file1.txt" should contain:
-        \"\"\"
-        Hello Universe
-        \"\"\"
-        And the file named "file2.txt" should contain:
-        \"\"\"
-        Hello Universe
-        \"\"\"
-        And the file named "file3.txt" should contain:
-        \"\"\"
-        Hello Universe
-        \"\"\"
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Overwrite a non-existing file
-    Given a file named "features/create_file.feature" with:
-    """
-    Feature: Overwrite file
-      Scenario: Overwrite file
-        When I overwrite "file1.txt" with:
-        \"\"\"
-        Hello Universe
-        \"\"\"
-        Then the file named "file1.txt" should contain:
-        \"\"\"
-        Hello Universe
-        \"\"\"
-    """
-    When I run `cucumber`
-    Then the features should not all pass with regex:
-    """
-    Expected [^ ]+ to be present
-    """

data/features/03_testing_frameworks/cucumber/steps/filesystem/remove_directory.feature

@@ -1,38 +0,0 @@
-Feature: Remove a directory
-
-  Background:
-    Given I use a fixture named "cli-app"
-
-  Scenario: Remove an existing directory
-    Given a file named "features/non-existence.feature" with:
-    """
-    Feature: Remove
-      Scenario: Remove
-        Given an empty directory named "foo"
-        When I remove the directory "foo"
-        Then the directory "foo" should not exist
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Remove an non-existing directory
-    Given a file named "features/non-existence.feature" with:
-    """
-    Feature: Remove
-      Scenario: Remove
-        When I remove the directory "foo"
-        Then the directory "foo" should not exist
-    """
-    When I run `cucumber`
-    Then the features should not pass
-
-  Scenario: Force remove an non-existing directory
-    Given a file named "features/non-existence.feature" with:
-    """
-    Feature: Remove
-      Scenario: Remove
-        When I remove the directory "foo" with full force
-        Then the directory "foo" should not exist
-    """
-    When I run `cucumber`
-    Then the features should all pass

data/features/03_testing_frameworks/cucumber/steps/filesystem/remove_file.feature

@@ -1,38 +0,0 @@
-Feature: Remove a file
-
-  Background:
-    Given I use a fixture named "cli-app"
-
-  Scenario: Remove an existing file
-    Given a file named "features/non-existence.feature" with:
-    """
-    Feature: Remove
-      Scenario: Remove
-        Given an empty file named "foo"
-        When I remove the file "foo"
-        Then the file "foo" should not exist
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Remove an non-existing file
-    Given a file named "features/non-existence.feature" with:
-    """
-    Feature: Remove
-      Scenario: Remove
-        When I remove the file "foo"
-        Then the file "foo" should not exist
-    """
-    When I run `cucumber`
-    Then the features should not pass
-
-  Scenario: Force remove an non-existing file
-    Given a file named "features/non-existence.feature" with:
-    """
-    Feature: Remove
-      Scenario: Remove
-        When I remove the file "foo" with full force
-        Then the file "foo" should not exist
-    """
-    When I run `cucumber`
-    Then the features should all pass

data/features/03_testing_frameworks/cucumber/steps/filesystem/use_fixtures_for_setup_test.feature

@@ -1,77 +0,0 @@
-Feature: Use a fixture
-
-  As a user of aruba
-  I want to use a fixture
-
-  Background:
-    Given I use a fixture named "cli-app"
-
-  Scenario: Use the fixture if fixtures directory is in root directory
-    Given a file named "features/use_fixtures.feature" with:
-    """
-    Feature: Use Fixture
-      Scenario: Use Fixture
-        Given I use a fixture named "my-app"
-        Then a file named "MY-APP-README.md" should exist
-    """
-    And a directory named "fixtures"
-    And a directory named "fixtures/my-app"
-    And an empty file named "fixtures/my-app/MY-APP-README.md"
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Use the fixture if fixtures directory is in features-directory
-    Given a file named "features/use_fixtures.feature" with:
-    """
-    Feature: Use Fixture
-      Scenario: Use Fixture
-        Given I use a fixture named "my-app"
-        Then a file named "MY-APP-README.md" should exist
-    """
-    And a directory named "features/fixtures"
-    And a directory named "features/fixtures/my-app"
-    And an empty file named "features/fixtures/my-app/MY-APP-README.md"
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Use the fixture if fixtures directory is in spec-directory
-    Given a file named "features/use_fixtures.feature" with:
-    """
-    Feature: Use Fixture
-      Scenario: Use Fixture
-        Given I use a fixture named "my-app"
-        Then a file named "MY-APP-README.md" should exist
-    """
-    And a directory named "spec/fixtures"
-    And a directory named "spec/fixtures/my-app"
-    And an empty file named "spec/fixtures/my-app/MY-APP-README.md"
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Use the fixture if fixtures directory is in test-directory
-    Given a file named "features/use_fixtures.feature" with:
-    """
-    Feature: Use Fixture
-      Scenario: Use Fixture
-        Given I use a fixture named "my-app"
-        Then a file named "MY-APP-README.md" should exist
-    """
-    And a directory named "test/fixtures"
-    And a directory named "test/fixtures/my-app"
-    And an empty file named "test/fixtures/my-app/MY-APP-README.md"
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Fails if fixture does not exist
-    Given a file named "features/use_fixtures.feature" with:
-    """
-    Feature: Use Fixture
-      Scenario: Use Fixture
-        Given I use a fixture named "my-app"
-    """
-    And a directory named "fixtures"
-    When I run `cucumber`
-    Then the features should not all pass with regex:
-    """
-    Fixture "my-app" does not exist in fixtures directory ".+/fixtures"
-    """

data/features/03_testing_frameworks/rspec/hooks/define_after_hook_for_commands.feature

@@ -1,43 +0,0 @@
-Feature: After command hooks
-
-  You can configure Aruba to run blocks of code after it has run
-  a command. The command will be passed to the block.
-
-  You can hook into Aruba's lifecycle just before it runs a command and after it has run the command:
-
-  ```ruby
-  Aruba.configure do |config|
-    config.after :command do |cmd|
-      puts "After the run of '#{cmd}'"
-    end
-  end
-  ```
-
-  Background:
-    Given I use a fixture named "cli-app"
-
-  Scenario: Run a simple command with an "after(:command)"-hook
-    Given a file named "spec/support/aruba_config.rb" with:
-    """
-    Aruba.configure do |config|
-      config.after :command do |cmd|
-        puts "after the run of `#{cmd.commandline}`"
-      end
-    end
-    """
-    And a file named "spec/hook_spec.rb" with:
-    """
-    require 'spec_helper'
-
-    RSpec.describe 'Hooks', :type => :aruba do
-      before(:each) { run_command_and_stop 'echo running' }
-
-      it { expect(last_command_started.stdout.chomp).to eq 'running' }
-    end
-    """
-    When I run `rspec`
-    Then the specs should all pass
-    And the output should contain:
-    """
-    after the run of `echo running`
-    """

data/features/03_testing_frameworks/rspec/hooks/define_before_hook_for_commands.feature

@@ -1,71 +0,0 @@
-Feature: before_cmd hooks
-
-  You can configure Aruba to run blocks of code before it runs
-  each command.
-
-  The command will be passed to the block.
-
-  You can hook into Aruba's lifecycle just before it runs a command and after it has run the command:
-
-  ```ruby
-  Aruba.configure do |config|
-    config.before :command do |cmd|
-      puts "About to run '#{cmd}'"
-    end
-  end
-  ```
-
-  Background:
-    Given I use a fixture named "cli-app"
-
-  Scenario: Run a simple command with a "before(:command)"-hook
-    Given a file named "spec/support/aruba_config.rb" with:
-    """
-    Aruba.configure do |config|
-      config.before :command do |cmd|
-        puts "before the run of `#{cmd.commandline}`"
-      end
-    end
-    """
-    And a file named "spec/hook_spec.rb" with:
-    """
-    require 'spec_helper'
-
-    RSpec.describe 'Hooks', :type => :aruba do
-      before(:each) { run_command_and_stop 'echo running' }
-
-      it { expect(last_command_started.stdout.chomp).to eq 'running' }
-    end
-    """
-    When I run `rspec`
-    Then the specs should all pass
-    And the output should contain:
-    """
-    before the run of `echo running`
-    """
-
-  Scenario: Run a simple command with a "before(:cmd)"-hook (deprecated)
-    Given a file named "spec/support/hooks.rb" with:
-    """
-    Aruba.configure do |config|
-      config.before :cmd do |cmd|
-        puts "before the run of `#{cmd}`"
-      end
-    end
-    """
-    And a file named "spec/hook_spec.rb" with:
-    """
-    require 'spec_helper'
-
-    RSpec.describe 'Hooks', :type => :aruba do
-      before(:each) { run_command_and_stop 'echo running' }
-
-      it { expect(last_command_started.stdout.chomp).to eq 'running' }
-    end
-    """
-    When I run `rspec`
-    Then the specs should all pass
-    And the output should contain:
-    """
-    before the run of `echo running`
-    """

data/features/03_testing_frameworks/rspec/setup_aruba_for_rspec.feature

@@ -1,179 +0,0 @@
-Feature: Getting started with RSpec and aruba
-
-  Background:
-    Given I use the fixture "empty-app"
-
-  Scenario: Simple Integration
-
-    To use the simple integration just require `aruba/rspec` in your
-    `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:
-
-      \* Setup Aruba Test directory
-      \* Clear environment (ENV)
-      \* 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
-    documentation for a solution.
-
-    Given a file named "spec/spec_helper.rb" with:
-    """
-    require 'aruba/rspec'
-    """
-    And a file named "spec/getting_started_spec.rb" with:
-    """
-    require 'spec_helper'
-
-    RSpec.describe 'Integrate Aruba into RSpec', :type => :aruba do
-      context 'when to be or not be...' do
-        it { expect(aruba).to be }
-      end
-
-      context 'when write file' do
-        let(:file) { 'file.txt' }
-
-        before(:each) { write_file file, 'Hello World' }
-
-        it { expect(file).to be_an_existing_file }
-        it { expect([file]).to include an_existing_file }
-      end
-    end
-    """
-    When I run `rspec`
-    Then the specs should all pass
-
-  Scenario: Simple Custom Integration
-
-    There might be some use cases where you want to build an aruba integration
-    of your own. You need to include the API and make sure, that you run
-
-      \* `restore_env` (only for aruba < 1.0.0)
-      \* `setup_aruba`
-
-    before any method of aruba is used.
-
-    Given a file named "spec/spec_helper.rb" with:
-    """
-    require 'aruba/api'
-
-    RSpec.configure do |config|
-      config.include Aruba::Api
-    end
-    """
-    And a file named "spec/getting_started_spec.rb" with:
-    """
-    require 'spec_helper'
-
-    RSpec.describe 'Custom Integration of aruba' do
-      let(:file) { 'file.txt' }
-
-      before(:each) { setup_aruba }
-      before(:each) { write_file file, 'Hello World' }
-
-      it { expect(file).to be_an_existing_file }
-    end
-    """
-    When I run `rspec`
-    Then the specs should all pass
-
-  Scenario: Custom Integration using before(:all) hook
-
-    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 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:
-    """
-    require 'aruba/api'
-
-    RSpec.configure do |config|
-      config.include Aruba::Api
-    end
-    """
-    And a file named "spec/getting_started_spec.rb" with:
-    """
-    require 'spec_helper'
-
-    RSpec.describe 'Custom Integration of aruba' do
-      before(:all) { setup_aruba }
-      before(:all) { write_file 'file.txt', 'Hello World' }
-
-      it { expect('file.txt').to be_an_existing_file }
-    end
-    """
-    When I run `rspec`
-    Then the specs should all pass
-
-  Scenario: Setup aruba before use any of it's methods
-
-    From 1.0.0 it will be required, that you setup aruba before you use it.
-
-    Given a file named "spec/spec_helper.rb" with:
-    """
-    require 'aruba/api'
-
-    RSpec.configure do |config|
-      config.include Aruba::Api
-    end
-    """
-    And a file named "spec/getting_started_spec.rb" with:
-    """
-    require 'spec_helper'
-
-    RSpec.describe 'Custom Integration of aruba' do
-      let(:file) { 'file.txt' }
-
-      before(:each) { setup_aruba }
-
-      it { expect(true).to be true }
-    end
-    """
-    And an empty file named "tmp/aruba/garbage.txt"
-    When I run `rspec`
-    Then the specs should all pass
-    And the file "tmp/aruba/garbage.txt" should not exist anymore
-
-  Scenario: Fail-safe use if "setup_aruba" is not used
-
-    If you forgot to run `setup_aruba` before the first method of aruba is
-    used, you might see an error. Although we did our best to prevent this.
-
-    Make sure that you run `setup_aruba` before any method of aruba is used. At
-    best before each and every test.
-
-    This will be not supported anymore from 1.0.0 on.
-
-    Given a file named "spec/spec_helper.rb" with:
-    """
-    require 'aruba/api'
-
-    RSpec.configure do |config|
-      config.include Aruba::Api
-    end
-    """
-    And a file named "spec/getting_started_spec.rb" with:
-    """
-    require 'spec_helper'
-
-    RSpec.describe 'Custom Integration of aruba' do
-      let(:file) { 'file.txt' }
-
-      it { expect { write_file file, 'Hello World' }.not_to raise_error }
-      it { expect(aruba.current_directory.directory?).to be true }
-    end
-    """
-    When I run `rspec`
-    Then the specs should all pass