aruba 0.14.9 → 1.0.0

data/features/steps/filesystem/file_content.feature

@@ -1,86 +0,0 @@
-Feature: Check file content
-
-  Background:
-    Given I use a fixture named "cli-app"
-
-  Scenario: Existing file having content
-    Given a file named "features/file_content.feature" with:
-    """
-    Feature: File content
-      Scenario: file content
-        Given a file named "test.txt" with:
-        \"\"\"
-        Hello World
-        \"\"\"
-        Then the file named "test.txt" should contain:
-        \"\"\"
-        Hello World
-        \"\"\"
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Existing file having content with special characters
-    Given a file named "features/file_content.feature" with:
-    """
-    Feature: File content
-      Scenario: file content
-        Given a file named "test.txt" with:
-        \"\"\"
-        UUUUU
-
-        1 scenario (1 undefined)
-        5 steps (5 undefined)
-
-        \"\"\"
-        Then the file named "test.txt" should contain:
-        \"\"\"
-        UUUUU
-
-        1 scenario (1 undefined)
-        5 steps (5 undefined)
-
-        \"\"\"
-    """
-    When I run `cucumber --format progress`
-    Then the features should all pass
-
-  Scenario: Trailing white space is ignored
-    Given a file named "features/file_content.feature" with:
-    """
-    Feature: File content
-      Scenario: file content
-        Given a file named "test.txt" with:
-        \"\"\"
-        UUUUU
-
-        \"\"\"
-        Then the file named "test.txt" should contain:
-        \"\"\"
-        UUUUU
-        \"\"\"
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Use non-ASCII UTF-8 characters
-    Given a file named "features/file_content.feature" with:
-    """
-    Feature: File content
-      Scenario: file content
-        Given a file named "test.txt" with:
-        \"\"\"
-        フィーチャ
-        \"\"\"
-        When I run `cat test.txt`
-        Then the output should contain:
-        \"\"\"
-        フィーチャ
-        \"\"\"
-        And the file named "test.txt" should contain:
-        \"\"\"
-        フィーチャ
-        \"\"\"
-    """
-    When I run `cucumber`
-    Then the features should all pass

data/features/steps/filesystem/fixtures.feature

@@ -1,64 +0,0 @@
-Feature: Use fixtures in your tests
-
-  Sometimes your tests need existing files to work - e.g binary data files you
-  cannot create programmatically. Since `aruba` >= 0.6.3 includes some basic
-  support for fixtures. All you need to do is the following:
-  
-  1. Create a `fixtures`-directory
-  2. Create fixture files in this directory
-  
-
-  Background:
-    Given I use a fixture named "cli-app"
-
-  Scenario: Use a fixture for your tests
-    Given a file named "features/fixtures.feature" with:
-    """
-    Feature: Fixture
-      Scenario: Fixture
-        Given I use a fixture named "fixtures-app"
-        Then a file named "test.txt" should exist
-    """
-    And a directory named "fixtures"
-    And an empty file named "fixtures/fixtures-app/test.txt"
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Use a fixture for your tests in test/
-    Given a file named "features/fixtures.feature" with:
-    """
-    Feature: Fixture
-      Scenario: Fixture
-        Given I use a fixture named "fixtures-app"
-        Then a file named "test.txt" should exist
-    """
-    And a directory named "test/fixtures"
-    And an empty file named "test/fixtures/fixtures-app/test.txt"
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Use a fixture for your tests in specs/
-    Given a file named "features/fixtures.feature" with:
-    """
-    Feature: Fixture
-      Scenario: Fixture
-        Given I use a fixture named "fixtures-app"
-        Then a file named "test.txt" should exist
-    """
-    And a directory named "spec/fixtures"
-    And an empty file named "spec/fixtures/fixtures-app/test.txt"
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Use a fixture for your tests in features/
-    Given a file named "features/fixtures.feature" with:
-    """
-    Feature: Fixture
-      Scenario: Fixture
-        Given I use a fixture named "fixtures-app"
-        Then a file named "test.txt" should exist
-    """
-    And a directory named "features/fixtures"
-    And an empty file named "features/fixtures/fixtures-app/test.txt"
-    When I run `cucumber`
-    Then the features should all pass

