aruba 0.14.14 → 1.0.0.pre.alpha.1

data/features/03_testing_frameworks/cucumber/steps/environment/append_environment_variable.feature

@@ -1,52 +0,0 @@
-Feature: Append environment variable via "cucumber"-step
-
-  It is quite handy to modify the environment of a process. To make this
-  possible, `aruba` provides several steps. One of these is
-  `I append the values to environment variables:`-step. Using this step appends
-  the values. Each variable name and each value is converted to a string.
-  Otherwise `ruby` would complain about an invalid argument.
-
-  Background:
-    Given I use the fixture "cli-app"
-    And an executable named "bin/aruba-test-cli" with:
-    """
-    #!/bin/bash
-
-    echo $LONG_LONG_VARIABLE
-    """
-    And a file named "features/support/variables.rb" with:
-    """
-    ENV['LONG_LONG_VARIABLE'] = '1'
-    """
-
-  Scenario: Append environment variable by using a step given in table
-    Given a file named "features/home_variable.feature" with:
-    """
-    Feature: Environment Variable
-      Scenario: Run command
-        Given I append the values to the environment variables:
-          | variable           | value      |
-          | LONG_LONG_VARIABLE | long_value |
-        When I run `aruba-test-cli`
-        Then the output should contain:
-        \"\"\"
-        1long_value
-        \"\"\"
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Append single environment variable by using a step
-    Given a file named "features/home_variable.feature" with:
-    """
-    Feature: Environment Variable
-      Scenario: Run command
-        Given I append "long_value" to the environment variable "LONG_LONG_VARIABLE"
-        When I run `aruba-test-cli`
-        Then the output should contain:
-        \"\"\"
-        1long_value
-        \"\"\"
-    """
-    When I run `cucumber`
-    Then the features should all pass

data/features/03_testing_frameworks/cucumber/steps/environment/modify_home_variable_for_testing.feature

@@ -1,62 +0,0 @@
-Feature: Mock the HOME variable
-
-  If you develop commandline applications, you might want to give your users
-  the possibility to configure your program. Normally this is done via
-  `.your-app-rc` or via `.config/your-app` an systems which comply to the
-  freedesktop-specifications.
-
-  To prevent to litter the developers HOME-directory `aruba` comes with a step
-  which mocks the `HOME`-variable. It is set to the
-  `aruba`-`working-directory`.
-
-  Background:
-    Given I use the fixture "cli-app"
-    And an executable named "bin/aruba-test-cli" with:
-    """
-    #!/bin/bash
-
-    echo "HOME: $HOME"
-    """
-
-  Scenario: Mocked home directory by using a step
-    Given a file named "features/home_variable.feature" with:
-    """
-    Feature: Home Variable
-      Scenario: Run command
-        Given a mocked home directory
-        When I run `aruba-test-cli`
-        Then the output should match %r<HOME:.*tmp/aruba$>
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Mocked home directory by using a tag
-    Given a file named "features/home_variable.feature" with:
-    """
-    Feature: Home Variable
-      @mocked-home-directory
-      Scenario: Run command
-        When I run `aruba-test-cli`
-        Then the output should match %r<HOME:.*tmp/aruba$>
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Redefine home directory by using the aruba configuration
-    Given a file named "features/support/home_variable.rb" with:
-    """
-    require 'aruba/cucumber'
-
-    Aruba.configure do |config|
-      config.home_directory = File.join(config.root_directory, config.working_directory)
-    end
-    """
-    Given a file named "features/home_variable.feature" with:
-    """
-    Feature: Home Variable
-      Scenario: Run command
-        When I run `aruba-test-cli`
-        Then the output should match %r<HOME:.*tmp/aruba$>
-    """
-    When I run `cucumber`
-    Then the features should all pass

data/features/03_testing_frameworks/cucumber/steps/environment/prepend_environment_variable.feature

@@ -1,52 +0,0 @@
-Feature: Prepend environment variable via "cucumber"-step
-
-  It is quite handy to modify the environment of a process. To make this
-  possible, `aruba` provides several steps. One of these is
-  `I prepend the values to environment variables:`-step. Using this step prepends
-  the values. Each variable name and each value is converted to a string.
-  Otherwise `ruby` would complain about an invalid argument.
-
-  Background:
-    Given I use the fixture "cli-app"
-    And an executable named "bin/aruba-test-cli" with:
-    """
-    #!/bin/bash
-
-    echo $LONG_LONG_VARIABLE
-    """
-    And a file named "features/support/variables.rb" with:
-    """
-    ENV['LONG_LONG_VARIABLE'] = '1'
-    """
-
-  Scenario: Prepend environment variable by using a step given in table
-    Given a file named "features/home_variable.feature" with:
-    """
-    Feature: Environment Variable
-      Scenario: Run command
-        Given I prepend the values to the environment variables:
-          | variable           | value      |
-          | LONG_LONG_VARIABLE | long_value |
-        When I run `aruba-test-cli`
-        Then the output should contain:
-        \"\"\"
-        long_value1
-        \"\"\"
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Prepend single environment variable by using a step
-    Given a file named "features/home_variable.feature" with:
-    """
-    Feature: Environment Variable
-      Scenario: Run command
-        Given I prepend "long_value" to the environment variable "LONG_LONG_VARIABLE"
-        When I run `aruba-test-cli`
-        Then the output should contain:
-        \"\"\"
-        long_value1
-        \"\"\"
-    """
-    When I run `cucumber`
-    Then the features should all pass

