guard-rspec 2.1.0 → 4.7.3

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 9f60e3dd503909fe6029b421e95d895ab27acde8
+  data.tar.gz: 810b86b4f0dff2ad8e269877d4eef0e4c17effb6
+SHA512:
+  metadata.gz: 593cf6747a4ef7e21d25f8bba6b27dc56dcb15cab6aca0bed634853cdeea0d18f9452e0a7aad84ea42bd364144138f426a107a83754242b09ebfa293055f4281
+  data.tar.gz: 5118ee63611b3af14955ec4481d528facbff713edeeec05229afefd3033b800ab839e274203c8b57424549ab248cdceb2408bba7920ae3f289127fa5fff6452b

data/.gitignore

@@ -0,0 +1,10 @@
+pkg/*
+*.gem
+.bundle
+.DS_Store
+.rvmrc
+.rbx/*
+Gemfile*.lock
+coverage/
+.ruby-version
+.ruby-gemset

data/.hound.yml

@@ -0,0 +1,3 @@
+ruby:
+  enabled: true
+  config_file: .rubocop.yml

data/.rspec

@@ -0,0 +1,2 @@
+--color
+--require spec_helper

data/.rubocop.yml

@@ -0,0 +1,5 @@
+inherit_from:
+  .rubocop_todo.yml
+
+Style/StringLiterals:
+  Enabled: false

data/.rubocop_todo.yml

@@ -0,0 +1,40 @@
+# This configuration was generated by
+# `rubocop --auto-gen-config`
+# on 2016-05-22 06:08:35 +0200 using RuboCop version 0.40.0.
+# The point is for the user to remove these configuration records
+# one by one as the offenses are removed from the code base.
+# Note that changes in the inspected code, or installation of new
+# versions of RuboCop, may require this file to be generated again.
+
+# Offense count: 15
+Style/Documentation:
+  Exclude:
+    - 'spec/**/*'
+    - 'test/**/*'
+    - 'lib/guard/rspec.rb'
+    - 'lib/guard/rspec/command.rb'
+    - 'lib/guard/rspec/deprecator.rb'
+    - 'lib/guard/rspec/dsl.rb'
+    - 'lib/guard/rspec/inspectors/base_inspector.rb'
+    - 'lib/guard/rspec/inspectors/factory.rb'
+    - 'lib/guard/rspec/inspectors/simple_inspector.rb'
+    - 'lib/guard/rspec/notifier.rb'
+    - 'lib/guard/rspec/options.rb'
+    - 'lib/guard/rspec/results.rb'
+    - 'lib/guard/rspec/rspec_process.rb'
+    - 'lib/guard/rspec/runner.rb'
+    - 'lib/guard/rspec_formatter.rb'
+
+# Offense count: 148
+# Cop supports --auto-correct.
+# Configuration parameters: EnforcedStyle, SupportedStyles.
+# SupportedStyles: leading, trailing
+Style/DotPosition:
+  Enabled: false
+
+# Offense count: 654
+# Cop supports --auto-correct.
+# Configuration parameters: EnforcedStyle, SupportedStyles, ConsistentQuotesInMultiline.
+# SupportedStyles: single_quotes, double_quotes
+Style/StringLiterals:
+  Enabled: false

data/.travis.yml

@@ -0,0 +1,14 @@
+language: ruby
+bundler_args: --without=tool development
+rvm:
+  - 2.2.5
+  - 2.3.1
+  - jruby-9.1.1.0
+gemfile:
+  - gemfiles/Gemfile.rspec-2.99
+  - gemfiles/Gemfile.rspec-3.4
+matrix:
+  allow_failures:
+    - rvm: jruby-9.1.1.0
+sudo: false
+cache: bundler

data/CONTRIBUTING.md

