gemrage 0.0.0

data/vendor/ruby/1.8/gems/rspec-core-2.0.0/Rakefile

@@ -0,0 +1,72 @@
+require "bundler"
+Bundler.setup
+Bundler::GemHelper.install_tasks
+
+require "rake"
+require "yaml"
+
+require "rake/rdoctask"
+require "rspec/core/rake_task"
+require "rspec/core/version"
+require "cucumber/rake/task"
+
+class Cucumber::Rake::Task::ForkedCucumberRunner
+  # When cucumber shells out, we still need it to run in the context of our
+  # bundle.
+  def run
+    sh "bundle exec #{RUBY} " + args.join(" ")
+  end
+end
+
+task :cleanup_rcov_files do
+  rm_rf 'coverage.data'
+end
+
+desc "Run all examples"
+RSpec::Core::RakeTask.new(:spec) do |t|
+  t.rspec_path = 'bin/rspec'
+  t.rspec_opts = %w[--color]
+end
+
+Cucumber::Rake::Task.new(:cucumber)
+
+namespace :spec do
+  desc "Run all examples using rcov"
+  RSpec::Core::RakeTask.new :rcov => :cleanup_rcov_files do |t|
+    t.rcov = true
+    t.rcov_opts =  %[-Ilib -Ispec --exclude "gems/*,features"]
+    t.rcov_opts << %[--text-report --sort coverage --no-html --aggregate coverage.data]
+  end
+end
+
+namespace :cucumber do
+  desc "Run cucumber features using rcov"
+  Cucumber::Rake::Task.new :rcov => :cleanup_rcov_files do |t|
+    t.cucumber_opts = %w{--format progress}
+    t.rcov = true
+    t.rcov_opts =  %[-Ilib -Ispec --exclude "gems/*,features"]
+    t.rcov_opts << %[--text-report --sort coverage --aggregate coverage.data]
+  end
+end
+
+task :default => [:spec, :cucumber]
+
+task :clobber do
+  rm_rf 'pkg'
+  rm_rf 'tmp'
+  rm_rf 'coverage'
+end
+
+desc "Push cukes to relishapp using the relish-client-gem"
+task :relish, :version do |t, args|
+  raise "rake relish[VERSION]" unless args[:version]
+  sh "bundle exec relish --organization rspec --project rspec-core -v #{args[:version]} push"
+end
+
+Rake::RDocTask.new do |rdoc|
+  rdoc.rdoc_dir = 'rdoc'
+  rdoc.title = "rspec-core #{RSpec::Core::Version::STRING}"
+  rdoc.rdoc_files.include('README*')
+  rdoc.rdoc_files.include('lib/**/*.rb')
+end
+

data/vendor/ruby/1.8/gems/rspec-core-2.0.0/Upgrade.markdown

