aruba 0.14.10 → 1.0.0

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

@@ -1,57 +0,0 @@
-Feature: Create Directory
-
-  As a user of aruba
-  I want to create directories
-
-  Background:
-    Given I use a fixture named "cli-app"
-
-  Scenario: Non-existing directory
-    Given a file named "features/create_directory.feature" with:
-    """
-    Feature: Create directory
-      Background:
-        Given a directory named "dir1"
-
-      Scenario: Create directory #1
-        Then a directory named "dir1" should exist
-
-      Scenario: Create directory #2
-        Then a directory named "dir1" should exist
-
-      Scenario: Create directory #3
-        Then a directory named "dir1" should exist
-
-      Scenario: Create directory #4
-        Then a directory named "dir1" should exist
-
-      Scenario: Create directory #5
-        Then a directory named "dir1" should exist
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Existing directory
-
-    It doesn't matter if a directory already exist.
-
-    Given a file named "features/create_directory.feature" with:
-    """
-    Feature: Create directory
-      Scenario: Create directory
-        Given a directory named "dir1"
-        And a directory named "dir1"
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Change mode a long with creation of directory
-    Given a file named "features/create_directory.feature" with:
-    """
-    Feature: Create directory
-      Scenario: Create directory
-        Given a directory named "dir1" with mode "0644"
-        Then the directory named "dir1" should have permissions "0644"
-    """
-    When I run `cucumber`
-    Then the features should all pass

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

@@ -1,76 +0,0 @@
-Feature: Create new File
-
-  As a user of aruba
-  I want to create files
-
-  Background:
-    Given I use a fixture named "cli-app"
-
-  Scenario: Create empty file
-    Given a file named "features/create_file.feature" with:
-    """
-    Feature: Create file
-      Scenario: Create file
-        Given an empty file named "file1.txt"
-        Then a file named "file1.txt" should exist
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Create file with content
-    Given a file named "features/create_file.feature" with:
-    """
-    Feature: Create file
-      Scenario: Create file
-        Given a file named "file1.txt" with:
-        \"\"\"
-        Hello World
-        \"\"\"
-        Then the file named "file1.txt" should contain:
-        \"\"\"
-        Hello World
-        \"\"\"
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Change mode a long with creation of a file with content
-    Given a file named "features/create_file.feature" with:
-    """
-    Feature: Create file
-      Scenario: Create file
-        Given a file named "file1.txt" with mode "0644" and with:
-        \"\"\"
-        Hello World
-        \"\"\"
-        Then the file named "file1.txt" should have permissions "0644"
-        And the file named "file1.txt" should contain:
-        \"\"\"
-        Hello World
-        \"\"\"
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Change mode a long with creation of empty file
-    Given a file named "features/create_file.feature" with:
-    """
-    Feature: Create file
-      Scenario: Create file
-        Given an empty file named "file1.txt" with mode "0644"
-        Then the file named "file1.txt" should have permissions "0644"
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Create a fixed sized file
-    Given a file named "features/non-existence.feature" with:
-    """
-    Feature: Create file
-      Scenario: Create file
-        Given a 1048576 byte file named "test.txt"
-        Then a 1048576 byte file named "test.txt" should exist
-    """
-    When I run `cucumber`
-    Then the features should all pass
-

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

@@ -1,44 +0,0 @@
-Feature: Move file or directory
-
-  As a user of aruba
-  I want ot move a file or a directory
-  To setup my tests
-
-  Background:
-    Given I use a fixture named "cli-app"
-
-  Scenario: Move file
-    Given a file named "features/move.feature" with:
-    """
-    Feature: Move
-      Scenario: Move
-        Given an empty file named "file1.txt"
-        And an empty file named "file2.txt"
-        And an empty file named "file3.txt"
-        When I move a file named "file1.txt" to "new_file1.txt"
-        When I move a file from "file2.txt" to "new_file2.txt"
-        When I move the file "file3.txt" to "new_file3.txt"
-        Then a file named "new_file1.txt" should exist
-        Then a file named "new_file2.txt" should exist
-        Then a file named "new_file3.txt" should exist
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Move directory
-    Given a file named "features/move.feature" with:
-    """
-    Feature: Move
-      Scenario: Move
-        Given a directory named "dir1.d"
-        And a directory named "dir2.d"
-        And a directory named "dir3.d"
-        When I move a directory named "dir1.d" to "new_dir1.d"
-        When I move a directory from "dir2.d" to "new_dir2.d"
-        When I move the directory "dir3.d" to "new_dir3.d"
-        Then a directory named "new_dir1.d" should exist
-        Then a directory named "new_dir2.d" should exist
-        Then a directory named "new_dir3.d" should exist
-    """
-    When I run `cucumber`
-    Then the features should all pass

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`
-    """