data/features/03_testing_frameworks/cucumber/steps/environment/set_environment_variable.feature

@@ -1,49 +0,0 @@
-Feature: Set environment variable via "cucumber"-step
-
-  It is quite handy to modify the environment of a process. To make this
-  possible, `aruba` provides several steps. One of these is
-  `I set the environment variables to:`-step. Using this step sets the values of a
-  non-existing variables and overwrites an existing values. Each variable name
-  and each value is converted to a string. Otherwise `ruby` would complain
-  about an invalid argument.
-
-  Background:
-    Given I use the fixture "cli-app"
-    And an executable named "bin/aruba-test-cli" with:
-    """
-    #!/bin/bash
-
-    echo $LONG_LONG_VARIABLE
-    """
-
-  Scenario: Set environment variable by using a step given in table
-    Given a file named "features/home_variable.feature" with:
-    """
-    Feature: Environment Variable
-      Scenario: Run command
-        Given I set the environment variables to:
-          | variable           | value      |
-          | LONG_LONG_VARIABLE | long_value |
-        When I run `aruba-test-cli`
-        Then the output should contain:
-        \"\"\"
-        long_value
-        \"\"\"
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Set single environment variable by using a step
-    Given a file named "features/home_variable.feature" with:
-    """
-    Feature: Environment Variable
-      Scenario: Run command
-        Given I set the environment variable "LONG_LONG_VARIABLE" to "long_value"
-        When I run `aruba-test-cli`
-        Then the output should contain:
-        \"\"\"
-        long_value
-        \"\"\"
-    """
-    When I run `cucumber`
-    Then the features should all pass

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

@@ -1,45 +0,0 @@
-Feature: Append content to file
-
-  You might want to append some content to a file.
-
-  Background:
-    Given I use a fixture named "cli-app"
-
-  Scenario: Append to a existing file
-    Given a file named "features/non-existence.feature" with:
-    """
-    Feature: Existence
-      Scenario: Existence
-        Given a file named "foo/bar/example.txt" with:
-        \"\"\"
-        hello world
-        \"\"\"
-        When I append to "foo/bar/example.txt" with:
-        \"\"\"
-        this was appended
-        \"\"\"
-        Then the file named "foo/bar/example.txt" should contain:
-        \"\"\"
-        hello worldthis was appended
-        \"\"\"
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Append to a non-existing file
-    Given a file named "features/non-existence.feature" with:
-    """
-    Feature: Existence
-      Scenario: Existence
-        Given a file named "foo/bar/example.txt" does not exist
-        When I append to "foo/bar/example.txt" with:
-        \"\"\"
-        this was appended
-        \"\"\"
-        Then the file named "foo/bar/example.txt" should contain:
-        \"\"\"
-        this was appended
-        \"\"\"
-    """
-    When I run `cucumber`
-    Then the features should all pass

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

