aruba-win-fix 0.14.2

data/features/steps/environment/append_environment_variable.feature

@@ -0,0 +1,52 @@
+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/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 `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 `cli`
+        Then the output should contain:
+        \"\"\"
+        1long_value
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass

data/features/steps/environment/home_variable.feature

@@ -0,0 +1,62 @@
+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/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 `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 `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 `cli`
+        Then the output should match %r<HOME:.*tmp/aruba$>
+    """
+    When I run `cucumber`
+    Then the features should all pass

data/features/steps/environment/prepend_environment_variable.feature

@@ -0,0 +1,52 @@
+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/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 `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 `cli`
+        Then the output should contain:
+        \"\"\"
+        long_value1
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass

data/features/steps/environment/set_environment_variable.feature

@@ -0,0 +1,49 @@
+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/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 `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 `cli`
+        Then the output should contain:
+        \"\"\"
+        long_value
+        \"\"\"
+    """
+    When I run `cucumber`
+    Then the features should all pass

data/features/steps/filesystem/append_to_file.feature

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

@@ -0,0 +1,33 @@
+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/steps/filesystem/check_file_content.feature

@@ -0,0 +1,61 @@
+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

data/features/steps/filesystem/check_permissions_of_file.feature

@@ -0,0 +1,39 @@
+Feature: Check permissions of file
+
+  Background:
+    Given I use a fixture named "cli-app"
+
+  Scenario: Check mode of existing file
+    Given a file named "features/create_file.feature" with:
+    """
+    Feature: Check
+      Background:
+        Given an empty file named "file1.txt" with mode "0644"
+
+      Scenario: Check #1
+        Then the file named "file1.txt" should have permissions "0644"
+
+      Scenario: Check #2
+        Then a file "file1.txt" should have permissions "0644"
+
+      Scenario: Check #3
+        Then a file "file1.txt" should not have permissions "0444"
+
+      Scenario: Check #4
+        Then the file "file1.txt" should not have permissions "0444"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Check mode of non-existing file
+    Given a file named "features/create_file.feature" with:
+    """
+    Feature: Check
+      Background:
+        Given a file named "file1.txt" does not exist
+
+      Scenario: Check 
+        Then the file named "file1.txt" should have permissions "0644"
+    """
+    When I run `cucumber`
+    Then the features should not pass

data/features/steps/filesystem/compare_files.feature

@@ -0,0 +1,42 @@
+Feature: Compare files
+
+  Background:
+    Given I use a fixture named "cli-app"
+
+  Scenario: Compare existing files
+    Given a file named "features/non-existence.feature" with:
+    """
+    Feature: Existence
+      Scenario: Existence
+        Given a file named "foo" with:
+        \"\"\"
+        hello world
+        \"\"\"
+        And a file named "bar" with:
+        \"\"\"
+        hello world
+        \"\"\"
+        And a file named "nonbar" with:
+        \"\"\"
+        hello another world
+        \"\"\"
+        Then the file "foo" should be equal to file "bar"
+        And the file "foo" should not be equal to file "nonbar"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Compare non-existing files
+    Given a file named "features/non-existence.feature" with:
+    """
+    Feature: Existence
+      Scenario: Existence
+        Given a file named "foo" with:
+        \"\"\"
+        hello world
+        \"\"\"
+        Then the file "foo" should be equal to file "bar"
+    """
+    When I run `cucumber`
+    Then the features should not pass
+

data/features/steps/filesystem/copy.feature

@@ -0,0 +1,45 @@
+Feature: Copy file or directory
+
+  As a user of aruba
+  I want ot copy a file or a directory
+  To setup my tests
+
+  Background:
+    Given I use a fixture named "cli-app"
+
+  Scenario: Copy file
+    Given a file named "features/copy.feature" with:
+    """
+    Feature: Copy
+      Scenario: Copy
+        Given an empty file named "file1.txt"
+        And an empty file named "file2.txt"
+        And an empty file named "file3.txt"
+        When I copy a file named "file1.txt" to "new_file1.txt"
+        When I copy a file from "file2.txt" to "new_file2.txt"
+        When I copy 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: Copy directory
+    Given a file named "features/copy.feature" with:
+    """
+    Feature: Copy
+      Scenario: Copy
+        Given a directory named "dir1.d"
+        And a directory named "dir2.d"
+        And a directory named "dir3.d"
+        When I copy a directory named "dir1.d" to "new_dir1.d"
+        When I copy a directory from "dir2.d" to "new_dir2.d"
+        When I copy 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
+