@@ -0,0 +1,38 @@
+Contribute to Guard::RSpec
+==========================
+
+File an issue
+-------------
+
+You can report bugs and feature requests to [GitHub Issues](https://github.com/guard/guard-rspec/issues).
+
+**Please don't ask question in the issue tracker**, instead ask them on at Stack Overflow and use the
+[guard](http://stackoverflow.com/questions/tagged/guard) tag and/or [guard-rspec](http://stackoverflow.com/questions/tagged/guard-rspec).
+
+Try to figure out where the issue belongs to: Is it an issue with Guard::RSpec itself or with Guard?
+
+When you file a bug, please try to follow these simple rules if applicable:
+
+* Make sure you've read the README carefully.
+* Make sure you run Guard with `bundle exec` first.
+* Add debug information to the issue by running Guard with the `--debug` option.
+* Add your `Guardfile` and `Gemfile` to the issue.
+* Make sure that the issue is reproducible with your description.
+
+**It's most likely that your bug gets resolved faster if you provide as much information as possible!**
+
+Development
+-----------
+
+* Documentation hosted at [RubyDoc](http://rubydoc.info/github/guard/guard-rspec/master/frames).
+* Source hosted at [GitHub](https://github.com/guard/guard-rspec).
+
+Pull requests are very welcome! Please try to follow these simple rules if applicable:
+
+* Please create a topic branch for every separate change you make.
+* Make sure your patches are well tested. All specs run with `rake test:all_versions` must pass.
+* Update the [README](https://github.com/guard/guard-rspec/blob/master/README.md).
+* Please **do not change** the version number.
+
+For questions please join us in our [Google group](http://groups.google.com/group/guard-dev) or on
+`#guard` (irc.freenode.net).

data/Gemfile

@@ -0,0 +1,25 @@
+# Note: on Travis, this Gemfile is only for installing
+# dependencies. The actual builds use the Gemfiles in
+# the gemspecs/* directory.
+
+filename = "gemfiles/common"
+instance_eval(IO.read(filename), filename, 1)
+
+group :test do
+  gem "rspec", "~> 3.4"
+end
+
+if ENV["USE_INSTALLED_GUARD_RSPEC"] == "1"
+  gem "guard-rspec"
+else
+  gemspec development_group: :gem_build_tools
+end
+
+group :gem_build_tools do
+end
+
+group :development do
+  gem "rubocop", require: false
+  gem "guard-rubocop", require: false
+  gem "guard-compat", ">= 0.0.2", require: false
+end

data/Guardfile

@@ -0,0 +1,28 @@
+group :specs, halt_on_fail: true do
+  guard :rspec, cmd: "bundle exec rspec" do
+    require "guard/rspec/dsl"
+    dsl = Guard::RSpec::Dsl.new(self)
+
+    # RSpec files
+    rspec = dsl.rspec
+    watch(rspec.spec_files)
+    watch(rspec.spec_helper) { rspec.spec_dir }
+    watch(rspec.spec_support) { rspec.spec_dir }
+
+    # Ruby files
+    dsl.watch_spec_files_for(dsl.ruby.lib_files)
+
+    watch(%r{^(lib/guard/rspec/template)s/Guardfile$}) do
+      rspec.spec.call("lib/guard/rspec/template")
+    end
+
+    watch(%r{^lib/guard/rspec/dsl.rb$}) do
+      rspec.spec.call("lib/guard/rspec/template")
+    end
+  end
+
+  guard :rubocop, all_on_start: false do
+    watch(/.+\.rb$/)
+    watch(%r{(?:.+/)?\.rubocop\.yml$}) { |m| File.dirname(m[0]) }
+  end
+end

data/{LICENSE → LICENSE.txt}

@@ -1,4 +1,6 @@
-Copyright (c) 2010-2012 Thibaud Guillaume-Gentil
+Copyright (c) 2010-2016 Thibaud Guillaume-Gentil
+
+MIT License
 
 Permission is hereby granted, free of charge, to any person obtaining
 a copy of this software and associated documentation files (the
@@ -17,4 +19,4 @@ 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.
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -1,46 +1,60 @@
-# Guard::RSpec [![Build Status](https://secure.travis-ci.org/guard/guard-rspec.png?branch=master)](http://travis-ci.org/guard/guard-rspec)
+# Guard::RSpec
 
-RSpec guard allows to automatically & intelligently launch specs when files are modified.
+[![Gem Version](https://badge.fury.io/rb/guard-rspec.png)](http://badge.fury.io/rb/guard-rspec) [![Build Status](https://secure.travis-ci.org/guard/guard-rspec.png?branch=master)](http://travis-ci.org/guard/guard-rspec) [![Dependency Status](https://gemnasium.com/guard/guard-rspec.png)](https://gemnasium.com/guard/guard-rspec) [![Code Climate](https://codeclimate.com/github/guard/guard-rspec.png)](https://codeclimate.com/github/guard/guard-rspec) [![Coverage Status](https://coveralls.io/repos/guard/guard-rspec/badge.png?branch=master)](https://coveralls.io/r/guard/guard-rspec)
 
-* Compatible with RSpec >= 2.11 (use guard-rspec 1.2.x for older release, including RSpec 1.x)
-* Tested against Ruby 1.8.7, 1.9.2, 1.9.3, REE and the latest versions of JRuby & Rubinius.
+Guard::RSpec allows to automatically & intelligently launch specs when files are modified.
+
+* Compatible with RSpec >2.99 & 3
+* Tested against Ruby 2.2.x, JRuby 9.0.5.0 ~~and Rubinius~~.
 
 ## Install
 
-Please be sure to have [Guard](https://github.com/guard/guard) installed before continue.
+Add the gem to your Gemfile (inside development group):
 
-Install the gem:
+``` ruby
+ gem 'guard-rspec', require: false
+```
+
+Add guard definition to your Guardfile by running this command:
 
 ```
-$ gem install guard-rspec
+$ bundle exec guard init rspec
 ```
 
-Add it to your Gemfile (inside development group):
+## Installing with beta versions of RSpec
 
-``` ruby
-group :development do
-  gem 'guard-rspec'
-end
-```
+To install beta versions of RSpec, you need to set versions of all the dependencies, e.g:
 
-Add guard definition to your Guardfile by running this command:
+```ruby
+gem 'rspec', '= 3.5.0.beta3'
+gem 'rspec-core', '= 3.5.0.beta3'
+gem 'rspec-expectations', '= 3.5.0.beta3'
+gem 'rspec-mocks', '= 3.5.0.beta3'
+gem 'rspec-support', '= 3.5.0.beta3'
 
+gem 'guard-rspec', '~> 4.7'
 ```
-$ guard init rspec
+
+and for Rails projects this also means adding:
+
+```ruby
+gem 'rspec-rails', '= 3.5.0.beta3'
 ```
 
+and then running `bundle update rspec rspec-core rspec-expectations rspec-mocks rspec-support rspec-rails` or just `bundle update` to update all the gems in your project.
+
 ## Usage
 
-Please read [Guard usage doc](https://github.com/guard/guard#readme)
+Please read [Guard usage doc](https://github.com/guard/guard#readme).
 
 ## Guardfile
 
-RSpec guard can be really adapted to all kind of projects.
+Guard::RSpec can be adapted to all kinds of projects, some examples:
 
 ### Standard RubyGem project
 
 ``` ruby
-guard 'rspec' do
+guard :rspec, cmd: 'rspec' do
   watch(%r{^spec/.+_spec\.rb$})
   watch(%r{^lib/(.+)\.rb$})     { |m| "spec/lib/#{m[1]}_spec.rb" }
   watch('spec/spec_helper.rb')  { "spec" }
@@ -50,13 +64,13 @@ end
 ### Typical Rails app
 
 ``` ruby
-guard 'rspec' do
+guard :rspec, cmd: 'bundle exec rspec' do
   watch('spec/spec_helper.rb')                        { "spec" }
   watch('config/routes.rb')                           { "spec/routing" }
   watch('app/controllers/application_controller.rb')  { "spec/controllers" }
   watch(%r{^spec/.+_spec\.rb$})
   watch(%r{^app/(.+)\.rb$})                           { |m| "spec/#{m[1]}_spec.rb" }
-  watch(%r{^app/(.*)(\.erb|\.haml)$})                 { |m| "spec/#{m[1]}#{m[2]}_spec.rb" }
+  watch(%r{^app/(.*)(\.erb|\.haml|\.slim)$})          { |m| "spec/#{m[1]}#{m[2]}_spec.rb" }
   watch(%r{^lib/(.+)\.rb$})                           { |m| "spec/lib/#{m[1]}_spec.rb" }
   watch(%r{^app/controllers/(.+)_(controller)\.rb$})  { |m| ["spec/routing/#{m[1]}_routing_spec.rb", "spec/#{m[2]}s/#{m[1]}_#{m[2]}_spec.rb", "spec/acceptance/#{m[1]}_spec.rb"] }
 end
@@ -66,137 +80,108 @@ Please read [Guard doc](https://github.com/guard/guard#readme) for more informat
 
 ## Options
 
-You can pass any of the standard RSpec CLI options using the `:cli` option:
+Guard::RSpec 4.0 now uses a simpler approach with the new `cmd` option that let you precisely define which rspec command will be launched on each run. **This option is required** due to the number of different ways possible to invoke rspec, the template now includes a default that should work for most applications but may not be optimal for all. As example if you want to support Spring with a custom formatter (progress by default) use:
 
 ``` ruby
-guard 'rspec', :cli => "--color --format nested --fail-fast --drb" do
+guard :rspec, cmd: 'spring rspec -f doc' do
   # ...
 end
 ```
 
-By default, Guard::RSpec will only look for spec files within `spec` in your project root. You can configure Guard::RSpec to look in additional paths by using the `:spec_paths` option:
+NOTE: the above example assumes you have the `spring rspec` command installed - see here: https://github.com/jonleighton/spring-commands-rspec
 
-``` ruby
-guard 'rspec', :spec_paths => ["spec", "vendor/engines/reset/spec"] do
-  # ...
-end
-```
-If you have only one path to look, you can configure `:spec_paths` option with a string:
+### Running with bundler
 
-``` ruby
-guard 'rspec', :spec_paths => "test" do
-  # ...
-end
-```
-If you want to set an environment variable, you can configure `:env` option with a hash:
+Running `bundle exec guard` will not run the specs with bundler. You need to change the `cmd` option to `bundle exec rspec`:
 
 ``` ruby
-guard 'rspec', :env => {'RAILS_ENV' => 'guard'} do
+guard :rspec, cmd: 'bundle exec rspec' do
   # ...
 end
 ```
-[Turnip](https://github.com/jnicklas/turnip) is supported (Ruby 1.9.X only), but you must enable it:
-``` ruby
-guard 'rspec', :turnip => true do
-  # ...
-end
-```
-
-
-Former `:color`, `:drb`, `:fail_fast` and `:formatter` options are deprecated and have no effect anymore.
 
 ### List of available options:
 
 ``` ruby
-:cli => "-c -f doc"          # pass arbitrary RSpec CLI arguments, default: "-f progress"
-:bundler => false            # use "bundle exec" to run the RSpec command, default: true
-:binstubs => true            # use "bin/rspec" to run the RSpec command (takes precedence over :bundle), default: false
-:rvm => ['1.8.7', '1.9.2']   # directly run your specs on multiple Rubies, default: nil
-:notification => false       # display Growl (or Libnotify) notification after the specs are done running, default: true
-:all_after_pass => false     # run all specs after changed specs pass, default: true
-:all_on_start => false       # run all the specs at startup, default: true
-:keep_failed => false        # keep failed specs until they pass, default: true
-:run_all => { :cli => "-p" } # cli arguments to use when running all specs, default: same as :cli
-:spec_paths => ["spec"]      # specify an array of paths that contain spec files
-:turnip => true              # enable turnip support; default: false
-:zeus => true                # enable zeus support; default: false
+cmd: 'zeus rspec'      # Specify a custom rspec command to run, default: 'rspec'
+cmd_additional_args: '-f progress' # Any arguments that should be added after the default
+                                   # arguments are applied but before the spec list
+spec_paths: ['spec']   # Specify a custom array of paths that contain spec files
+failed_mode: :focus    # What to do with failed specs
+                       # Available values:
+                       #  :focus - focus on the first 10 failed specs, rerun till they pass
+                       #  :keep - keep failed specs until they pass (add them to new ones)
+                       #  :none (default) - just report
+all_after_pass: true   # Run all specs after changed specs pass, default: false
+all_on_start: true     # Run all the specs at startup, default: false
+launchy: nil           # Pass a path to an rspec results file, e.g. ./tmp/spec_results.html
+notification: false    # Display notification after the specs are done running, default: true
+run_all: { cmd: 'custom rspec command', message: 'custom message' } # Custom options to use when running all specs
+title: 'My project'    # Display a custom title for the notification, default: 'RSpec results'
+chdir: 'directory'     # run rspec from within a given subdirectory (useful if project has separate specs for submodules)
+results_file: 'some/path' # use the given file for storing results (instead of default relative path)
+bundler_env: :original_env # Specify which Bundler env to run the cmd under, default: :original_env
+                       # Available values:
+                       #  :clean_env - old behavior, uses Bundler environment with all bundler-related variables removed. This is deprecated in bundler 1.12.x.
+                       #  :original_env (default) - uses Bundler environment present before Bundler was activated
+                       #  :inherit - runs inside the current environment
 ```
 
-You can also use a custom binstubs directory using `:binstubs => 'some-dir'`.
-
-### DRb mode
-
-When you specify `--drb` within `:cli`, guard-rspec will circumvent the `rspec` command line tool by
-directly communicating with the RSpec DRb server.  This avoids the extra overhead incurred by your
-shell, bundler and loading RSpec's environment just to send a DRb message.  It shaves off a
-second or two before the specs start to run; they should run almost immediately.
-
-
-Notification
-------------
+### Using Launchy to view rspec results
 
-The notification feature is only available for RSpec < 2, and RSpec >= 2.4 (due to the multiple-formatters feature that was present in RSpec 1, was removed in RSpec 2 and reintroduced in RSpec 2.4). So if you are using a version between 2 and 2.4, you should disable the notification with <tt>:notification => false</tt>. Otherwise, nothing will be displayed in the terminal when your specs will run.
-
-The best solution is still to update RSpec to the latest version!
-
-Formatters
-----------
-
-The `:formatter` option has been removed since CLI arguments can be passed through the `:cli` option. If you want to use the former Instafail formatter, you need to use [rspec-instafail](http://rubygems.org/gems/rspec-instafail) gem instead:
+guard-rspec can be configured to launch a results file in lieu of outputing rspec results to the terminal.
+Configure your Guardfile with the launchy option:
 
 ``` ruby
-# in your Gemfile
-gem 'rspec-instafail'
-
-# in your Guardfile
-guard 'rspec', :cli => '-r rspec/instafail -f RSpec::Instafail' do
+guard :rspec, cmd: 'rspec -f html -o ./tmp/spec_results.html', launchy: './tmp/spec_results.html' do
   # ...
 end
 ```
 
-Default formatter is the `progress` formatter (same as RSpec default).
+### Zeus Integration
 
-Running a subset of all specs
------------
+You can use plain `Zeus` or you can use `Guard::Zeus` for managing the `Zeus` server (but you'll want to remove the spec watchers from `Guard::Zeus`, or you'll have tests running multiple times).
 
-The `:all_on_start` and `:all_after_pass` options cause all specs located in the `spec` directory to be run.  If there
-are some specs you want to skip, you can tag them with RSpec metadata (such as `:slow => true`)
-and skip them with the cli `--tag` option (i.e. `--tag ~slow`).
+Also, if you get warnings about empty environment, be sure to [read about this workaround](https://github.com/guard/guard-rspec/wiki/Warning:-no-environment)
 
-You can also use option :spec_paths to override paths used when running all specs.
-You can use this feature to create multiple groups of guarded specs with distinct paths, and execute each in own process:
+### Using parallel_tests
 
-``` ruby
-# in your Guardfile
-group 'acceptance-tests' do
-  guard 'rspec', :spec_paths => ['spec/acceptance'] do
-    # ...
-  end
-end
+parallel_tests has a `-o` option for passing RSpec options, and here's a trick to make it work with Guard::RSpec:
 
-group 'unit-tests' do
-  guard 'rspec', :spec_paths => ['spec/models', 'spec/controllers', 'spec/routing'] do
-    # ...
-  end
-end
+```ruby
+rspec_options = {
+  cmd: "bundle exec rspec",
+  run_all: {
+    cmd: "bundle exec parallel_rspec -o '",
+    cmd_additional_args: "'"
+  }
+}
+guard :rspec, rspec_options do
+# (...)
 ```
 
+(Notice where the `'` characters are placed)
+
+
+## Development
+
+* Documentation hosted at [RubyDoc](http://rubydoc.info/github/guard/guard-rspec/master/frames).
+* Source hosted at [GitHub](https://github.com/guard/guard-rspec).
 
-Development
------------
+Pull requests are very welcome! Please try to follow these simple rules if applicable:
 
-* Source hosted at [GitHub](https://github.com/guard/guard-rspec)
-* Report issues/Questions/Feature requests on [GitHub Issues](https://github.com/guard/guard-rspec/issues)
+* Please create a topic branch for every separate change you make.
+* Make sure your patches are well tested. All specs run with `rake spec:portability` must pass.
+* Update the [README](https://github.com/guard/guard-rspec/blob/master/README.md).
+* Please **do not change** the version number.
 
-Pull requests are very welcome! Make sure your patches are well tested. Please create a topic branch for every separate change
-you make.
+For questions please join us in our [Google group](http://groups.google.com/group/guard-dev) or on
+`#guard` (irc.freenode.net).
 
-Testing
--------
+### Author
 
-Please run `rake spec:prepare_fixtures` once before launching specs.
+[Thibaud Guillaume-Gentil](https://github.com/thibaudgg) ([@thibaudgg](https://twitter.com/thibaudgg))
 
-Author
-------
+### Contributors
 
-[Thibaud Guillaume-Gentil](https://github.com/thibaudgg)
+[https://github.com/guard/guard-rspec/contributors](https://github.com/guard/guard-rspec/contributors)

data/Rakefile

@@ -0,0 +1,38 @@
+require "nenv"
+require "bundler/gem_tasks"
+require "yaml"
+
+default_tasks = []
+
+require "rspec/core/rake_task"
+default_tasks << RSpec::Core::RakeTask.new(:spec) do |t|
+  t.verbose = Nenv.ci?
+end
+
+unless Nenv.ci?
+  require "rubocop/rake_task"
+  default_tasks << RuboCop::RakeTask.new(:rubocop)
+end
+
+task default: default_tasks.map(&:name)
+
+namespace :test do
+  desc "Locally run tests like Travis and HoundCI would"
+  task :all_versions do
+    system(*%w(bundle install --quiet)) || abort
+    system(*%w(bundle update --quiet)) || abort
+    system(*%w(bundle exec rubocop -c .rubocop.yml)) || abort
+
+    travis = YAML.load(IO.read(".travis.yml"))
+    travis["gemfile"].each do |gemfile|
+      STDOUT.puts
+      STDOUT.puts "----------------------------------------------------- "
+      STDOUT.puts " >> Running tests using Gemfile: #{gemfile} <<"
+      STDOUT.puts "----------------------------------------------------- "
+      env = { "BUNDLE_GEMFILE" => gemfile }
+      system(env, *%w(bundle install --quiet)) || abort
+      system(env, *%w(bundle update --quiet)) || abort
+      system(env, *%w(bundle exec rspec)) || abort
+    end
+  end
+end

data/gemfiles/Gemfile.rspec-2.99

@@ -0,0 +1,6 @@
+gemspec path: '../'
+
+filename = "gemfiles/common"
+instance_eval(IO.read(filename), filename, 1)
+
+gem 'rspec', '~> 2.99'

data/gemfiles/Gemfile.rspec-3.4

@@ -0,0 +1,6 @@
+gemspec path: '../'
+
+filename = "gemfiles/common"
+instance_eval(IO.read(filename), filename, 1)
+
+gem 'rspec', '~> 3.4.0'

data/gemfiles/common

@@ -0,0 +1,9 @@
+source "https://rubygems.org"
+
+group :test do
+  gem "bundler", "~> 1.12", "< 2.0"
+  gem "rake", "~> 11.1"
+  gem 'coveralls', require: false
+  gem "launchy", "~> 2.4"
+  gem "gem_isolator", '~> 0.2', '>= 0.2.1'
+end

data/guard-rspec.gemspec

@@ -0,0 +1,25 @@
+# coding: utf-8
+lib = File.expand_path("../lib", __FILE__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require "guard/rspec/version"
+
+Gem::Specification.new do |s|
+  s.name        = "guard-rspec"
+  s.version     = Guard::RSpecVersion::VERSION
+  s.author      = "Thibaud Guillaume-Gentil"
+  s.email       = "thibaud@thibaud.gg"
+  s.summary     = "Guard gem for RSpec"
+  s.description = "Guard::RSpec automatically run your specs" \
+                  " (much like autotest)."
+
+  s.homepage    = "https://github.com/guard/guard-rspec"
+  s.license     = "MIT"
+
+  s.files        = `git ls-files`.split($INPUT_RECORD_SEPARATOR)
+  s.test_files   = s.files.grep(%r{^spec/})
+  s.require_path = "lib"
+
+  s.add_dependency "guard", "~> 2.1"
+  s.add_dependency "guard-compat", "~> 1.1"
+  s.add_dependency "rspec", ">= 2.99.0", "< 4.0"
+end