pickled_aruba 0.1.0

data/.bundle/config

@@ -0,0 +1,2 @@
+--- 
+BUNDLE_DISABLE_SHARED_GEMS: "1"

data/.document

@@ -0,0 +1,5 @@
+README.rdoc
+lib/**/*.rb
+bin/*
+features/**/*.feature
+LICENSE

data/Gemfile

@@ -0,0 +1,11 @@
+source "http://rubygems.org"
+
+# Don't use sister dependencies no one else will have,
+# Use gems so everyone can compile the code.
+group :development do
+  gem 'cucumber', ">= 0.9.3"
+  gem 'rspec', ">= 2.0.1"
+  gem 'background_process', ">= 1.2.0"
+  gem 'jeweler', ">= 1.5.0.pre5"
+  gem 'sdoc', ">= 0.2.20"
+end

data/History.txt

@@ -0,0 +1,4 @@
+== 0.1.0
+
+Initial project based on Aruba 2.3.0
+Added case insensitive matchers.

data/LICENSE

@@ -0,0 +1,21 @@
+Aruba 2.3.0 Copyright (c) 2010 Aslak Hellesøy and David Chelimsky.
+Pickled Aruba Copyright (c) 2010 Mike Bethany.
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.rdoc

@@ -0,0 +1,55 @@
+= pickled_aruba
+
+My own branch of Aruba so I can have needed changes incorporated immediatly. I have features
+I need to add and was waiting till my first pull request was processed but it never was so I
+needed to take control. My additions so far are very minor but I need to be able to use them
+in my apps when I need them. The Aruba project managers are just to busy to actively support
+pull requests.
+
+I'll incorporate main Aruba changes as I need them.
+
+Based on Aruba 2.3.0
+
+== Description
+
+Cucumber steps for driving out command line applications. The command line application can be anything,
+a compiled C program, a Java program, a Perl script - anything.
+
+== Usage
+
+  gem install pickled_aruba
+
+Then, just require the library in one of your ruby files under <tt>features/support</tt>
+
+  require 'pickled_aruba'
+
+You now have a bunch of step definitions that you can use in your features. Look at pickled_aruba/cucumber.rb
+to see all the step definitions. Look at features/*.feature for examples (which are also testing PickledAruba
+itself).
+
+== Getting more output with tags.
+
+PickledAruba has several tags you can use to get more information. You can put these tags on individual scenarios, or on a feature. The tags are:
+
+* <tt>@announce-cmd</tt> - See what command is is run
+* <tt>@announce-stdout</tt> - See the stdout
+* <tt>@announce-stderr</tt> - See the stderr
+* <tt>@announce-dir</tt> - See the current directory
+* <tt>@announce-env</tt> - See environment variables set by PickledAruba
+* <tt>@announce</tt> - Does all of the above
+
+== Note on Patches/Pull Requests
+ 
+* Fork the project.
+* Make your feature addition or bug fix.
+* Add tests for it. This is important so I don't break it in a
+  future version unintentionally.
+* Commit, do not mess with rakefile, version, or history.
+  (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull)
+* Send me a pull request. Bonus points for topic branches.
+
+== Copyright
+
+Aruba 2.3.0 Copyright (c) 2010 Aslak Hellesøy and David Chelimsky.  
+Pickled Aruba Copyright (c) 2010 Mike Bethany.  
+See LICENSE for details.

data/Rakefile

@@ -0,0 +1,39 @@
+# -*- encoding: utf-8 -*-
+
+require 'rubygems'
+require 'rake'
+
+$:.unshift 'lib'
+require 'pickled_aruba/version'
+version = PickledAruba::Version::STRING
+
+# run "rake gemspec" to create gemspec file
+begin
+  require 'jeweler'
+  Jeweler::Tasks.new do |gem|
+    gem.name = "pickled_aruba"
+    gem.version = version
+    gem.summary = %Q{pickled_aruba-#{version}}
+    gem.description = %Q{CLI Steps for Cucumber, pickled for freshness (i.e. so I can add changes without waiting months for pulls)}
+    gem.email = "picklepumpers@gmail.com"
+    gem.homepage = "http://github.com/PicklePumpers/pickled_aruba"
+    gem.authors = ["Aslak Hellesøy", "David Chelimsky", "Mike Bethany"]
+
+    gem.add_development_dependency "cucumber", ">= 0.9.3"
+  end
+  Jeweler::GemcutterTasks.new
+rescue LoadError
+  abort "Jeweler (or a dependency) not available. Install it with: gem install jeweler"
+end
+
+begin
+  require 'cucumber/rake/task'
+  Cucumber::Rake::Task.new(:cucumber) do |t|
+    t.cucumber_opts = "features --format pretty"
+  end
+  task :cucumber => :check_dependencies
+rescue LoadError
+  abort "Cucumber is not available. Install it with: gem install cucumber"
+end
+
+task :default => :cucumber

data/config/.gitignore

@@ -0,0 +1 @@
+pickled_aruba-rvm.yml

data/features/debug.feature

@@ -0,0 +1,39 @@
+Feature: Debug
+  In order to value
+  As a role
+  I want feature
+
+@active
+Scenario Outline: Detect subset of one-line output
+    When I run "<command_line> "
+    Then the output should contain "<output_array>"
+
+Scenarios: Detect subset of one-line output table
+ | command_line                      | output_array             |
+ | ruby -e \"puts '<output_array>'\" | line1                    |
+ | ruby -e \"puts '<output_array>'\" | 'Line two' fudgy whale   |
+ | ruby -e \"puts '<output_array>'\" | fudgy 'line three' whale |
+ | ruby -e \"puts '<output_array>'\" | fudgy whale 'line four'  |
+ | ruby -e \"puts '<output_array>'\" | 'line five'              |
+ | ruby -e \"puts '<output_array>'\" | line six                 |
+
+
+#@active
+Scenario: Detect subset of one-line output, regardless of case
+  When I run "echo 'Hello World'"
+  Then the output should, regardless of case, contain "hello world"
+
+  
+#@active
+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"
+
+#@active
+Scenario: Detect subset of multiline output, regardless of case
+  When I run "ruby -e 'puts \"hello\\nworld\"'"
+  Then the output should, regardless of case, contain:
+    """
+    Hello
+    """

data/features/exit_statuses.feature

@@ -0,0 +1,21 @@
+Feature: exit statuses
+
+  In order to specify expected exit statuses
+  As a developer using Cucumber
+  I want to use the "the exit status should be" step
+
+  Scenario: exit status of 0
+    When I run "ruby -h"
+    Then the exit status should be 0
+    
+  Scenario: non-zero exit status
+    When I run "ruby -e 'exit 56'"
+    Then the exit status should be 56
+    And the exit status should not be 0
+
+  Scenario: Successfully run something
+    When I successfully run "ruby -e 'exit 0'"
+
+  Scenario: Unsuccessfully run something
+    When I do pickled_aruba I successfully run "ruby -e 'exit 10'"
+    Then pickled_aruba should fail with "Exit status was 10"

data/features/file_system_commands.feature

@@ -0,0 +1,102 @@
+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 pickled_aruba I cd to "foo/nonexistant"
+    Then pickled_aruba should fail with "tmp/pickled_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 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 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
+    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/

data/features/interactive.feature

@@ -0,0 +1,30 @@
+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
+
+  Scenario: Running ruby interactively
+    Given a file named "echo.rb" with:
+      """
+      while res = gets.chomp
+        break if res == "quit"
+        puts res.reverse
+      end
+      """
+    When I run "ruby echo.rb" interactively
+    And I type "hello, world"
+    And I type "quit"
+    Then the output should contain:
+      """
+      dlrow ,olleh
+      """
+
+  Scenario: Running a native binary interactively
+    When I run "bc -q" interactively
+    And I type "4 + 3"
+    And I type "quit"
+    Then the output should contain:
+      """
+      7
+      """

data/features/output.feature

@@ -0,0 +1,247 @@
+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 gonna work
+    """
+
+	Scenario: Run unknown command, regardless of case
+	  When I run "neverever gonna work"
+	  Then the output should, regardless of case, contain:
+	  """
+	  no such file or directory - neverever gonna work
+	  """
+
+  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 subset of one-line output, regardless of case
+    When I run "echo 'Hello World'"
+    Then the output should, regardless of case, 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"
+		 And the output should not contain "Hello World"
+
+  Scenario: Detect absence of one-line output, regardless of case
+    When I run "ruby -e 'puts \"hello world\"'"
+    Then the output should not, regardless of case, 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, regardless of case
+    When I run "ruby -e 'puts \"hello\\nworld\"'"
+    Then the output should, regardless of case, contain:
+      """
+      Hello
+      """
+
+  Scenario: Detect subset of multiline output
+    When I run "ruby -e 'puts \"hello\\nworld\"'"
+    Then the output should not contain:
+      """
+      good-bye
+      """
+     And the output should not contain:
+      """
+      Hello
+      """
+
+	Scenario: Detect subset of multiline output, regardless of case
+	  When I run "ruby -e 'puts \"hello\\nworld\"'"
+	  Then the output should not, regardless of case, 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\n"
+
+  Scenario: Detect exact one-line output, regardless of case
+    When I run "ruby -e 'puts \"Hello World\"'"
+    Then the output should, regardless of case, contain exactly "hello world\n"
+
+  Scenario: Detect exact multiline output
+    When I run "ruby -e 'puts \"hello\\nworld\"'"
+    Then the output should contain exactly:
+      """
+      hello
+      world
+
+      """
+
+  Scenario: Detect exact multiline output, regardless of case
+    When I run "ruby -e 'puts \"Hello\\nWorld\"'"
+    Then the output should, regardless of case, 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 one-line output with regex, regardless of case
+	  When I run "ruby --version"
+	  Then the output should contain "ruby"
+	  And the output should match /RuBy ([\d]+\.[\d]+\.[\d]+)(p\d+)? \(.*$/i
+
+  @announce
+  Scenario: Do not detect unwanted text in subset of one-line output with regex
+    When I run "ruby --version"
+    Then the output should contain "ruby"
+		And the output should not match /Ruby/
+    And the output should not match /python/
+
+  @announce
+  Scenario: Do not detect unwanted text in subset of one-line output with regex, regardless of case
+    When I run "ruby --version"
+    Then the output should contain "ruby"
+    And the output should not match /Python/i
+
+  @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: Detect subset of multiline output with regex, regardless of case
+    When I run "ruby -e 'puts \"Hello\\nWorld\\nExtra line1\\nExtra line2\\nIMPORTANT LINE\"'"
+    Then the output should, regardless of case, match:
+	    """
+	    he..o
+	    wor.d
+	    .*
+	    important line
+	    """
+
+  @announce
+  Scenario: Do not detect unwanted text in subset of multiline output with regex
+  When I run "ruby -e 'puts \"Hello\\nWorld\\nExtra line1\\nExtra line2\\nIMPORTANT LINE\"'"
+    Then the output should not match:
+      """
+      g..bye
+      cruel worl.d
+      .*
+      unimportant blurb
+      """
+		And the output should not match:
+	    """
+	    he..o
+	    wor.d
+	    .*
+	    important line
+	    """
+
+	@announce
+	Scenario: Do not detect unwanted text in subset of multiline output with regex, regardless of case
+	  When I run "ruby -e 'puts \"hello\\nworld\\nextra line1\\nextra line2\\nimportant line\"'"
+	  Then the output should not, regardless of case, match:
+	    """
+	    G..bye
+	    Cruel Worl.d
+	    .*
+	    EXCLAMATION!
+	    """
+
+  @announce
+  Scenario: Match passing exit status and partial output
+    When I run "ruby -e 'puts \"hello\\nworld\"'"
+    Then it should pass with:
+      """
+      hello
+      """
+
+  @announce
+  Scenario: Match passing exit status and partial output, regardless of case
+    When I run "ruby -e 'puts \"Hello\\nWorld\"'"
+    Then it should, regardless of case, pass with:
+      """
+      hello
+      """
+
+  @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
+      """
+
+  @announce-stdout
+  Scenario: Match failing exit status and partial output, regardless of case
+    When I run "ruby -e 'puts \"Hello\\nWorld\";exit 99'"
+    Then it should, regardless of case, fail with:
+      """
+      hello
+      """
+
+  @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-stdout
+	Scenario: Match failing exit status and output with regex, regardless of case
+	  When I run "ruby -e 'puts \"Hello\\nWorld\";exit 99'"
+	  Then it should, regardless of case, 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-cmd
+  Scenario: Match output in stdout, regardless of case
+    When I run "ruby -e 'puts \"Hello\\nWorld\"'"
+    Then the stdout should, regardless of case, contain "hello"
+    Then the stderr should not, regardless of case, contain "hello"
+
+  @announce-stderr
+  Scenario: Match output in stderr
+    When I run "ruby -e 'STDERR.puts \"hello\\nworld\";exit 99'"
+    Then the stderr should contain "hello"
+    Then the stdout should not contain "hello"
+
+  @announce-stderr
+  Scenario: Match output in stderr, regardless of case
+    When I run "ruby -e 'STDERR.puts \"Hello\\nWorld\";exit 99'"
+    Then the stderr should, regardless of case, contain "hello"
+    Then the stdout should not, regardless of case, contain "hello"