aruba 0.9.0.pre → 0.9.0.pre2

data/features/api/filesystem/move.feature

@@ -0,0 +1,119 @@
+Feature: Move file/directory
+
+  If you need to move some files/directories you can use the `#move`-method
+  command. If multiple arguments are given, the last one needs to be a directory.
+
+  Background:
+    Given I use a fixture named "cli-app"
+
+  Scenario: Non-existing destination
+    Given a file named "spec/cd_spec.rb" with:
+    """ruby
+    require 'spec_helper'
+
+    RSpec.describe 'Move', :type => :aruba do
+      let(:old_location) { 'old_dir.d' }
+      let(:new_location) { 'new_dir.d' }
+
+      before(:each) do 
+        create_directory old_location
+        move old_location, new_location
+      end
+
+      it { expect(new_location).to be_an_existing_directory }
+    end
+    """
+    When I run `rspec`
+    Then the specs should all pass
+
+  Scenario: Existing destination
+    Given a file named "spec/cd_spec.rb" with:
+    """ruby
+    require 'spec_helper'
+
+    RSpec.describe 'Move', :type => :aruba do
+      let(:old_location) { 'old_dir.d' }
+      let(:new_location) { 'new_dir.d' }
+
+      before(:each) do 
+        create_directory old_location
+        create_directory new_location
+
+        move old_location, new_location
+      end
+
+      it { expect(File.join(new_location, old_location)).to be_an_existing_directory }
+    end
+    """
+    When I run `rspec`
+    Then the specs should all pass
+
+  Scenario: Source is fixture path
+    Given a file named "spec/cd_spec.rb" with:
+    """ruby
+    require 'spec_helper'
+
+    RSpec.describe 'Move', :type => :aruba do
+      let(:old_location) { '%/old_dir.d' }
+      let(:new_location) { 'new_dir.d' }
+
+      it { expect { move old_location, new_location }.to raise_error ArgumentError, /fixture/ }
+    end
+    """
+    When I run `rspec`
+    Then the specs should all pass
+
+  Scenario: Destination is fixture path
+    Given a file named "spec/cd_spec.rb" with:
+    """ruby
+    require 'spec_helper'
+
+    RSpec.describe 'Move', :type => :aruba do
+      let(:old_location) { 'old_dir.d' }
+      let(:new_location) { '%/new_dir.d' }
+
+      it { expect { move old_location, new_location }.to raise_error ArgumentError, /fixture/ }
+    end
+    """
+    When I run `rspec`
+    Then the specs should all pass
+
+  Scenario: Multiple sources and destination is directory
+    Given a file named "spec/cd_spec.rb" with:
+    """ruby
+    require 'spec_helper'
+
+    RSpec.describe 'Move', :type => :aruba do
+      let(:old_location) { %w(old_dir1.d old_dir2.d) }
+      let(:new_location) { 'new_dir.d' }
+
+      before :each do
+        old_location.each { |l| create_directory l }
+        move old_location, new_location
+      end
+
+      it { expect(old_location.map { |l| File.join(new_location, l) }).to all be_an_existing_directory }
+    end
+    """
+    When I run `rspec`
+    Then the specs should all pass
+
+  Scenario: Multiple sources and destination is file
+    Given a file named "spec/cd_spec.rb" with:
+    """ruby
+    require 'spec_helper'
+
+    RSpec.describe 'Move', :type => :aruba do
+      let(:old_location) { %w(old_dir1.d old_dir2.d) }
+      let(:new_location) { 'new_file.txt' }
+
+      before :each do
+        old_location.each { |l| create_directory l }
+        touch new_location
+      end
+
+      it { expect { move old_location, new_location }.to raise_error ArgumentError, /Multiple sources/ }
+    end
+    """
+    When I run `rspec`
+    Then the specs should all pass

data/features/cli/console.feature

@@ -11,7 +11,7 @@ Feature: Aruba Console
     aruba:001:0>
     """
 
-  @ignore-platform-java
+  @unsupported-on-platform-java
   Scenario: Show help
     Given I run `aruba console` interactively
     And I type "aruba_help"
@@ -29,7 +29,7 @@ Feature: Aruba Console
     Documentation:
     """
 