data/features/steps/filesystem/move.feature

@@ -1,45 +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/steps/filesystem/non_existence_of_directory.feature

@@ -1,69 +0,0 @@
-Feature: Make sure and check a directory does not exist
-
-  To setup a working environment, you may want to make sure, that a
-  directory does not exist or if you ran your command of a directory
-  was deleted.
-
-  Background:
-    Given I use a fixture named "cli-app"
-
-  Scenario: Delete existing directory
-    Given a file named "features/non-existence.feature" with:
-    """
-    Feature: Non-Existence
-      Background:
-        Given a directory named "example.d" does not exist
-
-      Scenario: Non-Existence #1
-        Then the directory "example.d" should not exist
-
-      Scenario: Non-Existence #2
-        Then the directory "example.d" should not exist
-
-      Scenario: Non-Existence #3
-        Then the directory "example.d" should not exist
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Check if a directory does not exists
-    Given a file named "features/non-existence.feature" with:
-    """
-    Feature: Non-Existence
-      Background:
-        Given a directory named "example.d" does not exist
-
-      Scenario: Non-Existence #1
-        Then the directory "example.d" should not exist
-
-      Scenario: Non-Existence #2
-        Then the directory named "example.d" should not exist
-
-      Scenario: Non-Existence #3
-        Then a directory named "example.d" should not exist
-
-      Scenario: Non-Existence #4
-        Then a directory named "example.d" should not exist anymore
-
-      Scenario: Non-Existence #5
-        Then the directory named "example.d" should not exist anymore
-
-      Scenario: Non-Existence #6
-        Then the directory "example.d" should not exist anymore
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Check for absence of a subset of directories
-    Given a file named "features/non-existence.feature" with:
-    """
-    Feature: Non-Existence
-      Scenario: Non-Existence
-        Given the directory "lorem/ipsum/dolor" does not exist
-        And the directory "lorem/ipsum/amet" does not exist
-        Then the following directories should not exist:
-          | lorem/ipsum/dolor |
-          | lorem/ipsum/amet  |
-    """
-    When I run `cucumber`
-    Then the features should all pass

data/features/steps/filesystem/non_existence_of_file.feature

