aruba 0.11.0.pre4 → 0.11.1

data/features/commands/environment_variables.feature

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

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

@@ -1,220 +0,0 @@
-Feature: file system commands
-
-  In order to specify commands that load files
-  As a developer using Cucumber
-  I want to create temporary files
-
-  # Scenario: create a dir
-  #   Given a directory named "foo/bar"
-  #   When I run `file foo/bar`
-  #   Then the stdout should contain "foo/bar: directory"
-
-  # Scenario: create a file
-  #   Given a file named "foo/bar/example.txt" with:
-  #     """
-  #     hello world
-  #     """
-  #   When I run `cat foo/bar/example.txt`
-  #   Then the output should contain exactly "hello world"
-
-  Scenario: a file does not exist
-    Given a file named "example.txt" does not exist
-    Then the file "example.txt" should not exist
-
-  Scenario: a directory does not exist
-    Given a directory named "example.d" does not exist
-    Then the directory "foo" should not exist
-
-  Scenario: create a fixed sized file
-    Given a 1048576 byte file named "test.txt"
-    Then a 1048576 byte file named "test.txt" should exist
-
-  Scenario: Append to a file
-    \### We like appending to files:
-    1. Disk space is cheap
-    1. It's completely safe
-
-    \### Here is a list:
-    - One
-    - Two
-
-    Given a file named "foo/bar/example.txt" with:
-      """
-      hello world
-
-      """
-    When I append to "foo/bar/example.txt" with:
-      """
-      this was appended
-
-      """
-    When I run `cat foo/bar/example.txt`
-    Then the stdout should contain "hello world"
-    And the stdout should contain "this was appended"
-
-  Scenario: Append to a new file
-    When I append to "thedir/thefile" with "x"
-    And I append to "thedir/thefile" with "y"
-    Then the file "thedir/thefile" should contain "xy"
-
-  Scenario: clean up files generated in previous scenario
-    Then the file "foo/bar/example.txt" should not exist
-
-  Scenario: change to a subdir
-    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"
-
-  Scenario: Reset current directory from previous scenario
-    When I run `pwd`
-    Then the output should match /\057tmp\057aruba$/
-
-  Scenario: Holler if cd to bad dir
-    When I do aruba I cd to "foo/nonexistant"
-    Then aruba should fail with "tmp/aruba/foo/nonexistant is not a directory"
-
-  Scenario: Check for presence of a subset of files
-    Given an empty file named "lorem/ipsum/dolor"
-    Given an empty file named "lorem/ipsum/sit"
-    Given an empty file named "lorem/ipsum/amet"
-    Then the following files should exist:
-      | lorem/ipsum/dolor |
-      | lorem/ipsum/amet  |
-
-  Scenario: Check for absence of files
-    Then the following files should not exist:
-      | lorem/ipsum/dolor |
-
-  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 absence of a single file
-    Then a file named "lorem/ipsum/dolor" should not exist
-
-  Scenario: Check for absence of a single file using a regex
-    Then a file matching %r<^ipsum> should not exist
-
-  Scenario: Check for presence of a single file using a regex
-    Given an empty file named "lorem/ipsum/dolor"
-    Then a file matching %r<dolor$> should exist
-
-  Scenario: Check for presence of a single file using a more complicated regex
-    Given an empty file named "lorem/ipsum/dolor"
-    Then a file matching %r<ipsum/dolor> should exist
-
-  Scenario: Check for presence of a subset of directories
-    Given a directory named "foo/bar"
-    Given a directory named "foo/bla"
-    Then the following directories should exist:
-      | foo/bar |
-      | foo/bla |
-
-  Scenario: check for absence of directories
-    Given a directory named "foo/bar"
-    Given a directory named "foo/bla"
-    Then the following step should fail with Spec::Expectations::ExpectationNotMetError:
-    """
-    Then the following directories should not exist:
-      | foo/bar/ |
-      | foo/bla/ |
-    """
-
-  Scenario: Check for presence of a single directory
-    Given a directory named "foo/bar"
-    Then a directory named "foo/bar" should exist
-
-  Scenario: Check for absence of a single directory
-    Given a directory named "foo/bar"
-    Then the following step should fail with Spec::Expectations::ExpectationNotMetError:
-      """
-      Then the directory "foo/bar" should not exist
-      """
-
-  Scenario: Check file contents with text
-    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"
-
-  Scenario: Check file contents with regexp
-    Given a file named "foo" with:
-      """
-      hello world
-      """
-    Then the file "foo" should match /hel.o world/
-    And the file "foo" should not match /HELLO WORLD/
-
-  Scenario: Check file contents with docstring
-    Given a file named "foo" with:
-      """
-      foo
-      bar
-      baz
-      foobar
-      """
-    Then the file "foo" should contain:
-      """
-      bar
-      baz
-      """
-
-  Scenario: Check file contents with another file
-    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"
-
-  Scenario: Remove file
-    Given a file named "foo" with:
-      """
-      hello world
-      """
-    When I remove the file "foo"
-    Then the file "foo" should not exist
-
-  Scenario: Remove directory
-    Given a directory named "foo"
-    When I remove the directory "foo"
-    Then the directory "foo" should not exist
-
-  Scenario: Just a dummy for reporting
-    Given an empty file named "a/b.txt"
-    Given an empty file named "a/b/c.txt"
-    Given an empty file named "a/b/c/d.txt"
-
-  Scenario: Change mode of empty file
-    Given an empty file named "test.txt" with mode "0666"
-    Then the mode of filesystem object "test.txt" should match "0666"
-
-  Scenario: Change mode of a directory
-    Given a directory named "test.d" with mode "0666"
-    Then the mode of filesystem object "test.d" should match "0666"
-
-  Scenario: Change mode of file
-    Given a file named "test.txt" with mode "0666" and with:
-    """
-    asdf
-    """
-    Then the mode of filesystem object "test.txt" should match "0666"
-
-  Scenario: Use a fixture
-    Given I use a fixture named "fixtures-app"
-    Then a file named "test.txt" should exist