@@ -1,33 +0,0 @@
-Feature: Change working directory
-
-  You might want to change the current working directory.
-
-  Background:
-    Given I use a fixture named "cli-app"
-
-  Scenario: Change to an existing sub directory
-    Given a file named "features/non-existence.feature" with:
-    """
-    Feature: Working Directory
-      Scenario: Working Directory
-        Given a file named "foo/bar/example.txt" with:
-        \"\"\"
-        hello world
-        \"\"\"
-        When I cd to "foo/bar"
-        And I run `cat example.txt`
-        Then the output should contain "hello world"
-        And the file "example.txt" should exist
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Change to an non-existing sub directory
-    Given a file named "features/non-existence.feature" with:
-    """
-    Feature: Working Directory
-      Scenario: Working Directory
-        When I cd to "foo/bar/non-existing"
-    """
-    When I run `cucumber`
-    Then the features should not pass

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

@@ -1,57 +0,0 @@
-Feature: Make sure and check a directory exists
-
-  To setup a working environment, you may want to make sure, that a
-  directory exist.
-
-  Background:
-    Given I use a fixture named "cli-app"
-
-  Scenario: Check for presence of a single directory
-    Given a file named "features/existence.feature" with:
-    """
-    Feature: Existence
-      Background:
-        Given an empty directory "lorem/ipsum/dolor"
-
-      Scenario: Existence #1
-        Then the directory "lorem/ipsum/dolor" should exist
-
-      Scenario: Existence #2
-        Then the directory named "lorem/ipsum/dolor" should exist
-
-      Scenario: Existence #3
-        Then a directory named "lorem/ipsum/dolor" should exist
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Check for presence of a multiple directories
-    Given a file named "features/existence.feature" with:
-    """
-    Feature: Existence
-      Scenario: Existence
-        Given an empty directory "lorem/ipsum/dolor"
-        And an empty directory "lorem/ipsum/amet"
-        Then the following directories should exist:
-          | lorem/ipsum/dolor |
-          | lorem/ipsum/amet  |
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
-
-  Scenario: Check for presence of a subset of directories
-    Given a file named "features/existence.feature" with:
-    """
-    Feature: Existence
-      Scenario: Existence
-        Given an empty directory "lorem/ipsum/dolor"
-        And an empty directory "lorem/ipsum/amet"
-        And an empty directory "lorem/ipsum/sit"
-        Then the following directories should exist:
-          | lorem/ipsum/dolor |
-          | lorem/ipsum/amet  |
-    """
-    When I run `cucumber`
-    Then the features should all pass
-

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

@@ -1,43 +0,0 @@
-Feature: Make sure and check a file exists
-
-  To setup a working environment, you may want to make sure, that a
-  file exist or if you ran your command of a file
-  was deleted.
-
-  Background:
-    Given I use a fixture named "cli-app"
-
-  Scenario: Check for presence of a single file
-    Given an empty file named "lorem/ipsum/dolor"
-    Then a file named "lorem/ipsum/dolor" should exist
-
-  Scenario: Check for presence of a subset of files
-    Given a file named "features/existence.feature" with:
-    """
-    Feature: Existence
-      Scenario: Existence
-        Given an empty file named "lorem/ipsum/dolor"
-        And an empty file named "lorem/ipsum/sit"
-        And an empty file named "lorem/ipsum/amet"
-        Then the following files should exist:
-          | lorem/ipsum/dolor |
-          | lorem/ipsum/amet  |
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Check for presence of a single file using a regex
-    Given a file named "features/non-existence.feature" with:
-    """
-    Feature: Existence
-      Background:
-        Given an empty file named "lorem/ipsum/dolor"
-
-      Scenario: Existence #1
-        Then a file matching %r<dolor$> should exist
-
-      Scenario: Existence #2
-        Then a file matching %r<ipsum/dolor> should exist
-    """
-    When I run `cucumber`
-    Then the features should all pass

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

@@ -1,143 +0,0 @@
-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:
-    """
-    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