aruba-jbb 0.2.2

data/.document

@@ -0,0 +1,7 @@
+README.rdoc
+lib/aruba/cucumber_steps.rb
+lib/aruba/api.rb
+lib/**/*.rb
+bin/*
+features/**/*.feature
+LICENSE

data/.gitignore

@@ -0,0 +1,22 @@
+## MAC OS
+.DS_Store
+
+## TEXTMATE
+*.tmproj
+tmtags
+
+## EMACS
+*~
+\#*
+.\#*
+
+## VIM
+*.swp
+
+## PROJECT::GENERAL
+coverage
+rdoc
+pkg
+
+## PROJECT::SPECIFIC
+tmp

data/History.txt

@@ -0,0 +1,75 @@
+== 0.2.1
+
+=== Bugfixes
+* Always compare with RSpec should =~ instead of should match. This gives a diff when there is no match. (Aslak Hellesøy)
+
+== 0.2.0
+
+=== New Features
+* Added aruba.gemspec. (David Chelimsky)
+
+=== Changed features
+* Several step definitions regarding output have changed. (#1 Aslak Hellesøy)
+
+  - /^I should see "([^\"]*)"$/
+  + /^the output should contain "([^"]*)"$/
+
+  - /^I should not see "([^\"]*)"$/
+  + /^the output should not contain "([^"]*)"$/
+
+  - /^I should see:$/
+  + /^the output should contain:$/
+
+  - /^I should not see:$/
+  + /^the output should not contain:$/
+
+  - /^I should see exactly "([^\"]*)"$/
+  + /^the output should contain exactly "([^"]*)"$/
+
+  - /^I should see exactly:$/
+  + /^the output should contain exactly:$/
+
+  - /^I should see matching \/([^\/]*)\/$/
+  + /^the output should match \/([^\/]*)\/$/
+
+  - /^I should see matching:$/
+  + /^the output should match:$/
+
+== 0.1.9
+* If the GOTGEMS environment variable is set, bundler won't run (faster). (Aslak Hellesøy)
+
+== 0.1.8
+* Use // instead of "" for "I should see matching" step. (Aslak Hellesøy)
+* Replace rvm gemset character '%' with '@' for rvm 0.1.24 (#5 Ashley Moran)
+* Support gem bundler, making it easier to specify gems. (Aslak Hellesøy)
+
+== 0.1.7
+* New @announce-stderr tag (Robert Wahler)
+* New "I should see matching" steps using Regexp (Robert Wahler)
+
+== 0.1.6
+* When /^I successfully run "(.*)"$/ now prints the combined output if exit status is not 0. (Aslak Hellesøy)
+* Add bundle to list of common ruby scripts. (Aslak Hellesøy)
+
+== 0.1.5
+* Added ability to map rvm versions to a specific version with config/aruba-rvm.yml. (Aslak Hellesøy)
+* Check for presence of files. (Aslak Hellesøy)
+* Allow specification of rvm gemsets. (Aslak Hellesøy)
+* Detect ruby commands and use current ruby when rvm is not explicitly used. (Aslak Hellesøy)
+* Added support for rvm, making it possible to choose Ruby interpreter. (Aslak Hellesøy)
+* Added @announce-cmd, @announce-stdout and @announce tags, useful for seeing what's executed and outputted. (Aslak Hellesøy)
+
+== 0.1.4
+* New step definition for appending to a file (Aslak Hellesøy)
+
+== 0.1.3
+* New step definition for cd (change directory) (Aslak Hellesøy)
+
+== 0.1.2
+* Separated API from Cucumber step definitions, makes this usable without Cucumber. (Aslak Hellesøy)
+
+== 0.1.1
+* Better Regexp escaping (David Chelimsky)
+
+== 0.1.0
+* First release (David Chelimsky and Aslak Hellesøy)

data/LICENSE

@@ -0,0 +1,20 @@
+Copyright (c) 2010 Aslak Hellesøy, David Chelimsky
+
+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,163 @@
+= Aruba
+
+aruba-jbb is a fork of http://github.com/aslakhellesoy/aruba
+
+Aruba is a set of api methods and 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. 
+
+Aruba may also be used to test complex configuration files for third-party
+applications where the software itself may not be modified.
+
+Aruba provides support for testing using various Ruby versions (see below).
+
+== Usage
+
+  gem install aruba-jbb
+
+Then, just require the library in one of your Ruby files under 
+<tt>features/support</tt>
+
+  require 'aruba'  # note that aruba-jbb and aruba cannot co-exist
+
+You now have a bunch of step definitions that you can use in your features. 
+Look at aruba/cucumber_steps.rb to see all the step definitions. Look at 
+features/*.feature for examples (which are also testing Aruba itself).
+
+You should be aware that Aruba runs the application it tests and creates
+all local output in its own working directory (awd). The awd defaults to
+<tt>tmp/aruba</tt> and is purged and created by Aruba at the beginning of
+every Scenario.  However, the contents created by the last Scenario 
+are left in the awd for your inspection.
+
+If it is desired to alter the awd then this fork provides for setting the
+working directory to something else via the ARUBA_WORKING_DIR environmental
+variable.  This must be set relative to the user's cwd.
+
+This fork also contains a <tt>rebase</tt> api method which creates soft
+(symbolic) links inside aruba's working directory to directories rooted
+at the user's own current working directory (cwd). This permits the
+application to find its configuation and support files in their usual
+directories.  A string of directories to rebase also may be passed by
+setting the ARUBA_REBASE environmental variable.  These must be set relative
+to the user's cwd as well.
+
+For example:
+
+<tt>ARUBA_REBASE="bin,config,lib"</tt>
+
+This will cause Aruba to create soft links called <tt>./tmp/aruba/bin</tt>,
+<tt>./tmp/aruba/config</tt> and <tt>./tmp/aruba/lib</tt> each pointing
+to the corresponding directory in the user's cwd.
+
+This fork also provides support for a <tt>@no-aruba-tmpdir</tt> tag.  Use of
+this tag will cause Aruba to run the test application in the user's cwd
+instead of the awd.  When this tag is activated the directory contents are not
+cleared, for obvious reasons. In fact, if the awd is set to anything outside
+a directory tree containing a <tt>/tmp/</tt> portion then an error is raised
+when trying to clear the contents.  For similar reasons, when this is the case
+the <tt>rebase</tt> method also raises an error.
+
+== Ruby/RVM love
+
+Aruba has a couple of step definitions that make it easier to test your 
+Ruby command line program with specific versions of Ruby (regardless of 
+what Ruby version you're using to invoke Cucumber).
+
+This is done with the follwoing step definitions:
+
+  /^I am using rvm "([^"]*)"$/
+  /^I am using rvm gemset "([^"]*)"$/
+
+Then, if you use the step definition:
+
+  /^I run "(.*)"$/
+
+.. with a command that starts with <tt>ruby</tt>, Aruba will actually invoke 
+the Ruby version (and gemset if you specified) instead of just <tt>ruby</tt>, 
+which would be the one on your <tt>PATH</tt>, which might not be the one you 
+want. The same goes for commands starting with <tt>bundle</tt>,
+<tt>cucumber</tt>, <tt>gem</tt>, <tt>jeweler</tt>, <tt>rails</tt>, 
+<tt>rake</tt>, <tt>rspec</tt> and <tt>spec</tt> -
+they can all be run with a particular Ruby version that you specify.
+
+See features/running_ruby.feature for examples.
+
+== Getting more output with tags.
+
+Aruba has several tags you can use to see what command actually gets run 
+(useful if you're using the RVM steps), STDOUT or STDERR. You can put these 
+tags on individual scenarios, or on a feature. The tags are:
+
+* <tt>@announce-cmd</tt>
+* <tt>@announce-stdout</tt>
+* <tt>@announce-stderr</tt>
+* <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.
+
+== Note on Aruba-JBB Step Definitions
+
+This fork has extensively refactoried both the API and the Step
+Definitions.  There is some breakage with the step definitions 
+provided with the parent.  Mostly these have to do with making
+Aruba-jbb steps more specific so as to avoid anticipated collisions
+with the user's own steps.  On the other hand, most Aruba-jbb steps
+are defined as sub strings so that the subject is no longer part of
+the matcher.  For example, instead of:
+
+<tt>When /^I have a file named "([^\"]*)"$/ do |file|</tt>
+
+This fork uses:
+
+<tt>When /do have a file named "([^\"]*)"$/ do |file|</tt>
+
+So in your features you can write this:
+
+<tt> When I do have a file named "test"</tt>
+.  .  .
+<tt> When we do have a file named "test"</tt>
+.  .  .
+<tt> When they do have a file named "test"</tt>
+
+== Note on Aruba-JBB Development Testing
+
+This fork has not tested the JRuby features.  It has also disabled 
+RCov in the Rake file and removed dependencies on beta versions of
+RSpec.
+
+There is a problem with loading Ruby libraries from rake which causes
+Gherkin not to be found by Cucumber when Aruba features are exercised
+using Rake (<tt>rake</tt> or <tt>rake cucumber</tt>).  Nonetheless, all 
+features not using JRuby pass when exercised using <tt>cucumber features</tt>.  
+
+You can contact me at byrnejb@jharte-lyne.ca.  I also monitor the 
+cukes@googlegroups.com mailing list.
+
+== Note on Cucumber-Rails
+
+I have renamed this gem since it has now evolved considerably away
+from the baseline although, in the main, compatiblity between the
+the two remains quite high. Nonetheless, to avoid collisions Aruba
+must be removed (or uninstalled) if you wish to use Aruba-jbb.  
+
+However, Cucumber-Rails v0.3.2 has a dependency on Aruba which will
+result in the Aruba baseline gem being installed whenever 
+Cucumber-Rails is installed or updated.  Therefore the baseline Aruba
+gem must be removed after updating Cucumber-Rails and the dependency
+warning ignored.
+
+== Copyright
+
+Copyright (c) 2010 Aslak Hellesøy and David Chelimsky. See LICENSE for details.
+
+Portions copyright (c) 2010 James B. Byrne.  Released under the same LICENSE.

data/Rakefile

@@ -0,0 +1,52 @@
+# -*- encoding: utf-8 -*-
+require 'rubygems'
+require 'rake'
+
+begin
+  require 'jeweler'
+  Jeweler::Tasks.new do |gem|
+    gem.version = "0.2.2"
+    gem.name = "aruba-jbb"
+    gem.summary = %Q{CLI Steps for Cucumber}
+    gem.description = %Q{CLI Steps for Cucumber, hand-crafted for you in Aruba}
+    gem.email = "cukes@googlegroups.com"
+    gem.homepage = "http://github.com/byrnejb/aruba"
+    gem.authors = ["Aslak Hellesøy", "David Chelimsky", "James B. Byrne"]
+    gem.add_development_dependency "rspec", ">= 1.3.0"
+    gem.add_development_dependency "cucumber", ">= 0.8.3"
+  end
+  Jeweler::GemcutterTasks.new
+rescue LoadError
+  puts "Jeweler (or a dependency) is not available. \n" +
+         "  Install it with: gem install jeweler"
+end
+
+begin
+  require 'cucumber/rake/task'
+
+  Cucumber::Rake::Task.new do |t|
+    t.cucumber_opts = %w{--tags ~@jruby} unless defined?(JRUBY_VERSION)
+    t.rcov = false
+  end
+
+  task :cucumber => :check_dependencies
+rescue LoadError
+  task :cucumber do
+    abort "Cucumber is not available. \n" + 
+            "  In order to run features, you must install it. \n" +
+            "  gem install cucumber"
+  end
+end
+
+task :default => :cucumber
+
+require 'rake/rdoctask'
+Rake::RDocTask.new do |rdoc|
+  version = File.exist?('VERSION') ? File.read('VERSION') : ""
+
+  rdoc.rdoc_dir = 'rdoc'
+  rdoc.title = "aruba-jbb #{version}"
+  rdoc.rdoc_files.include('README*')
+  rdoc.rdoc_files.include('lib/aruba/cucumber_steps.rb')
+  rdoc.rdoc_files.include('lib/**/*.rb')
+end

data/aruba-jbb.gemspec

@@ -0,0 +1,60 @@
+# Generated by jeweler
+# DO NOT EDIT THIS FILE DIRECTLY
+# Instead, edit Jeweler::Tasks in Rakefile, and run the gemspec command
+# -*- encoding: utf-8 -*-
+
+Gem::Specification.new do |s|
+  s.name = %q{aruba-jbb}
+  s.version = "0.2.2"
+
+  s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
+  s.authors = ["Aslak Helles\303\270y", "David Chelimsky", "James B. Byrne"]
+  s.date = %q{2010-07-23}
+  s.description = %q{CLI Steps for Cucumber, hand-crafted for you in Aruba}
+  s.email = %q{cukes@googlegroups.com}
+  s.extra_rdoc_files = [
+    "LICENSE",
+     "README.rdoc"
+  ]
+  s.files = [
+    ".document",
+     ".gitignore",
+     "History.txt",
+     "LICENSE",
+     "README.rdoc",
+     "Rakefile",
+     "aruba-jbb.gemspec",
+     "config/.gitignore",
+     "features/exit_statuses.feature",
+     "features/file_system_commands.feature",
+     "features/output.feature",
+     "features/running_ruby.feature",
+     "features/step_definitions/aruba_dev_steps.rb",
+     "features/support/env.rb",
+     "lib/aruba.rb",
+     "lib/aruba/api.rb",
+     "lib/aruba/cucumber_steps.rb"
+  ]
+  s.homepage = %q{http://github.com/byrnejb/aruba}
+  s.rdoc_options = ["--charset=UTF-8"]
+  s.require_paths = ["lib"]
+  s.rubygems_version = %q{1.3.7}
+  s.summary = %q{CLI Steps for Cucumber}
+
+  if s.respond_to? :specification_version then
+    current_version = Gem::Specification::CURRENT_SPECIFICATION_VERSION
+    s.specification_version = 3
+
+    if Gem::Version.new(Gem::VERSION) >= Gem::Version.new('1.2.0') then
+      s.add_development_dependency(%q<rspec>, [">= 1.3.0"])
+      s.add_development_dependency(%q<cucumber>, [">= 0.8.3"])
+    else
+      s.add_dependency(%q<rspec>, [">= 1.3.0"])
+      s.add_dependency(%q<cucumber>, [">= 0.8.3"])
+    end
+  else
+    s.add_dependency(%q<rspec>, [">= 1.3.0"])
+    s.add_dependency(%q<cucumber>, [">= 0.8.3"])
+  end
+end
+

data/config/.gitignore

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

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" without error
+    Then the exit status should be 0
+    
+  Scenario: non-zero exit status
+    When I run "ruby -e 'exit 56'" with errors
+    Then the exit status should be 56
+    And the exit status should not be 0
+
+  Scenario: Successfully run something
+    When I run "ruby -e 'exit 0'" without error
+
+  Scenario: Unsuccessfully run something
+    When I do aruba I run "ruby -e 'exit 10'" without error step
+    Then aruba should fail with "Exit status was 10"

data/features/file_system_commands.feature

@@ -0,0 +1,115 @@
+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 I do have 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 I do have 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 I do have 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 I do have 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 I do have a file named "foo/bar/example.rb" with:
+      """
+      puts "hello world"
+      """
+    When I do aruba I cd to "foo/nonexistant" step
+    Then aruba should fail with "tmp/aruba/foo/nonexistant is not a directory"
+
+  Scenario: Check for presence of a subset of files
+    Given I do have an empty file named "lorem/ipsum/dolor"
+      And I do have an empty file named "lorem/ipsum/sit"
+      And I do have 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 I do have a directory named "foo/bar"
+      And I do have a directory named "foo/bla"
+    Then the following directories should exist:
+      | foo/bar |
+      | foo/bla |
+
+  Scenario: Check file contents
+    Given I do have 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: @aruba-tmpdir flag runs scenario in tmp/aruba
+    When I run "ruby -e \"require 'fileutils'; puts FileUtils.pwd\""
+    Then the stdout should contain "tmp/aruba"
+
+  @no-aruba-tmpdir
+  Scenario: @no-aruba-tmpdir runs scenario in cwd
+    When I run "ruby -e \"require 'fileutils'; puts FileUtils.pwd\""
+    Then the stdout should not contain "tmp/aruba"
+
+  @rebase-test @aruba-tmpdir @announce 
+  Scenario: clean_up api checks for tmp directory subtree
+    Given the rebase-test before block conditions
+    When I cd to "../../testdata"
+    Then the clean_up api method should fail
+      And output should match /outside the tmp subtree and may not be deleted/
+
+
+  @rebase-test @aruba-tmpdir @announce
+  Scenario: @rebase-test tag creates soft links in aruba working directory
+    Given the rebase-test before block conditions
+    Then the soft links should exist in the aruba working directory
+
+
+  @rebase-test @aruba-tmpdir @announce
+  Scenario: rebase api creats soft links in aruba working directory
+    Given the rebase-test before block conditions
+      And I create the cwd sub-directory named "rebase_test"
+    When I rebase the directory named "rebase_test"
+    Then "rebase_test" should have a soft link in the aruba working directory
+      And I delete the cwd sub-directory named "rebase_test"

data/features/output.feature

@@ -0,0 +1,96 @@
+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:
+    """
+    sh: neverever: command not found
+    """
+
+  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\n"
+
+  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
+      """
+
+  @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-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-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"