-  @ignore-platform-java
+  @unsupported-on-platform-java
   Scenario: Show methods
     Given I run `aruba console` interactively
     And I type "aruba_methods"
@@ -43,7 +43,7 @@ Feature: Aruba Console
     * setup_aruba
     """
 
-  @ignore-platform-java
+  @unsupported-on-platform-java
   Scenario: Has history
     Given I run `aruba console` interactively
     And I type "aruba_methods"

data/features/commands/debug_command.feature

@@ -0,0 +1,93 @@
+Feature: Debug your command in cucumber-test-run
+
+  As a developer
+  I want to use some debugger in my code and therefor need system() to execute my program
+  In order to find a bug
+
+  Background:
+    Given I use a fixture named "cli-app"
+    And the default aruba exit timeout is 60 seconds
+
+  Scenario: Can handle exit status 0
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    exit 0
+    """
+    And a file named "features/debug.feature" with:
+    """cucumber
+    Feature: Exit status in debug environment
+
+      @debug
+      Scenario: Run program with debug code
+        When I run `cli`
+        Then the exit status should be 0
+    """
+    When I successfully run `cucumber`
+    Then the features should all pass
+
+  Scenario: Can handle exit status 1
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    exit 1
+    """
+    And a file named "features/debug.feature" with:
+    """cucumber
+    Feature: Exit status in debug environment
+
+      @debug
+      Scenario: Run program with debug code
+        When I run `cli`
+        Then the exit status should be 1
+    """
+    When I successfully run `cucumber`
+    Then the features should all pass
+
+  @unsupported-on-ruby-older-193
+  Scenario: You can use a debug repl in your cli program
+
+    If you want to debug a strange error, which only occures in one of your
+    `cucumber`-tests, the `@debug`-tag becomes handy. You can add `@debug` in
+    front of your feature/scenario to make `binding.pry` or `byebug` work in
+    your program.
+
+    Please make sure, that there's a statement after the `binding.pry`-call.
+    Otherwise you might not get an interactive shell, because your program will
+    just exit.
+
+    We are going to demonstrate this using `pry`, but any other interactive
+    debugger for any other programming language should also work.
+
+    Given an executable named "bin/cli" with:
+    """ruby
+    #!/usr/bin/env ruby
+
+    $stderr.sync = true
+    $stdout.sync = true
+
+    require 'pry'
+    binding.pry
+
+    exit 0
+    """
+    And a file named "features/debug.feature" with:
+    """cucumber
+    Feature: Exit status in debug environment
+
+      @debug
+      Scenario: Run program with debug code
+        When I run `cli`
+        Then the exit status should be 0
+    """
+    When I run `cucumber` interactively
+    And I stop the command started last if output contains:
+    """
+    pry
+    """
+    Then the output should contain:
+    """
+    binding.pry
+    """

data/features/commands/environment_variables.feature

@@ -0,0 +1,64 @@
+Feature: Modify environment variables
+
+  In order to test command line applications which make use of environment variables
+  As a developer using Cucumber
+  I want to use the command environment variable step
+
+  Background:
+    Given I use a fixture named "cli-app"
+
+  Scenario: Change/Set value of arbitrary environment variable
+    Given an executable named "bin/cli" with:
+    """ruby
+    #!/usr/bin/env ruby
+
+    puts ENV['LONG_LONG_VARIABLE']
+    """
+    And a file named "features/environment_variable.feature" with:
+    """cucumber
+    Feature: Flushing output
+      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: Change the HOME-variable of current user during test using custom step
+    Given an executable named "bin/cli" with:
+    """ruby
+    #!/usr/bin/env ruby
+
+    puts File.expand_path('~/')
+    """
+    And a file named "features/home_directory.feature" with:
+    """cucumber
+    Feature: Run command with different home directory
+      Scenario: Run command
+        Given a mocked home directory
+        When I run `cli`
+        Then the output should contain "tmp/aruba"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Change the HOME-variable of current user during test using tag
+    Given an executable named "bin/cli" with:
+    """ruby
+    #!/usr/bin/env ruby
+
+    puts File.expand_path('~/')
+    """
+    And a file named "features/home_directory.feature" with:
+    """cucumber
+    Feature: Run command
+      @mocked_home_directory
+      Scenario: Run command
+        When I run `cli`
+        Then the output should contain "tmp/aruba"
+    """
+    When I run `cucumber`
+    Then the features should all pass

data/features/commands/flushing.feature

@@ -0,0 +1,74 @@
+Feature: Flushing the output of your application
+
+  In order to test processes that output a lot of data
+  As a developer using Aruba
+  I want to make sure that large amounts of output aren't buffered
+
+  Background:
+    Given I use a fixture named "cli-app"
+
+  Scenario: A little output
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    for ((c=0; c<256; c = c+1)); do 
+      echo -n "a"
+    done
+    """
+    And a file named "features/flushing.feature" with:
+    """cucumber
+    Feature: Flushing output
+      Scenario: Run command
+        When I run `cli`
+        Then the output should contain "a"
+        And the output should be 256 bytes long
+        And the exit status should be 0
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Tons of output
+    Given the default aruba exit timeout is 10 seconds
+    And an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    for ((c=0; c<65536; c = c+1)); do
+      echo -n "a"
+    done
+    """
+    And a file named "features/flushing.feature" with:
+    """cucumber
+    Feature: Flushing output
+      Scenario: Run command
+        When I run `cli`
+        Then the output should contain "a"
+        And the output should be 65536 bytes long
+        And the exit status should be 0
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  Scenario: Tons of interactive output
+    Given the default aruba exit timeout is 10 seconds
+    And an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env bash
+
+    read size; for ((c=0; c<$size; c = c+1)); do
+      echo -n "a"
+    done
+    """
+    And a file named "features/flushing.feature" with:
+    """cucumber
+    Feature: Flushing output
+      Scenario: Run command
+        When I run `cli` interactively
+        And I type "65536"
+        Then the output should contain "a"
+        And the output should be 65536 bytes long
+        And the exit status should be 0
+    """
+    When I run `cucumber`
+    Then the features should all pass