@@ -1,80 +0,0 @@
-Feature: Make sure and check a file does not exist
-
-  To setup a working environment, you may want to make sure, that a
-  file does not exist or if you ran your command of a file
-  was deleted.
-
-  Background:
-    Given I use a fixture named "cli-app"
-
-  Scenario: Delete existing file
-    Given a file named "features/non-existence.feature" with:
-    """
-    Feature: Non-Existence
-      Background:
-        Given a file named "example.txt" does not exist
-
-      Scenario: Non-Existence #1
-        Then the file "example.txt" should not exist
-
-      Scenario: Non-Existence #2
-        Then the file "example.txt" should not exist
-
-      Scenario: Non-Existence #3
-        Then the file "example.txt" should not exist
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Check if a file does not exists
-    Given a file named "features/non-existence.feature" with:
-    """
-    Feature: Non-Existence
-      Background:
-        Given a file named "example.txt" does not exist
-
-      Scenario: Non-Existence #1
-        Then the file "example.txt" should not exist
-
-      Scenario: Non-Existence #2
-        Then the file named "example.txt" should not exist
-
-      Scenario: Non-Existence #3
-        Then a file named "example.txt" should not exist
-
-      Scenario: Non-Existence #4
-        Then a file named "example.txt" should not exist anymore
-
-      Scenario: Non-Existence #5
-        Then the file named "example.txt" should not exist anymore
-
-      Scenario: Non-Existence #6
-        Then the file "example.txt" should not exist anymore
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Check for absence of multiple files
-    Given a file named "features/non-existence.feature" with:
-    """
-    Feature: Non-Existence
-      Scenario: Non-Existence
-        Given the file "lorem/ipsum/dolor.txt" does not exist
-        Given the file "lorem/ipsum/sit.txt" does not exist
-        Then the following files should not exist:
-          | lorem/ipsum/dolor.txt |
-          | lorem/ipsum/sit.txt |
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Check for absence of a single file using a regex
-    Given a file named "features/non-existence.feature" with:
-    """
-    Feature: Existence
-      Scenario: Existence
-        Given the file "lorem/ipsum/sit.txt" does not exist
-        Then a file matching %r<^ipsum> should not exist
-    """
-    When I run `cucumber`
-    Then the features should all pass

data/features/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/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/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/steps/filesystem/use_fixture.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/steps/overview.feature

@@ -1,25 +0,0 @@
-Feature: Overview of steps
-
-  Given you're a system administrator
-  Who would like to use `aruba`
-  But didn't know which steps are available
-
-  Scenario: Use cucumber output formatter
-    Given I use a fixture named "cli-app"
-    And a file named "features/run.feature" with:
-    """
-    Feature: Run it
-      Scenario: Run command
-        Given a directory named "features"
-        And a file named "features/support/env.rb" with:
-        \"\"\"
-        require 'aruba/cucumber'
-        \"\"\"
-        When I run `cucumber --format stepdefs`
-        Then the output should contain:
-        \"\"\"
-        NOT MATCHED BY ANY STEPS
-        \"\"\"
-    """
-    When I run `cucumber`
-    Then the features should all pass

data/features/support/aruba.rb

@@ -1,7 +0,0 @@
-require 'aruba/cucumber'
-
-Aruba.configure do |config|
-  config.exit_timeout                          = 120
-  config.io_wait_timeout                       = 2
-  config.activate_announcer_on_command_failure = [:stderr, :stdout, :command]
-end

data/features/support/env.rb

@@ -1,33 +0,0 @@
-$LOAD_PATH.unshift File.expand_path('../../../lib', __FILE__)
-
-# Has to be the first file required so that all other files show coverage information
-require 'simplecov'
-
-# Standard Library
-require 'fileutils'
-require 'pathname'
-
-# Gems
-require 'aruba/cucumber'
-require 'rspec/expectations'
-
-Before do |scenario|
-  command_name = if scenario.respond_to?(:feature) && scenario.respond_to?(:name)
-                   "#{scenario.feature.name} #{scenario.name}"
-                 else
-                   raise TypeError.new("Don't know how to extract command name from #{scenario.class}")
-                 end
-
-  # Used in simplecov_setup so that each scenario has a different name and their coverage results are merged instead
-  # of overwriting each other as 'Cucumber Features'
-  ENV['SIMPLECOV_COMMAND_NAME'] = command_name.to_s
-
-  simplecov_setup_pathname = Pathname.new(__FILE__).expand_path.parent.join('simplecov_setup')
-
-  # set environment variable so child processes will merge their coverage data with parent process's coverage data.
-  ENV['RUBYOPT'] = if RUBY_VERSION < '1.9'
-                     "-r rubygems -r#{simplecov_setup_pathname} #{ENV['RUBYOPT']}"
-                   else
-                     "-r#{simplecov_setup_pathname} #{ENV['RUBYOPT']}"
-                   end
-end

data/features/support/jruby.rb

@@ -1,5 +0,0 @@
-if RUBY_PLATFORM == 'java'
-  Before do
-    @aruba_timeout_seconds = 15
-  end
-end

data/features/support/simplecov_setup.rb

@@ -1,8 +0,0 @@
-# @note this file is loaded in env.rb to setup simplecov using RUBYOPTs for child processes and @in-process
-require 'simplecov'
-
-root = File.expand_path('../../../', __FILE__)
-
-SimpleCov.command_name(ENV['SIMPLECOV_COMMAND_NAME'])
-SimpleCov.root(root)
-load File.join(root, '.simplecov')

data/fixtures/cli-app/bin/cli

@@ -1,6 +0,0 @@
-#!/usr/bin/env ruby
-
-$LOAD_PATH << File.expand_path('../../lib', __FILE__)
-require 'cli/app'
-
-exit 0

data/fixtures/spawn_process/stderr.sh

@@ -1,3 +0,0 @@
-#!/usr/bin/env bash
-
-echo $* >&2