data/features/output.feature

@@ -1,131 +0,0 @@
-Feature: All output of commands which were executed
-
-  In order to specify expected output
-  As a developer using Cucumber
-  I want to use the "the output should contain" step
-
-  Background:
-    Given I use a fixture named "cli-app"
-
-  @requires-aruba-version-1
-  Scenario: Detect output from all processes normal and interactive ones
-    Given an executable named "bin/cli1" with:
-    """
-    #!/usr/bin/env bash
-    echo 'This is cli1'
-    """
-    And an executable named "bin/cli2" with:
-    """
-    #!/usr/bin/env ruby
-
-    while input = gets do
-      break if "" == input
-      puts input
-    end
-    """
-    And a file named "features/output.feature" with:
-    """
-    Feature: Run command
-      Scenario: Run command
-        When I run `cli1`
-        When I run `cli2` interactively
-        And I type "This is cli2"
-        And I type ""
-        Then the stdout should contain exactly:
-        \"\"\"
-        This is cli1
-        \"\"\"
-        And the stdout should contain exactly:
-        \"\"\"
-        This is cli2
-        \"\"\"
-    """
-    When I run `cucumber`
-    Then the features should all pass
-
-  Scenario: Detect stdout from all processes
-    When I run `printf "hello world!\n"`
-    And I run `cat` interactively
-    And I type "hola"
-    And I type ""
-    Then the stdout should contain:
-      """
-      hello world!
-      """
-    And the stdout should contain:
-      """
-      hola
-      """
-    And the stderr should not contain anything
-
-  Scenario: Detect stderr from all processes
-    When I run `bash -c 'printf "hello world!\n" >&2'`
-    And I run `bash -c 'cat >&2 '` interactively
-    And I type "hola"
-    And I type ""
-    Then the stderr should contain:
-    """
-    hello world!
-    """
-    And the stderr should contain:
-    """
-    hola
-    """
-    And the stdout should not contain anything
-
-  Scenario: Detect stderr from all processes (deprecated)
-    When I run `bash -c 'printf "hello world!\n" >&2'`
-    And I run `bash -c 'cat >&2 '` interactively
-    And I type "hola"
-    And I type ""
-    Then the stderr should contain:
-    """
-    hello world!
-    hola
-    """
-    And the stdout should not contain anything
-
-  Scenario: Detect output from named source
-    When I run `printf 'simple'`
-    And I run `cat` interactively
-    And I type "interactive"
-    And I type ""
-    Then the output from "printf 'simple'" should contain "simple"
-    And the output from "printf 'simple'" should contain exactly "simple"
-    And the output from "printf 'simple'" should contain exactly:
-      """
-      simple
-      """
-    And the output from "cat" should not contain "simple"
-
-  Scenario: Detect stdout from named source
-    When I run `printf 'hello'`
-    And I run `printf 'goodbye'`
-    Then the stdout from "printf 'hello'" should contain "hello"
-    And the stdout from "printf 'hello'" should contain exactly "hello"
-    And the stdout from "printf 'hello'" should contain exactly:
-      """
-      hello
-      """
-    And the stderr from "printf 'hello'" should not contain "hello"
-    And the stdout from "printf 'goodbye'" should not contain "hello"
-
-  Scenario: Detect stderr from named source
-    When I run `bash -c 'printf hello >&2'`
-    And I run `printf goodbye`
-    Then the stderr from "bash -c 'printf hello >&2'" should contain "hello"
-    And the stderr from "bash -c 'printf hello >&2'" should contain exactly "hello"
-    And the stderr from "bash -c 'printf hello >&2'" should contain exactly:
-      """
-      hello
-      """
-    And the stdout from "bash -c 'printf hello >&2'" should not contain "hello"
-    And the stderr from "printf goodbye" should not contain "hello"
-
-  Scenario: Detect second output from named source with custom name
-    When I set the environment variable "ARUBA_TEST_VAR" to "first"
-    And I run `bash -c 'printf $ARUBA_TEST_VAR'`
-    Then the output from "bash -c 'printf $ARUBA_TEST_VAR'" should contain "first"
-    When I set the environment variable "ARUBA_TEST_VAR" to "second"
-    And I run `bash -c 'printf $ARUBA_TEST_VAR'`
-    Then the output from "bash -c 'printf $ARUBA_TEST_VAR'" should contain "second"