remq 0.0.1a → 0.0.3

data/vendor/bundle/gems/rspec-core-2.12.2/README.md

@@ -0,0 +1,257 @@
+# rspec-core [![Build Status](https://secure.travis-ci.org/rspec/rspec-core.png?branch=master)](http://travis-ci.org/rspec/rspec-core) [![Code Climate](https://codeclimate.com/badge.png)](https://codeclimate.com/github/rspec/rspec-core)
+
+rspec-core provides the structure for writing executable examples of how your
+code should behave, and an `rspec` command with tools to constrain which
+examples get run and tailor the output.
+
+## install
+
+    gem install rspec      # for rspec-core, rspec-expectations, rspec-mocks
+    gem install rspec-core # for rspec-core only
+    rspec --help
+
+## basic structure
+
+RSpec uses the words "describe" and "it" so we can express concepts like a conversation:
+
+    "Describe an order."
+    "It sums the prices of its line items."
+
+```ruby
+describe Order do
+  it "sums the prices of its line items" do
+    order = Order.new
+    order.add_entry(LineItem.new(:item => Item.new(
+      :price => Money.new(1.11, :USD)
+    )))
+    order.add_entry(LineItem.new(:item => Item.new(
+      :price => Money.new(2.22, :USD),
+      :quantity => 2
+    )))
+    order.total.should eq(Money.new(5.55, :USD))
+  end
+end
+```
+
+The `describe` method creates an [ExampleGroup](http://rubydoc.info/gems/rspec-core/RSpec/Core/ExampleGroup).  Within the
+block passed to `describe` you can declare examples using the `it` method.
+
+Under the hood, an example group is a class in which the block passed to
+`describe` is evaluated. The blocks passed to `it` are evaluated in the
+context of an _instance_ of that class.
+
+## nested groups
+
+You can also declare nested nested groups using the `describe` or `context`
+methods:
+
+```ruby
+describe Order do
+  context "with no items" do
+    it "behaves one way" do
+      # ...
+    end
+  end
+
+  context "with one item" do
+    it "behaves another way" do
+      # ...
+    end
+  end
+end
+```
+
+## aliases
+
+You can declare example groups using either `describe` or `context`, though
+only `describe` is available at the top level.
+
+You can declare examples within a group using any of `it`, `specify`, or
+`example`.
+
+## shared examples and contexts
+
+Declare a shared example group using `shared_examples`, and then include it
+in any group using `include_examples`.
+
+```ruby
+shared_examples "collections" do |collection_class|
+  it "is empty when first created" do
+    collection_class.new.should be_empty
+  end
+end
+
+describe Array do
+  include_examples "collections", Array
+end
+
+describe Hash do
+  include_examples "collections", Hash
+end
+```
+
+Nearly anything that can be declared within an example group can be declared
+within a shared example group. This includes `before`, `after`, and `around`
+hooks, `let` declarations, and nested groups/contexts.
+
+You can also use the names `shared_context` and `include_context`. These are
+pretty much the same as `shared_examples` and `include_examples`, providing
+more accurate naming when you share hooks, `let` declarations, helper methods,
+etc, but no examples.
+
+## metadata
+
+rspec-core stores a metadata hash with every example and group, which
+contains like their descriptions, the locations at which they were
+declared, etc, etc. This hash powers many of rspec-core's features,
+including output formatters (which access descriptions and locations),
+and filtering before and after hooks.
+
+Although you probably won't ever need this unless you are writing an
+extension, you can access it from an example like this:
+
+```ruby
+it "does something" do
+  example.metadata[:description].should eq("does something")
+end
+```
+
+### `described_class`
+
+When a class is passed to `describe`, you can access it from an example
+using the `described_class` method, which is a wrapper for
+`example.metadata[:described_class]`.
+
+```ruby
+describe Widget do
+  example do
+    described_class.should equal(Widget)
+  end
+end
+```
+
+This is useful in extensions or shared example groups in which the specific
+class is unknown. Taking the shared examples example from above, we can
+clean it up a bit using `described_class`:
+
+```ruby
+shared_examples "collections" do
+  it "is empty when first created" do
+    described.new.should be_empty
+  end
+end
+
+describe Array do
+  include_examples "collections"
+end
+
+describe Hash do
+  include_examples "collections"
+end
+```
+
+## the `rspec` command
+
+When you install the rspec-core gem, it installs the `rspec` executable,
+which you'll use to run rspec. The `rspec` comes with many useful options.
+Run `rspec --help` to see the complete list.
+
+## store command line options `.rspec`
+
+You can store command line options in a `.rspec` file in the project's root
+directory, and the `rspec` command will read them as though you typed them on
+the command line.
+
+## autotest integration
+
+rspec-core ships with an Autotest extension, which is loaded automatically if
+there is a `.rspec` file in the project's root directory.
+
+## rcov integration
+
+rcov is best integrated via the [rcov rake
+task](http://www.rubydoc.info/github/relevance/rcov/master/Rcov/RcovTask).
+
+rcov can also be integrated via the rspec rake task, but it requires a bit
+more setup:
+
+```ruby
+# Rakefile
+require 'rspec/core/rake_task'
+
+RSpec::Core::RakeTask.new(:spec) do |config|
+  config.rcov = true
+end
+
+task :default => :spec
+
+# spec/spec_helper.rb
+require 'rspec/autorun' # **add this**
+```
+
+## get started
+
+Start with a simple example of behavior you expect from your system. Do
+this before you write any implementation code:
+
+```ruby
+# in spec/calculator_spec.rb
+describe Calculator do
+  it "add(x,y) returns the sum of its arguments" do
+    Calculator.new.add(1, 2).should eq(3)
+  end
+end
+```
+
+Run this with the rspec command, and watch it fail:
+
+```
+$ rspec spec/calculator_spec.rb
+./spec/calculator_spec.rb:1: uninitialized constant Calculator
+```
+
+Implement the simplest solution:
+
+```ruby
+# in lib/calculator.rb
+class Calculator
+  def add(a,b)
+    a + b
+  end
+end
+```
+
+Be sure to require the implementation file in the spec:
+
+```ruby
+# in spec/calculator_spec.rb
+# - RSpec adds ./lib to the $LOAD_PATH
+require "calculator"
+```
+
+Now run the spec again, and watch it pass:
+
+```
+$ rspec spec/calculator_spec.rb
+.
+
+Finished in 0.000315 seconds
+1 example, 0 failures
+```
+
+Use the `documentation` formatter to see the resulting spec:
+
+```
+$ rspec spec/calculator_spec.rb --format doc
+Calculator add
+  returns the sum of its arguments
+
+Finished in 0.000379 seconds
+1 example, 0 failures
+```
+
+## Also see
+
+* [http://github.com/rspec/rspec](http://github.com/rspec/rspec)
+* [http://github.com/rspec/rspec-expectations](http://github.com/rspec/rspec-expectations)
+* [http://github.com/rspec/rspec-mocks](http://github.com/rspec/rspec-mocks)

data/vendor/bundle/gems/rspec-core-2.12.2/exe/autospec

@@ -0,0 +1,13 @@
+#!/usr/bin/env ruby
+require 'rspec/core/deprecation'
+RSpec.warn_deprecation <<-WARNING
+************************************************************
+REMOVAL NOTICE: you are using behaviour that has been
+removed from rspec-2.
+
+* The 'autospec' command is no longer supported.
+* Please use 'autotest' insted.
+
+This message will be removed from a future version of rspec.
+************************************************************
+WARNING

data/vendor/bundle/gems/rspec-core-2.12.2/exe/rspec

@@ -0,0 +1,25 @@
+#!/usr/bin/env ruby
+
+begin
+  require 'rspec/autorun'
+rescue LoadError
+  $stderr.puts <<-EOS
+#{'*'*50}
+  Could not find 'rspec/autorun'
+
+  This may happen if you're using rubygems as your package manager, but it is not
+  being required through some mechanism before executing the rspec command.
+
+  You may need to do one of the following in your shell:
+
+    # for bash/zsh
+    export RUBYOPT=rubygems
+
+    # for csh, etc.
+    set RUBYOPT=rubygems
+
+  For background, please see http://gist.github.com/54177.
+#{'*'*50}
+  EOS
+  exit(1)
+end

data/vendor/bundle/gems/rspec-core-2.12.2/features/Autotest.md

@@ -0,0 +1,38 @@
+RSpec ships with a specialized subclass of Autotest. To use it, just add a
+`.rspec` file to your project's root directory, and run the `autotest` command
+as normal:
+
+    $ autotest
+
+## Bundler
+
+The `autotest` command generates a shell command that runs your specs. If you
+are using Bundler, and you want the shell command to include `bundle exec`,
+require the Autotest bundler plugin in a `.autotest` file in the project's root
+directory or your home directory:
+
+    # in .autotest
+    require "autotest/bundler"
+
+## Upgrading from previous versions of rspec
+
+Previous versions of RSpec used a different mechanism for telling autotest to
+invoke RSpec's Autotest extension: it generated an `autotest/discover.rb` file
+in the project's root directory. This is no longer necessary with the new
+approach of RSpec looking for a `.rspec` file, so feel free to delete the
+`autotest/discover.rb` file in the project root if you have one.
+
+## Gotchas
+
+### Invalid Option: --tty
+
+The `--tty` option was [added in rspec-core-2.2.1](changelog), and is used
+internally by RSpec. If you see an error citing it as an invalid option, you'll
+probably see there are two or more versions of rspec-core in the backtrace: one
+< 2.2.1 and one >= 2.2.1.
+
+This usually happens because you have a newer rspec-core installed, and an
+older rspec-core specified in a Bundler Gemfile. If this is the case, you can:
+
+1. specify the newer version in the Gemfile (recommended)
+2. prefix the `autotest` command with `bundle exec`

data/vendor/bundle/gems/rspec-core-2.12.2/features/README.md

@@ -0,0 +1,17 @@
+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
+
+This documentation is [open
+source](https://github.com/rspec/rspec-core/tree/master/features), and a work
+in progress.  If you find it incomplete or confusing, please [submit an
+issue](http://github.com/rspec/rspec-core/issues), or, better yet, [a pull
+request](http://github.com/rspec/rspec-core).