data/features/commands/interactive.feature

@@ -0,0 +1,90 @@
+Feature: Interactive process control
+
+  In order to test interactive command line applications
+  As a developer using Cucumber
+  I want to use the interactive session steps
+
+  Background:
+    Given I use a fixture named "cli-app"
+
+  @wip-jruby-java-1.6
+  Scenario: Running ruby interactively
+    Given an executable named "bin/cli" with:
+    """bash
+    #!/usr/bin/env ruby
+
+    while res = gets.chomp
+      break if res == "quit"
+      puts res.reverse
+    end
+    """
+    And a file named "features/interactive.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        When I run `cli` interactively
+        And I type "hello, world"
+        And I type "quit"
+        Then it should pass with "dlrow ,olleh"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  @posix
+  Scenario: Running a native binary interactively
+    Given a file named "features/interactive.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+      When I run `cat` interactively
+      And I type "Hello, world"
+      And I type ""
+      Then the output should contain "Hello, world"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  @posix
+  Scenario: Pipe in a file
+    Given a file named "features/interactive.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        Given a file named "test.txt" with "line1\nline2"
+        When I run `cat` interactively
+        And I pipe in the file "test.txt"
+        Then the output should contain "line1\nline2"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  @posix
+  Scenario: Close stdin stream
+    Given a file named "features/interactive.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        When I run `cat` interactively
+        And I type "Hello, world"
+        And I close the stdin stream
+        Then the output should contain "Hello, world"
+    """
+    When I run `cucumber`
+    Then the features should all pass
+
+  @posix
+  Scenario: All processes are stopped before checking for filesystem changes
+
+    See: http://github.com/aslakhellesoy/aruba/issues#issue/17 for context
+
+    Given a file named "features/interactive.feature" with:
+    """cucumber
+    Feature: Run command
+      Scenario: Run command
+        Given a directory named "rename_me"
+        When I run `mv rename_me renamed` interactively
+        Then the directory "renamed" should exist
+        And the directory "rename_me" should not exist
+    """
+    When I run `cucumber`
+    Then the features should all pass