aruba 0.9.0.pre → 0.9.0.pre2

data/features/step_definitions/aruba_dev_steps.rb

@@ -25,30 +25,32 @@ Then /^the following step should fail with Spec::Expectations::ExpectationNotMet
   expect{steps multiline_step.to_s}.to raise_error(RSpec::Expectations::ExpectationNotMetError)
 end
 
-Then /^the output should be (\d+) bytes long$/ do |length|
-  expect(all_output.length).to eq length.to_i
-end
-
 Then /^the feature(?:s)? should( not)?(?: all)? pass$/ do |negated|
   if negated
     step 'the output should contain " failed)"'
     step 'the exit status should be 1'
   else
     step 'the output should not contain " failed)"'
+    step 'the output should not contain " undefined)"'
     step 'the exit status should be 0'
   end
 end
 
-Then /^the feature(?:s)? should( not)?(?: all)? pass with:$/ do |negated, string|
+Then /^the feature(?:s)? should( not)?(?: all)? pass with( regex)?:$/ do |negated, regex, string|
   if negated
     step 'the output should contain " failed)"'
     step 'the exit status should be 1'
   else
     step 'the output should not contain " failed)"'
+    step 'the output should not contain " undefined)"'
     step 'the exit status should be 0'
   end
 
-  step 'the output should contain:', string if string
+  if regex
+    step "the output should match %r<#{string}>"
+  else
+    step 'the output should contain:', string
+  end
 end
 
 Then /^the spec(?:s)? should( not)?(?: all)? pass(?: with (\d+) failures?)?$/ do |negated, count_failures|
@@ -66,7 +68,7 @@ Then /^the spec(?:s)? should( not)?(?: all)? pass(?: with (\d+) failures?)?$/ do
   end
 end
 
-Then /^the spec(?:s)? should( not)?(?: all)? pass with:$/ do |negated, string|
+Then /^the spec(?:s)? should( not)?(?: all)? pass with( regex)?:$/ do |negated, regex, string|
   if negated
     step 'the output should contain " failed)"'
     step 'the exit status should be 1'
@@ -75,7 +77,11 @@ Then /^the spec(?:s)? should( not)?(?: all)? pass with:$/ do |negated, string|
     step 'the exit status should be 0'
   end
 
-  step 'the output should contain:', string if string
+  if regex
+    step "the output should match %r<#{string}>"
+  else
+    step 'the output should contain:', string
+  end
 end
 
 Given(/^the default executable$/) do
@@ -103,6 +109,7 @@ Given(/^the default feature-test$/) do
   )
 end
 
-Given(/^(?:an|the) executable(?: named)? "([^"]*)" with:$/) do |file_name, file_content|
-  step %(a file named "#{file_name}" with mode "0755" and with:), file_content
+Then(/^aruba should be installed on the local system$/) do
+  run('gem list aruba')
+  expect(last_command_started).to have_output(/aruba/)
 end

data/features/step_definitions/hooks.rb

@@ -0,0 +1,11 @@
+require 'cucumber/platform'
+
+Before '@requires-ruby-version-193' do
+  next unless RUBY_VERSION < '1.9.3'
+
+  if Cucumber::VERSION < '2'
+    pending
+  else
+    skip_this_scenario
+  end
+end

data/features/steps/commands/exit_statuses.feature

@@ -94,7 +94,7 @@ Feature: Check exit status of commands
     """
     Feature: Failing program
       Scenario: Run command
-        Given the default aruba timeout is 2 seconds
+        Given the default aruba exit timeout is 2 seconds
         When I successfully run `cli`
     """
     When I run `cucumber`
@@ -110,7 +110,7 @@ Feature: Check exit status of commands
     """
     Feature: Failing program
       Scenario: Run command
-        Given the default aruba timeout is 0 seconds
+        Given the default aruba exit timeout is 0 seconds
         When I successfully run `cli` for up to 2 seconds
     """
     When I run `cucumber`
@@ -126,7 +126,7 @@ Feature: Check exit status of commands
     """
     Feature: Failing program
       Scenario: Run command
-        Given the default aruba timeout is 0 seconds
+        Given the default aruba exit timeout is 0 seconds
         When I successfully run `cli` for up to 1 seconds
     """
     When I run `cucumber`

data/features/steps/commands/run.feature

@@ -19,18 +19,3 @@ Feature: Run commands
     """
     When I run `cucumber`
     Then the features should all pass
-
-  Scenario: Relative command
-    Given an executable named "bin/cli" with:
-    """
-    #!/bin/bash
-    exit 0
-    """
-    And a file named "features/run.feature" with:
-    """
-    Feature: Run it
-      Scenario: Run command
-        When I run `bin/cli`
-    """
-    When I run `cucumber`
-    Then the features should all 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
+

data/features/steps/filesystem/create_directory.feature

@@ -0,0 +1,47 @@
+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
+      Scenario: Create directory
+        Given a directory named "dir1"
+        Given the directory "dir2"
+        Given the directory named "dir3"
+        Then a directory named "dir1" should exist
+        And a directory named "dir2" should exist
+        And a directory named "dir3" 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/steps/filesystem/create_file.feature

@@ -0,0 +1,53 @@
+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 file
+    Given a file named "features/create_file.feature" with:
+    """
+    Feature: Create directory
+      Scenario: Create directory
+        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

data/features/steps/filesystem/file_content.feature

@@ -42,7 +42,7 @@ Feature: Check file content
 
         \"\"\"
     """
-    When I run `cucumber`
+    When I run `cucumber --format progress`
     Then the features should all pass
 
   Scenario: Trailing white space is ignored

data/features/steps/filesystem/move.feature

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

@@ -0,0 +1,72 @@
+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/use_fixture.feature

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