@@ -0,0 +1,235 @@
+# Upgrade to rspec-core-2.0
+
+## What's changed since RSpec-1
+
+### rspec command
+
+The command to run specs is now `rspec` instead of `spec`.
+
+    rspec ./spec
+
+#### Co-habitation of rspec-1 and rspec-2
+
+Early beta versions of RSpec-2 included a `spec` command, which conflicted with
+the RSpec-1 `spec` command because RSpec-1's was installed by the rspec gem,
+while RSpec-2's is installed by the rspec-core gem.
+
+If you installed one of these early versions, the safest bet is to uninstall
+rspec-1 and rspec-core-2, and then reinstall both. After you do this, you will
+be able to run rspec-2 like this:
+
+    `rspec ./spec`
+
+... and rspec-1 like this:
+
+    `spec _1.3.1_ ./spec`
+
+Rubygems inspects the first argument to any gem executable to see if it's
+formatted like a version number surrounded by underscores. If so, it uses that
+version (e.g.  `1.3.1`). If not, it uses the most recent version (e.g.
+`2.0.0`).
+
+### rake task
+
+The RSpec rake task has moved to:
+
+    'rspec/core/rake_task'
+
+RCov options are now set directly on the Rake task:
+
+    RSpec::Core::RakeTask.new(:rcov) do |t|
+      t.rcov_opts =  %q[--exclude "spec"]
+    end
+
+In RSpec-1, the rake task would read in rcov options from an `rcov.opts`
+file. This is ignored by RSpec-2.
+
+### autotest
+
+RSpec-2 works with autotest as follows:
+
+    rspec --configure autotest
+
+This adds `./autotest/discover.rb` with:
+
+    Autotest.add_discovery { "rspec2" }
+
+Now, on the command line just type:
+
+    autotest
+
+Or, if you're using bundler:
+
+    bundle exec autotest
+
+The `autospec` command is a thing of the past. 
+
+### RSpec is the new Spec
+
+The root namespace (top level module) is now `RSpec` instead of `Spec`, and
+the root directory under `lib` within all of the `rspec` gems is `rspec` instead of `spec`.
+
+### Configuration
+
+Typically in `spec/spec_helper.rb`, configuration is now done like this:
+
+    RSpec.configure do |c|
+      # ....
+    end
+
+### .rspec
+
+Command line options can be persisted in a `.rspec` file in a project. You
+can also store a `.rspec` file in your home directory (`~/.rspec`) with global
+options. Precedence is:
+
+    command line
+    ./.rspec
+    ~/.rspec
+
+### Bones
+
+Bones produces a handy little Rakefile to provide several services including
+running specs. The current version (3.4.7) still assumes RSpec-1. To bring its
+Rakefile into conformance with RSpec-2 a few changes are necessary.
+
+1.  The require line has changed to `require 'spec/rake/spectask'`
+
+2.  The `spec_opts` accessor has been deprecated in favor of `rspec_opts`. Also,
+    the `rspec` command no longer supports the `--options` command line option
+    so the options must be embedded directly in the Rakefile, or stored in the
+    `.rspec` files mentioned above.
+
+3.  The `spec_files` accessor has been replaced by `pattern`.
+
+Here is a complete example:
+
+    # rspec-1
+    Spec::Rake::SpecTask.new do |t|
+      t.spec_opts = ['--options', "\"spec/spec.opts\""]
+      t.spec_files = FileList['spec/**/*.rb']
+    end
+
+becomes:
+
+    # rspec-2
+    RSpec::Core::RakeTask.new do |t|
+      t.rspec_opts = ["-c", "-f progress", "-r ./spec/spec_helper.rb"]
+      t.pattern = 'spec/**/*_spec.rb'
+    end
+
+### `context` is no longer a top-level method
+
+We removed `context` from the main object because it was creating conflicts with
+IRB and some users who had `Context` domain objects. `describe` is still there,
+so if you want to use `context` at the top level, just alias it:
+
+    alias :context :describe
+
+Of course, you can still use `context` to declare a nested group:
+
+    describe "something" do
+      context "in some context" do
+        it "does something" do
+          # ...
+        end
+      end
+    end
+
+### `$KCODE` no longer set implicitly to `'u'`
+
+In RSpec-1, the runner set `$KCODE` to `'u'`, which impacts, among other
+things, the behaviour of Regular Expressions when applied to non-ascii
+characters. This is no longer the case in RSpec-2.
+
+## What's new
+
+### Runner
+
+The new runner for rspec-2 comes from Micronaut.
+
+### Metadata!
+
+In rspec-2, every example and example group comes with metadata information
+like the file and line number on which it was declared, the arguments passed to
+`describe` and `it`, etc.  This metadata can be appended to through a hash
+argument passed to `describe` or `it`, allowing us to pre and post-process
+each example in a variety of ways.
+
+### Filtering
+
+The most obvious use is for filtering the run. For example:
+
+    # in spec/spec_helper.rb
+    RSpec.configure do |c|
+      c.filter_run :focus => true
+    end
+
+    # in any spec file
+    describe "something" do
+      it "does something", :focus => true do
+        # ....
+      end
+    end
+
+When you run the `rspec` command, rspec will run only the examples that have
+`:focus => true` in the hash. 
+
+You can also add `run_all_when_everything_filtered` to the config:
+
+    RSpec.configure do |c|
+      c.filter_run :focus => true
+      c.run_all_when_everything_filtered = true
+    end
+
+Now if there are no examples tagged with `:focus => true`, all examples
+will be run. This makes it really easy to focus on one example for a
+while, but then go back to running all of the examples by removing that
+argument from `it`. Works with `describe` too, in which case it runs
+all of the examples in that group.
+
+The configuration will accept a lambda, which provides a lot of flexibility
+in filtering examples. Say, for example, you have a spec for functionality that
+behaves slightly differently in Ruby 1.8 and Ruby 1.9. We have that in
+rspec-core, and here's how we're getting the right stuff to run under the
+right version:
+
+    # in spec/spec_helper.rb
+    RSpec.configure do |c|
+      c.exclusion_filter = { :ruby => lambda {|version|
+        !(RUBY_VERSION.to_s =~ /^#{version.to_s}/)
+      }}
+    end
+
+    # in any spec file
+    describe "something" do
+      it "does something", :ruby => 1.8 do
+        # ....
+      end
+
+      it "does something", :ruby => 1.9 do
+        # ....
+      end
+    end
+
+In this case, we're using `exclusion_filter` instead of `filter_run` or
+`filter`, which indicate _inclusion_ filters. So each of those examples is
+excluded if we're _not_ running the version of Ruby they work with.
+
+### Shared example groups
+
+Shared example groups are now run in a nested group within the including group
+(they used to be run in the same group). Nested groups inherit `before`, `after`,
+`around`, and `let` hooks, as well as any methods that are defined in the parent
+group.
+
+This new approach provides better encapsulation, better output, and an
+opportunity to add contextual information to the shared group via a block
+passed to `it_should_behave_like`.
+
+See [features/example\_groups/shared\_example\_group.feature](http://github.com/rspec/rspec-core/blob/master/features/example_groups/shared_example_group.feature) for more information.
+
+NOTICE: The including example groups no longer have access to any of the
+methods, hooks, or state defined inside a shared group. This will break specs
+that were using shared example groups to extend the behavior of including
+groups in any way besides their intended purpose: to add examples to a group.

data/vendor/ruby/1.8/gems/rspec-core-2.0.0/autotest/discover.rb

@@ -0,0 +1,2 @@
+Autotest.add_discovery { "rspec2" }
+

data/vendor/ruby/1.8/gems/rspec-core-2.0.0/bin/rspec

@@ -0,0 +1,2 @@
+#!/usr/bin/env ruby
+require 'rspec/autorun'

data/vendor/ruby/1.8/gems/rspec-core-2.0.0/cucumber.yml

@@ -0,0 +1,2 @@
+default: --require features --strict --format progress --tags ~@wip features
+wip:     --require features --tags @wip:3 --wip features

data/vendor/ruby/1.8/gems/rspec-core-2.0.0/features/README.markdown

@@ -0,0 +1,19 @@
+rspec-core provides the structure for RSpec code examples:
+
+    describe Account do
+      it "has a balance of zero when first opened" do
+        # example code goes here - for more on the 
+        # code inside the examples, see rspec-expectations 
+        # and rspec-mocks
+      end
+    end
+
+## Issues
+
+The documentation for rspec-core is a work in progress. We'll be adding
+Cucumber features over time, and clarifying existing ones.  If you have
+specific features you'd like to see added, find the existing documentation
+incomplete or confusing, or, better yet, wish to write a missing Cucumber
+feature yourself, please [submit an
+issue](http://github.com/rspec/rspec-core/issues) or a [pull
+request](http://github.com/rspec/rspec-core).

data/vendor/ruby/1.8/gems/rspec-core-2.0.0/features/command_line/configure.feature

@@ -0,0 +1,20 @@
+Feature: configure
+
+  Use the --configure option on the command line to generate configuration
+  files.
+
+  The only supported argument, so far, is "autotest", which creates an
+  autotest/discover.rb file in your project root directory.
+
+  Background:
+    Given a directory named "rspec_project"
+
+  Scenario: generate autotest directory and discover file
+    When I cd to "rspec_project"
+    And I run "rspec --configure autotest"
+    Then the following directories should exist:
+      | autotest |
+    And the following files should exist:
+      | autotest/discover.rb |
+    And the file "autotest/discover.rb" should contain "Autotest.add_discovery"
+    And the stdout should contain "autotest/discover.rb has been added"

data/vendor/ruby/1.8/gems/rspec-core-2.0.0/features/command_line/example_name_option.feature

@@ -0,0 +1,86 @@
+Feature: example name option
+
+  Use the --example (or -e) option to filter the examples to be run by name.
+
+  The argument is compiled to a Ruby Regexp, and matched against the full
+  description of the example, which is the concatenation of descriptions of the
+  group (including any nested groups) and the example.
+
+  This allows you to run a single uniquely named example, all examples with
+  similar names, all the example in a uniquely named group, etc, etc.
+
+  Background:
+    Given a file named "first_spec.rb" with:
+      """
+      describe "first group" do
+        it "first example in first group" do; end
+        it "second example in first group" do; end
+      end
+      """
+    And a file named "second_spec.rb" with:
+      """
+      describe "second group" do
+        it "first example in second group" do; end
+        it "second example in second group" do; end
+      end
+      """
+    And a file named "third_spec.rb" with:
+      """
+      describe "third group" do
+        it "first example in third group" do; end
+        context "nested group" do
+          it "first example in nested group" do; end
+          it "second example in nested group" do; end
+        end
+      end
+      """
+    And a file named "fourth_spec.rb" with:
+      """
+      describe Array do
+        describe "#length" do
+          it "is the number of items" do
+            Array.new([1,2,3]).length.should eq 3
+          end
+        end
+      end
+      """
+
+  Scenario: no matches
+    When I run "rspec . --example nothing_like_this"
+    Then the output should contain "0 examples, 0 failures"
+
+  Scenario: match on one word
+    When I run "rspec . --example example"
+    Then the output should contain "7 examples, 0 failures"
+
+  Scenario: one match in each context
+    When I run "rspec . --example 'first example'"
+    Then the output should contain "4 examples, 0 failures"
+
+  Scenario: one match in one file using just the example name
+    When I run "rspec . --example 'first example in first group'"
+    Then the output should contain "1 example, 0 failures"
+
+  Scenario: one match in one file using the example name and the group name
+    When I run "rspec . --example 'first group first example in first group'"
+    Then the output should contain "1 example, 0 failures"
+
+  Scenario: one match in one file using regexp
+    When I run "rspec . --example 'first .* first example'"
+    Then the output should contain "1 example, 0 failures"
+
+  Scenario: all examples in one group
+    When I run "rspec . --example 'first group'"
+    Then the output should contain "2 examples, 0 failures"
+
+  Scenario: one match in one file with group name
+    When I run "rspec . --example 'second group first example'"
+    Then the output should contain "1 example, 0 failures"
+
+  Scenario: all examples in one group including examples in nested groups
+    When I run "rspec . --example 'third group'"
+    Then the output should contain "3 examples, 0 failures"
+
+  Scenario: Object#method
+    When I run "rspec . --example 'Array#length'"
+    Then the output should contain "1 example, 0 failures"

data/vendor/ruby/1.8/gems/rspec-core-2.0.0/features/command_line/exit_status.feature

@@ -0,0 +1,52 @@
+Feature: exit status
+
+  In order to fail the build when it should, the spec CLI exits with an
+  appropriate exit status
+
+  Scenario: exit with 0 when all examples pass
+    Given a file named "ok_spec.rb" with:
+      """
+      describe "ok" do
+        it "passes" do
+        end
+      end
+      """
+    When I run "rspec ok_spec.rb"
+    Then the exit status should be 0
+    And the stdout should contain "1 example, 0 failures"
+
+  Scenario: exit with 1 when one example fails
+    Given a file named "ko_spec.rb" with:
+      """
+      describe "KO" do
+        it "fails" do
+          raise "KO"
+        end
+      end
+      """
+    When I run "rspec ko_spec.rb"
+    Then the exit status should be 1
+    And the stdout should contain "1 example, 1 failure"
+
+  Scenario: exit with 1 when a nested examples fails
+    Given a file named "nested_ko_spec.rb" with:
+      """
+      describe "KO" do
+        describe "nested" do
+          it "fails" do
+            raise "KO"
+          end
+        end
+      end
+      """
+    When I run "rspec nested_ko_spec.rb"
+    Then the exit status should be 1
+    And the stdout should contain "1 example, 1 failure"
+      
+  Scenario: exit with 0 when no examples are run
+    Given a file named "a_no_examples_spec.rb" with:
+      """
+      """
+    When I run "rspec a_no_examples_spec.rb"
+    Then the exit status should be 0
+    And the stdout should contain "0 examples, 0 failures"

data/vendor/ruby/1.8/gems/rspec-core-2.0.0/features/command_line/line_number_appended_to_path.feature

@@ -0,0 +1,104 @@
+Feature: line number appended to file path
+
+  Append a line number to the path to run a single example, or a single group.
+  
+  Background:
+    Given a file named "example_spec.rb" with:
+      """
+      describe "outer group" do
+
+        it "first example in outer group" do
+
+        end
+        
+        it "second example in outer group" do
+
+        end
+
+        describe "nested group" do
+          
+          it "example in nested group" do
+
+          end
+        
+        end
+
+      end
+      """
+
+  Scenario: nested groups - outer group on declaration line
+    When I run "rspec example_spec.rb:1 --format doc"
+    Then the output should contain "3 examples, 0 failures"
+    And the output should contain "second example in outer group"
+    And the output should contain "first example in outer group"
+    And the output should contain "example in nested group"
+
+  Scenario: nested groups - outer group inside block before example
+    When I run "rspec example_spec.rb:2 --format doc"
+    Then the output should contain "3 examples, 0 failures"
+    And the output should contain "second example in outer group"
+    And the output should contain "first example in outer group"
+    And the output should contain "example in nested group"
+
+  Scenario: nested groups - inner group on declaration line
+    When I run "rspec example_spec.rb:11 --format doc"
+    Then the output should contain "1 example, 0 failures"
+    And the output should contain "example in nested group"
+    And the output should not contain "second example in outer group"
+    And the output should not contain "first example in outer group"
+
+  Scenario: nested groups - inner group inside block before example
+    When I run "rspec example_spec.rb:12 --format doc"
+    Then the output should contain "1 example, 0 failures"
+    And the output should contain "example in nested group"
+    And the output should not contain "second example in outer group"
+    And the output should not contain "first example in outer group"
+
+  Scenario: two examples - first example on declaration line
+    When I run "rspec example_spec.rb:3 --format doc"
+    Then the output should contain "1 example, 0 failures"
+    And the output should contain "first example in outer group"
+    But the output should not contain "second example in outer group"
+    And the output should not contain "example in nested group"
+
+  Scenario: two examples - first example inside block
+    When I run "rspec example_spec.rb:4 --format doc"
+    Then the output should contain "1 example, 0 failures"
+    And the output should contain "first example in outer group"
+    But the output should not contain "second example in outer group"
+    And the output should not contain "example in nested group"
+
+  Scenario: two examples - first example on end
+    When I run "rspec example_spec.rb:5 --format doc"
+    Then the output should contain "1 example, 0 failures"
+    And the output should contain "first example in outer group"
+    But the output should not contain "second example in outer group"
+    And the output should not contain "example in nested group"
+
+  Scenario: two examples - first example after end but before next example
+    When I run "rspec example_spec.rb:6 --format doc"
+    Then the output should contain "1 example, 0 failures"
+    And the output should contain "first example in outer group"
+    But the output should not contain "second example in outer group"
+    And the output should not contain "example in nested group"
+
+  Scenario: two examples - second example on declaration line
+    When I run "rspec example_spec.rb:7 --format doc"
+    Then the output should contain "1 example, 0 failures"
+    And the output should contain "second example in outer group"
+    But the output should not contain "first example in outer group"
+    And the output should not contain "example in nested group"
+
+  Scenario: two examples - second example inside block
+    When I run "rspec example_spec.rb:7 --format doc"
+    Then the output should contain "1 example, 0 failures"
+    And the output should contain "second example in outer group"
+    But the output should not contain "first example in outer group"
+    And the output should not contain "example in nested group"
+
+  Scenario: two examples - second example on end
+    When I run "rspec example_spec.rb:7 --format doc"
+    Then the output should contain "1 example, 0 failures"
+    And the output should contain "second example in outer group"
+    But the output should not contain "first example in outer group"
+    And the output should not contain "example in nested group"

data/vendor/ruby/1.8/gems/rspec-core-2.0.0/features/command_line/line_number_option.feature

@@ -0,0 +1,43 @@
+Feature: line number option
+
+  Use the line number option to run a single example, or a single group.
+
+  Scenario: standard examples
+    Given a file named "example_spec.rb" with:
+      """
+      require "rspec/expectations"
+
+      describe 9 do
+
+        it "should be > 8" do
+          9.should be > 8
+        end
+
+        it "should be < 10" do
+          9.should be < 10
+        end
+        
+      end
+      """
+    When I run "rspec example_spec.rb --line 5 --format doc"
+    Then the output should contain "1 example, 0 failures"
+    Then the output should contain "should be > 8"
+    But the stdout should not contain "should be < 10"
+
+  Scenario: one liner
+    Given a file named "example_spec.rb" with:
+      """
+      require "rspec/expectations"
+
+      describe 9 do
+
+        it { should be > 8 }
+
+        it { should be < 10 }
+        
+      end
+      """
+    When I run "rspec example_spec.rb --line 5 --format doc"
+    Then the output should contain "1 example, 0 failures"
+    Then the output should contain "should be > 8"
+    But the stdout should not contain "should be < 10"