cuken 0.1.13 → 0.1.15

data/features/command_examples/file_system_commands.feature

@@ -0,0 +1,128 @@
+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 `ruby -e "puts test ?d, 'foo'"`
+    Then the stdout should contain "true"
+  
+  Scenario: create a file
+    Given a file named "foo/bar/example.rb" with:
+      """
+      puts "hello world"
+      """
+    When I run `ruby foo/bar/example.rb`
+    Then the output should contain "hello world"
+
+  Scenario: append to a file
+    Given a file named "foo/bar/example.rb" with:
+      """
+      puts "hello world"
+      """
+    When I append to "foo/bar/example.rb" with:
+      """
+      puts "this was appended"
+      """
+    When I run `ruby foo/bar/example.rb`
+    Then the output should contain "hello world"
+    And the output should contain "this was appended"
+
+  Scenario: clean up files generated in previous scenario
+    When I run `ruby foo/bar/example.rb`
+    Then the exit status should be 1
+    And the output should contain "No such file or directory -- foo/bar/example.rb"
+  
+  Scenario: change to a subdir
+    Given a file named "foo/bar/example.rb" with:
+      """
+      puts "hello world"
+      """
+    When I cd to "foo/bar"
+    And I run `ruby example.rb`
+    Then the output should contain "hello world"
+
+  Scenario: Reset current directory from previous scenario
+    When I run `ruby example.rb`
+    Then the exit status should be 1
+
+  Scenario: Holler if cd to bad dir
+    Given a file named "foo/bar/example.rb" with:
+      """
+      puts "hello world"
+      """
+    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 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 a directory named "foo/bar" should not exist
+      """
+
+  Scenario: Check file contents
+    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: Remove file
+    Given a file named "foo" with:
+      """
+      hello world
+      """
+    When I remove the file "foo"
+    Then the file "foo" should not exist

data/features/command_examples/flushing.feature

@@ -0,0 +1,24 @@
+Feature: Flushing output
+
+  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
+
+  Scenario: A little output
+    When I run `ruby -e 'puts :a.to_s * 256'`
+    Then the output should contain "a"
+    And the output should be 256 bytes long
+    And the exit status should be 0
+
+  Scenario: Tons of output
+    When I run `ruby -e 'puts :a.to_s * 65536'`
+    Then the output should contain "a"
+    And the output should be 65536 bytes long
+    And the exit status should be 0
+
+  Scenario: Tons of interactive output
+    When I interactively run `ruby -e 'len = gets.chomp; puts :a.to_s * len.to_i'`
+    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

data/features/command_examples/interactive.feature

@@ -0,0 +1,57 @@
+@announce
+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
+  @ssh_remote
+  Scenario: Running ruby interactively
+    Given the file "echo.rb" contains:
+      """
+      while res = gets.chomp
+        break if res == "quit"
+        puts res.reverse
+      end
+      """
+    When I interactively run `ruby echo.rb`
+    And I type "hello, world"
+    And I type "quit"
+    Then the output contains:
+      """
+      dlrow ,olleh
+      """
+
+  Scenario: Running a native binary interactively
+    When I interactively run `bc -q`
+    And I type "4 + 3"
+    And I type "quit"
+    Then the output should contain:
+      """
+      7
+      """
+
+  Scenario: Running interactively in a directory outside Aruba's scratch
+    When I interactively run `echo 'correct' >discovered.txt` in "/tmp"
+    When I run `cat /tmp/discovered.txt`
+    Then the output contains:
+      """
+      correct
+      """
+     And the file "discovered.txt" does not exist
+
+  Scenario: Running successfully in a directory outside Aruba's scratch
+    When I successfully run `echo 'correct2' >discovered.txt` in "~/tmp/"
+    When I run `cat ~/tmp/discovered.txt`
+    Then the output contains:
+      """
+      correct2
+      """
+     And the file "discovered.txt" does not exist
+
+  Scenario: Stop processes before checking for filesystem changes 
+    See: http://github.com/aslakhellesoy/aruba/issues#issue/17 for context
+
+    Given a directory named "rename_me"
+    When I interactively run `mv rename_me renamed`
+    Then a directory named "renamed" should exist
+    And a directory named "rename_me" should not exist

data/features/command_examples/no_clobber.feature

@@ -0,0 +1,41 @@
+Feature: No clobber
+
+  By default Aruba removes its scratch directory before
+  every scenario. This isn't always the right thing
+  to do, especially when the path to the default directory
+  has been changed. Use @no-clobber to stop Aruba from
+  cleaning up after itself.
+
+  Scenario: Change the filesystem
+    Given a directory named "foo/bar"
+    And a file named "foo/bar/baz.txt" with:
+      """
+      I don't want to die!
+      """
+
+  @no-clobber
+  Scenario: Verify nothing was clobbered
+    Then a file named "foo/bar/baz.txt" should exist
+    And the file "foo/bar/baz.txt" should contain exactly:
+      """
+      I don't want to die!
+      """
+
+  Scenario: Cleanup and verify the previous scenario
+    Then a file named "foo/bar/baz.txt" should not exist
+
+  # use bash or ruby due to GH issue #69
+  Scenario: Do not change the filesystem
+    Given I successfully run `bash -c 'echo "I will survive!" >baz.txt'` in "/tmp/foo/bar"
+     When I run `cat baz.txt` in "/tmp/foo/bar"
+     Then the output should contain "I will survive!"
+
+  Scenario: Once more verify nothing was clobbered
+    Given I run `cat baz.txt` in "/tmp/foo/bar"
+    Then the output should contain "I will survive!"
+
+  Scenario: Adults cleanup after themselves
+    Given I run `rm baz.txt` in "/tmp/foo/bar"
+     When I run `cat baz.txt` in "/tmp/foo/bar"
+    Then the output should not contain "I will survive!"
+

data/features/command_examples/output.feature

@@ -0,0 +1,205 @@
+Feature: Output
+
+  In order to specify expected output
+  As a developer using Cucumber
+  I want to use the "the output should contain" step
+
+  Scenario: Run unknown command
+    When I run `neverever gonna work`
+    Then the output should contain:
+      """
+      No such file or directory - neverever
+      """
+
+  Scenario: Detect subset of one-line output
+    When I run `ruby -e 'puts \"hello world\"'`
+    Then the output should contain "hello world"
+
+  Scenario: Detect subset of one-line output
+    When I run `echo 'hello world'`
+    Then the output should contain "hello world"
+
+  Scenario: Detect absence of one-line output
+    When I run `ruby -e 'puts \"hello world\"'`
+    Then the output should not contain "good-bye"
+
+  Scenario: Detect subset of multiline output
+    When I run `ruby -e 'puts \"hello\\nworld\"'`
+    Then the output should contain:
+      """
+      hello
+      """
+
+  Scenario: Detect subset of multiline output
+    When I run `ruby -e 'puts \"hello\\nworld\"'`
+    Then the output should not contain:
+      """
+      good-bye
+      """
+
+  Scenario: Detect exact one-line output
+    When I run `ruby -e 'puts \"hello world\"'`
+    Then the output should contain exactly:
+      """
+      hello world
+      
+      """
+
+  Scenario: Detect exact multiline output
+    When I run `ruby -e 'puts "hello\nworld"'`
+    Then the output should contain exactly:
+      """
+      hello
+      world
+
+      """
+
+  @announce
+  Scenario: Detect subset of one-line output with regex
+    When I run `ruby --version`
+    Then the output should contain "ruby"
+    And the output should match /ruby ([\d]+\.[\d]+\.[\d]+)(p\d+)? \(.*$/
+
+  @announce
+  Scenario: Detect subset of multiline output with regex
+    When I run `ruby -e 'puts "hello\nworld\nextra line1\nextra line2\nimportant line"'`
+    Then the output should match:
+      """
+      he..o
+      wor.d
+      .*
+      important line
+      """
+
+  @announce
+  Scenario: Match passing exit status and partial output
+    When I run `ruby -e 'puts "hello\nworld"'`
+    Then it should pass with:
+      """
+      hello
+      """
+
+  Scenario: Match passing exit status and exact output
+    When I run `ruby -e 'puts "hello\nworld"'`
+    Then it should pass with exactly:
+      """
+      hello
+      world
+
+      """
+
+  @announce-stdout
+  Scenario: Match failing exit status and partial output
+    When I run `ruby -e 'puts \"hello\\nworld\";exit 99'`
+    Then it should fail with:
+      """
+      hello
+      """
+
+  Scenario: Match failing exit status and exact output
+    When I run `ruby -e 'puts "hello\nworld";exit 99'`
+    Then it should fail with exactly:
+      """
+      hello
+      world
+
+      """
+
+  @announce-stdout
+  Scenario: Match failing exit status and output with regex
+    When I run `ruby -e 'puts \"hello\\nworld\";exit 99'`
+    Then it should fail with regex:
+      """
+      hello\s*world
+      """
+
+  @announce-cmd
+  Scenario: Match output in stdout
+    When I run `ruby -e 'puts \"hello\\nworld\"'`
+    Then the stdout should contain "hello"
+    Then the stderr should not contain "hello"
+
+  @announce
+  Scenario: Match output on several lines
+    When I run `ruby -e 'puts %{GET /}'`
+    Then the stdout should contain:
+      """
+      GET /
+      """
+
+  Scenario: Match output on several lines using quotes
+    When I run `ruby -e 'puts %{GET "/"}'`
+    Then the stdout should contain:
+      """
+      GET "/"
+      """
+
+  Scenario: Match output in stdout
+    When I run `ruby -e 'puts \"hello\\nworld\"'`
+    Then the stdout should contain "hello"
+    Then the stderr should not contain "hello"
+
+  Scenario: Detect output from all processes
+    When I run `ruby -e 'puts \"hello world!\"'`
+    And I interactively run `ruby -e 'puts gets.chomp.reverse'`
+    And I type "hello"
+    Then the output should contain exactly:
+      """
+      hello world!
+      olleh
+
+      """
+
+  Scenario: Detect stdout from all processes
+    When I run `ruby -e 'puts \"hello world!\"'`
+    And I interactively run `ruby -e 'puts gets.chomp.reverse'`
+    And I type "hello"
+    Then the stdout should contain:
+      """
+      hello world!
+      olleh
+      """
+    And the stderr should not contain:
+      """
+      hello world!
+      olleh
+      """
+
+  Scenario: Detect stderr from all processes
+    When I run `ruby -e 'STDERR.puts \"hello world!\"'`
+    And I interactively run `ruby -e 'STDERR.puts gets.chomp.reverse'`
+    And I type "hello"
+    Then the stderr should contain:
+      """
+      hello world!
+      olleh
+      """
+    And the stdout should not contain:
+      """
+      hello world!
+      olleh
+      """
+
+  Scenario: Detect output from named source
+    When I run `ruby -e 'puts :simple'`
+    And I interactively run `ruby -e 'puts gets.chomp'`
+    And I type "interactive"
+    Then the output from "ruby -e 'puts :simple'" should contain "simple"
+    And the output from "ruby -e 'puts gets.chomp'" should not contain "simple"
+
+  Scenario: Detect stdout from named source
+    When I run `ruby -e 'puts :hello'`
+    And I run `ruby -e 'puts :goodbye'`
+    Then the stdout from "ruby -e 'puts :hello'" should contain "hello"
+    And the stderr from "ruby -e 'puts :hello'" should not contain "hello"
+    And the stdout from "ruby -e 'puts :goodbye'" should not contain "hello"
+
+  Scenario: Detect stderr from named source
+    When I run `ruby -e 'STDERR.puts :hello'`
+    And I run `ruby -e 'puts :goodbye'`
+    Then the stderr from "ruby -e 'STDERR.puts :hello'" should contain "hello"
+    And the stdout from "ruby -e 'STDERR.puts :hello'" should not contain "hello"
+    And the stderr from "ruby -e 'puts :goodbye'" should not contain "hello"
+
+  @wip
+  Scenario: Detect output from named source with custom name

data/features/command_steps/command_steps.feature

@@ -8,61 +8,68 @@ Feature: Command steps
     Given that "cuken/cmd" has been required
 
   Scenario: Command execution
-    Then these steps are defined for "cuken/cucumber/cmd.rb":
-      | step                                                   |
-      |I run `([^`]*)`                                         |
-      |I run `([^`]*)` interactively                           |
-      |I successfully run `([^`]*)`                            |
-      |I type "([^"]*)"                                        |
+    Then these steps are defined for "cuken/cucumber/cmd/execution.rb":
+         | step                                                   |
+         |I run `([^`]*)`                                         |
+         |I run `([^`]*)` in "([^"]*)"                            |
+         |I interactively run `([^`]*)`                           |
+         |I interactively run `([^`]*)` in "([^"]*)"              |
+         |I successfully run `([^`]*)`                            |
+         |I successfully run `([^`]*)` in "([^"]*)"               |
+         |I type "([^"]*)"                                        |
 
   Scenario: Command exit status
-    Then these steps are defined for "cuken/cucumber/cmd.rb":
-      | step                                                   |
-      |the exit status should be (\d+)                         |
-      |the exit status should not be (\d+)                     |
+    Then these steps are defined for "cuken/cucumber/cmd/exit_status.rb":
+         | step                                                   |
+         |the exit status should be (\d+)                         |
+         |the exit status should not be (\d+)                     |
 #    Pending:
 #    https://rspec.lighthouseapp.com/projects/16211-cucumber/tickets/707-element-size-differs-2-should-be-1-indexerror
 #      |it should (pass|fail) with:                             |
 #      |it should (pass|fail) with exactly:                     |
 #      |it should (pass|fail) with regexp?:                     |
 
-  Scenario: Command output (stdout+stderr)
-    Then these steps are defined for "cuken/cucumber/cmd.rb":
+  Scenario: All output (stdout+stderr) per command
+    Then these steps are defined for "cuken/cucumber/output/cmd.rb":
+         | step                                                |
+         |the output from "([^"]*)" contains exactly:          |
+         |the output from "([^"]*)" does not contain exactly:  |
+         |the output from "([^"]*)" contains:                  |
+         |the output from "([^"]*)" does not contain:          |
+         |the output from "([^"]*)" contains "([^"]*)"         |
+         |the output from "([^"]*)" does not contain "([^"]*)" |
+
+  Scenario: All output (stdout+stderr) for all commands
+    Then these steps are defined for "cuken/cucumber/output/all.rb":
       | step                                                   |
-      |the output from "(.*)" contains exactly:                |
-      |the output from "([^"]*)" does not contain exactly:     |
-      |the output from "([^"]*)" contains:                     |
-      |the output from "([^"]*)" does not contain:             |
-      |the output from "([^"]*)" should contain "([^"]*)"      |
-      |the output from "([^"]*)" should not contain "([^"]*)"  |
-      |the output should contain "([^"]*)"                     |
-      |the output should contain:                              |
-      |the output should contain exactly "([^"]*)"             |
-      |the output should contain exactly:                      |
-      |the output should match \/([^\/]*)\/                    |
-      |the output should match:                                |
-      |the output should not contain "([^"]*)"                 |
-      |the output should not contain:                          |
+      |the output contains "([^"]*)"                     |
+      |the output contains:                              |
+      |the output contains exactly "([^"]*)"             |
+      |the output contains exactly:                      |
+      |the output does not contain "([^"]*)"                 |
+      |the output does not contain:                          |
+      |the output matches \/([^\/]*)\/                    |
+      |the output matches:                                |
 
   Scenario: Command stderr
-    Then these steps are defined for "cuken/cucumber/cmd.rb":
+    Then these steps are defined for "cuken/cucumber/output/stderr.rb":
       | step                                                   |
-      |the stderr from "([^"]*)" should contain "([^"]*)"      |
-      |the stderr from "([^"]*)" should not contain "([^"]*)"  |
-      |the stderr should contain "([^"]*)"                     |
-      |the stderr should contain:                              |
-      |the stderr should contain exactly:                      |
-      |the stderr should not contain "([^"]*)"                 |
-      |the stderr should not contain:                          |
+      |the stderr from "([^"]*)" contains "([^"]*)"      |
+      |the stderr from "([^"]*)" does not contain "([^"]*)"  |
+      |the stderr contains "([^"]*)"                     |
+      |the stderr contains:                              |
+      |the stderr contains exactly:                      |
+      |the stderr does not contain "([^"]*)"                 |
+      |the stderr does not contain:                          |
 
   Scenario: Command stdout
-    Then these steps are defined for "cuken/cucumber/cmd.rb":
+    Then these steps are defined for "cuken/cucumber/output/stdout.rb":
       | step                                                   |
-      |the stdout from "([^"]*)" should contain "([^"]*)"      |
-      |the stdout from "([^"]*)" should not contain "([^"]*)"  |
-      |the stdout should contain "([^"]*)"                     |
-      |the stdout should contain:                              |
-      |the stdout should contain exactly:                      |
-      |the stdout should not contain "([^"]*)"                 |
-      |the stdout should not contain:                          |
+      |the stdout from "([^"]*)" contains "([^"]*)"      |
+      |the stdout from "([^"]*)" does not contain "([^"]*)"  |
+      |the stdout contains "([^"]*)"                     |
+      |the stdout contains:                              |
+      |the stdout contains exactly:                      |
+      |the stdout does not contain "([^"]*)"                 |
+      |the stdout does not contain:                          |
 

data/features/file_examples/files.feature

@@ -28,7 +28,7 @@ Feature: Examining files
 
   @steps
   Scenario: Mtime
-    Given an empty file named "foo.file"
+    Given the file "foo.file" contains nothing
       And we record the a-mtime of "foo.file"
       And I run `sleep 1`
       And I run `touch -m foo.file`
@@ -36,7 +36,7 @@ Feature: Examining files
 
   @steps
   Scenario: File contents
-    When I write to "monkeytest.file" with:
+    When I write to "monkeytest.file":
     """
     monkeypants
     monkeyshorts
