aruba-jbb 0.2.6.3 → 0.2.6.4

data/.gitignore

@@ -14,10 +14,11 @@ tmtags
 *.swp
 
 ## PROJECT::GENERAL
+*.gem
 coverage
 rdoc
 pkg
 
 ## PROJECT::SPECIFIC
 tmp
-Gemfile.lock
+Gemfile.lock

data/History.txt

@@ -1,5 +1,13 @@
+== 0.2.6.4 jbb
+* Fix for ruby 1.9.2 change in handling StandardError objects as strings
+
+== 0.2.6.3 jbb
+* Revised documentation.
+* Added aruba-jbb and aruba_jbb library calls
+* Minor extension of do have syntax - 'do(?;es)? have'
+
 == 0.2.6.2 jbb
-* merged aslak aruba-0.2.3
+* Merged aslak aruba-0.2.3
 
 == 0.2.6 jbb
 * Altered rebase method to handle Ruby 1.9 changes to String class. (JBB)

data/README.rdoc

@@ -1,14 +1,17 @@
 = Aruba
 
-aruba-jbb is a fork of http://github.com/aslakhellesoy/aruba
+Aruba-jbb is a fork of http://github.com/aslakhellesoy/aruba and is found
+at http://byrnejb/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-jbb is a set of api methods and cucumber steps for driving out command
+line application behaviours. 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
+Aruba-jbb may also be used to test complex configuration files for third-party
 applications where the software itself may not be modified.
 
+Aruba-jbb works with Ruby-1.8.7 and Ruby-1.9.2
+
 
 == Usage
 
@@ -39,7 +42,15 @@ 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
+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, regardless of the tag, 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.
+
+This fork 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
@@ -55,14 +66,6 @@ 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.
-
 Upstream addressed the more limtied problem of locating <code>./bin</code> 
 by adding <code>@bin</code> tag which appends <code>./bin</code> to Cucumber's
 LOADPATH. This technique is supported by Aruba-jbb as well.
@@ -72,12 +75,12 @@ LOADPATH. This technique is supported by Aruba-jbb as well.
 
 Aruba once had a couple of step definitions to 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).  These were removed in 
+what Ruby version you were using to invoke Cucumber).  These were removed in 
 upstream's 0.2.2 version and are no longer present in this fork either.
 The last version of this fork having them was 0.2.6.
 
 To test against specific versions of Ruby using RVM you are advised to use
-following idiom:
+following idiom (note the comma between Ruby version numbers):
 
 <code>$ rvm 1.9.2,1.8.7 exec cucumber [flags] [arguments] </code>
 

data/aruba-jbb.gemspec

@@ -2,7 +2,7 @@
 
 Gem::Specification.new do |s|
   s.name = %q{aruba-jbb}
-  s.version = "0.2.6.3"
+  s.version = "0.2.6.4"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["Aslak Hellesøy", "David Chelimsky", "James B. Byrne"]

data/lib/aruba/api.rb

@@ -154,7 +154,7 @@ module Aruba
       if @interactive
         interactive_output
       else
-        @last_stdout + @last_stderr
+        @last_stdout.to_s + @last_stderr.to_s
       end
     end
 

data/lib/aruba-jbb.rb

@@ -0,0 +1,3 @@
+require 'pathname'
+lib_path = Pathname.new(File.dirname(__FILE__)).realpath.to_s + '/'
+require lib_path + 'aruba/cucumber_steps'

data/lib/aruba_jbb.rb

@@ -0,0 +1,3 @@
+require 'pathname'
+lib_path = Pathname.new(File.dirname(__FILE__)).realpath.to_s + '/'
+require lib_path + 'aruba/cucumber_steps'

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification 
 name: aruba-jbb
 version: !ruby/object:Gem::Version 
-  hash: 65
+  hash: 79
   prerelease: false
   segments: 
   - 0
   - 2
   - 6
-  - 3
-  version: 0.2.6.3
+  - 4
+  version: 0.2.6.4
 platform: ruby
 authors: 
 - "Aslak Helles\xC3\xB8y"
@@ -97,11 +97,13 @@ files:
 - features/output.feature
 - features/step_definitions/aruba_dev_steps.rb
 - features/support/env.rb
+- lib/aruba-jbb.rb
 - lib/aruba.rb
 - lib/aruba/api.rb
 - lib/aruba/aruba_extension_steps.rb
 - lib/aruba/cucumber.rb
 - lib/aruba/cucumber_steps.rb
+- lib/aruba_jbb.rb
 has_rdoc: true
 homepage: http://github.com/byrnejb/aruba
 licenses: []