@@ -45,7 +45,7 @@ Feature: Examining files
 
   @steps
   Scenario: File contents exact match
-    When I write to "monkeytest.file" with:
+    When I write to "monkeytest.file":
     """
     monkeypants
     monkeyshorts
@@ -58,7 +58,7 @@ Feature: Examining files
 
     """
   Scenario: File contents multiple matches
-    When I write to "monkeytest.file" with:
+    When I write to "monkeytest.file":
     """
     monkeypants
     monkeyshorts
@@ -80,7 +80,7 @@ Feature: Examining files
 
   @steps
   Scenario: Directory exists
-    When I run "mkdir -p dirtest"
+    When I run `mkdir -p dirtest`
     Then the directory "dirtest" exists
 
   @steps

data/features/git_examples/git_clone.feature

@@ -0,0 +1,33 @@
+@announce @git_quick
+Feature: Git cloning
+  In order to manage application and configuration code using Git
+  As an Administrator
+  I want to clone Git Repositories
+
+  Background:
+    Given a default Git repository in "ckbk/scratch/myapp"
+
+  Scenario: Clone from a Git repository
+    Given Explanation: Next we step up two levels to escape Aruba's working folder
+      And the Git repository "./../../features/data/repositories/cookbooks/hosts/.git"
+     When I clone the remote Git repository branch "master" to "ckbk/scratch/myapp/cookbooks/hosts"
+     Then the local Git repository exists
+
+  Scenario: Clone a single Repository from a Git URI
+    Given the Git URI "git://github.com/cookbooks/"
+     When I clone the Repository "hosts" branch "master" to "ckbk/scratch/myapp/cookbooks/hosts2"
+     Then the local Git repository exists
+
+  Scenario: Clone multiple Repositories from a Git URI
+    Given the Git URI "git://github.com/cookbooks/"
+     When I clone the Repositories:
+     | repo     | branch | tag       | ref        | destination                         |
+     | hosts    |        | 37s.0.1.0 |            | ckbk/scratch/myapp/cookbooks/hosts3 |
+     | users    | 37s    |           |            | ckbk/scratch/myapp/cookbooks/users  |
+     | xml      | master |           | b7a11ea4eb | ckbk/scratch/myapp/cookbooks/xml    |
+      And these local Repositories exist:
+     | repo                                  |
+     | ckbk/scratch/myapp/cookbooks/hosts3   |
+     | ckbk/scratch/myapp/cookbooks/users    |
+     | ckbk/scratch/myapp/cookbooks/xml      |
+

data/features/ssh_examples/ssh.feature

@@ -14,7 +14,7 @@ Feature: Password-less SSH
 
   Scenario: Aruba steps for remote commands via password-less SSH access
     Given I successfully run "ssh cuken 'echo Supercalifragilisticexpialidocious;'"
-    Then the output should contain "Supercalifragilisticexpialidocious"
+    Then the output contains "Supercalifragilisticexpialidocious"
 
   Scenario: Batch initialize password-less SSH access
     When I initialize password-less SSH access for:
@@ -23,4 +23,13 @@ Feature: Password-less SSH
       | :default  | localhost  | `echo cuken` | 22          |
       | :default  | :default   | :default     | :default    |
     And I successfully run `ssh cuken 'echo Supercalifragilisticexpialidocious;'`
-    Then the output should contain "Supercalifragilisticexpialidocious"
+    Then the output contains "Supercalifragilisticexpialidocious"
+
+    Scenario: Initialize interactive password-less SSH access
+      When I interactively SSH to:
+        | user      | hostname   | name         | port        |
+        | :default  | :default   | :default     | :default    |
+      And I type "echo $SSH_CLIENT"
+      And I type "echo $SSH_CONNECTION"
+      Then I type "exit"
+       And the output contains "..."