guard-jasmine 0.7.2 → 0.8.0

data/README.md

@@ -2,7 +2,7 @@
 
 Guard::Jasmine automatically tests your Jasmine specs when files are modified.
 
-Tested on MRI Ruby 1.8.7, 1.9.2, REE and the latest versions of JRuby & Rubinius.
+Tested on MRI Ruby 1.8.7, 1.9.2, 1.9.3, REE and the latest versions of JRuby & Rubinius.
 
 If you have any questions please join us on our [Google group](http://groups.google.com/group/guard-dev) or on `#guard`
 (irc.freenode.net).
@@ -18,6 +18,8 @@ various web standards: DOM handling, CSS selector, JSON, Canvas, and SVG.
 * Runs the standard Jasmine test runner, so you can use [Jasminerice][] for integrating [Jasmine][] into the
 [Rails 3.1 asset pipeline][] and write your specs in [CoffeeScript][].
 
+* Command line helper for CI server integration.
+
 * Runs on Mac OS X, Linux and Windows.
 
 ## How it works
@@ -39,19 +41,22 @@ various web standards: DOM handling, CSS selector, JSON, Canvas, and SVG.
 
 ### Guard and Guard::Jasmine
 
-Please be sure to have [Guard][] installed.
-
-Install the gem:
+The simplest way to install Guard is to use [Bundler](http://gembundler.com/).
+Please make sure to have [Guard][] installed.
 
-    $ gem install guard-jasmine
+Add Guard::Jasmine to your `Gemfile`:
 
-Add it to your `Gemfile`, preferably inside the development group:
+```ruby
+group :development do
+  gem 'guard-jasmine'
+end
+```
 
-    gem 'guard-jasmine'
+Add the default Guard::Jasmine template to your `Guardfile` by running:
 
-Add guard definition to your `Guardfile` by running this command:
-
-    $ guard init jasmine
+```bash
+$ guard init jasmine
+```
 
 ### Jasminerice
 
@@ -62,20 +67,26 @@ Please read the detailed installation and configuration instructions at [Jasmine
 
 In short, you add it to your `Gemfile`:
 
-    group :development, :test do
-      gem 'jasminerice'
-    end
+```ruby
+group :development, :test do
+  gem 'jasminerice'
+end
+```
 
 and add a route for the Jasmine Test Runner to `config/routes.rb`:
 
-    if ["development", "test"].include? Rails.env
-      mount Jasminerice::Engine => "/jasmine"
-    end
+```ruby
+if ["development", "test"].include? Rails.env
+  mount Jasminerice::Engine => "/jasmine"
+end
+```
 
 Next you create the directory `spec/javascripts` where your CoffeeScript tests go into. You define the Rails 3.1
 asset pipeline manifest in `spec/javascripts/spec.js.coffee`:
 
-    #=require_tree ./
+```coffeescript
+#=require_tree ./
+```
 
 ### PhantomJS
 
@@ -84,13 +95,17 @@ You need the PhantomJS browser installed on your system. You can download binari
 
 Alternatively you can install [Homebrew][] on Mac OS X and install it with:
 
-    $ brew install phantomjs
+```bash
+$ brew install phantomjs
+```
 
 If you are using Ubuntu 10.10, you can install it with apt:
 
-    $ sudo add-apt-repository ppa:jerome-etienne/neoip
-    $ sudo apt-get update
-    $ sudo apt-get install phantomjs
+```bash
+$ sudo add-apt-repository ppa:jerome-etienne/neoip
+$ sudo apt-get update
+$ sudo apt-get install phantomjs
+```
 
 You can also build it from source for several other operating systems, please consult the
 [PhantomJS build instructions][].
@@ -104,46 +119,54 @@ Please read the [Guard usage documentation](https://github.com/guard/guard#readm
 Guard::Jasmine can be adapted to all kind of projects. Please read the
 [Guard documentation](https://github.com/guard/guard#readme) for more information about the Guardfile DSL.
 
-    guard 'jasmine' do
-      watch(%r{app/assets/javascripts/(.+)\.(js\.coffee|js)}) { |m| "spec/javascripts/#{m[1]}_spec.#{m[2]}" }
-      watch(%r{spec/javascripts/(.+)_spec\.(js\.coffee|js)})  { |m| "spec/javascripts/#{m[1]}_spec.#{m[2]}" }
-      watch(%r{spec/javascripts/spec\.(js\.coffee|js)})       { "spec/javascripts" }
-    end
+```ruby
+guard 'jasmine' do
+  watch(%r{app/assets/javascripts/(.+)\.(js\.coffee|js)}) { |m| "spec/javascripts/#{m[1]}_spec.#{m[2]}" }
+  watch(%r{spec/javascripts/(.+)_spec\.(js\.coffee|js)})  { |m| "spec/javascripts/#{m[1]}_spec.#{m[2]}" }
+  watch(%r{spec/javascripts/spec\.(js\.coffee|js)})       { "spec/javascripts" }
+end
+```
 
 ## Options
 
 There are many options that can customize Guard::Jasmine to your needs. Options are simply supplied as hash when
 defining the Guard in your `Guardfile`:
 
-    guard 'jasmine', :all_on_start => false, :specdoc => :always do
-      ...
-    end
+```ruby
+guard 'jasmine', :all_on_start => false, :specdoc => :always do
+  ...
+end
+```
 
 ### General options
 
 The general options configures the environment that is needed to run Guard::Jasmine:
 
-    :jasmine_url => 'http://192.168.1.5/jasmine'  # URL where Jasmine is served.
-                                                  # default: http://127.0.0.1/jasmine
+```ruby
+:jasmine_url => 'http://192.168.1.5/jasmine'  # URL where Jasmine is served.
+                                              # default: http://127.0.0.1/jasmine
 
-    :phantomjs_bin => '~/bin/phantomjs'           # Path to phantomjs.
-                                                  # default: '/usr/local/bin/phantomjs'
+:phantomjs_bin => '~/bin/phantomjs'           # Path to phantomjs.
+                                              # default: '/usr/local/bin/phantomjs'
 
-    :timeout => 20000                             # The time in ms to wait for the spec runner to finish.
-                                                  # default: 10000
+:timeout => 20000                             # The time in ms to wait for the spec runner to finish.
+                                              # default: 10000
+```
 
 ### Spec runner options
 
 The spec runner options configures the behavior driven development (or BDD) cycle:
 
-    :all_on_start => false                        # Run all suites on start.
-                                                  # default: true
+```ruby
+:all_on_start => false                        # Run all suites on start.
+                                              # default: true
 
-    :keep_failed => false                         # Keep failed suites and add them to the next run again.
-                                                  # default: true
+:keep_failed => false                         # Keep failed suites and add them to the next run again.
+                                              # default: true
 
-    :all_after_pass => false                      # Run all suites after a suite has passed again after failing.
-                                                  # default: true
+:all_after_pass => false                      # Run all suites after a suite has passed again after failing.
+                                              # default: true
+```
 
 The `:keep_failed` failed option remembers failed suites and not failed specs. The reason for this decision is to
 avoid additional round trip time to request the Jasmine test runner for each single spec, which is mostly more expensive
@@ -154,14 +177,16 @@ than running a whole suite.
 Guard::Jasmine can generate an RSpec like specdoc in the console after running the specs and you can set when it will
 be shown in the console:
 
-    :specdoc => :always                           # Specdoc output options, either :always, :never or :failure
-                                                  # default: :failure
+```ruby
+:specdoc => :always                           # Specdoc output options, either :always, :never or :failure
+                                              # default: :failure
 
-    :focus => false                               # Specdoc focus to hide successful specs when at least one spec fails.
-                                                  # default: true
+:focus => false                               # Specdoc focus to hide successful specs when at least one spec fails.
+                                              # default: true
 
-    :console => :always                           # Console.log output options, either :always, :never or :failure
-                                                  # default: :failure
+:console => :always                           # Console.log output options, either :always, :never or :failure
+                                              # default: :failure
+```
 
 With the option set to `:always`, the specdoc is shown with and without errors in your spec, whereas on with the option
 set to `:never`, there is no output at all, instead just a summary of the spec run is shown. The default option
@@ -176,11 +201,15 @@ to see support for more console methods coming to PhantomJS.
 
 Another restriction on console logging is that currently only the first log parameter is passed. So instead of writing
 
-    console.log('Debug of %o with %s', object, string)
+```javascript
+console.log('Debug of %o with %s', object, string)
+```
 
 your should write
 
-    console.log('Debug of ' + object.toString() + ' width ' + string)
+```javascript
+console.log('Debug of ' + object.toString() + ' width ' + string)
+```
 
 You can also give your vote on [Issue 36](http://code.google.com/p/phantomjs/issues/detail?id=36) to see support for
 multiple console arguments.
@@ -189,14 +218,16 @@ multiple console arguments.
 
 These options affects what system notifications (growl, libnotify or notifu) are shown after a spec run:
 
-    :notifications => false                       # Show success and error notifications.
-                                                  # default: true
+```ruby
+:notifications => false                       # Show success and error notifications.
+                                              # default: true
 
-    :hide_success => true                         # Disable successful spec run notification.
-                                                  # default: false
+:hide_success => true                         # Disable successful spec run notification.
+                                              # default: false
 
-    :max_error_notify => 5                        # Maximum error notifications to show.
-                                                  # default: 3
+:max_error_notify => 5                        # Maximum error notifications to show.
+                                              # default: 3
+```
 
 ## A note on Rails 2 and 3
 
@@ -207,54 +238,60 @@ it's freely up to you how you'll prepare the assets and serve the Jasmine runner
 You can use [the Jasmine Gem][], configure the test suite in `jasmine.yml` and start the Jasmine test runner with
 the supplied Rake task:
 
-    $ rake jasmine
+```bash
+$ rake jasmine
+```
 
 Next follows an example on how to configure your `Guardfile` with the Jasmine gem:
 
-    guard 'jasmine', :jasmine_url => 'http://127.0.0.1:8888' do
-      watch(%r{public/javascripts/(.+)\.js})                  { |m| "spec/javascripts/#{m[1]}_spec.js" }
-      watch(%r{spec/javascripts/(.+)_spec\.js})               { |m| "spec/javascripts/#{m[1]}_spec.js" }
-      watch(%r{spec/javascripts/support/jasmine\.yml})        { "spec/javascripts" }
-      watch(%r{spec/javascripts/support/jasmine_config\.rb})  { "spec/javascripts" }
-    end
+```ruby
+guard 'jasmine', :jasmine_url => 'http://127.0.0.1:8888' do
+  watch(%r{public/javascripts/(.+)\.js})                  { |m| "spec/javascripts/#{m[1]}_spec.js" }
+  watch(%r{spec/javascripts/(.+)_spec\.js})               { |m| "spec/javascripts/#{m[1]}_spec.js" }
+  watch(%r{spec/javascripts/support/jasmine\.yml})        { "spec/javascripts" }
+  watch(%r{spec/javascripts/support/jasmine_config\.rb})  { "spec/javascripts" }
+end
+```
 
 You can also use [guard-process](https://github.com/socialreferral/guard-process) to start the Jasmine Gem server when
 Guard starts:
 
-    guard 'process', :name => 'Jasmine server', :command => 'bundle exec rake jasmine' do
-      watch(%r{spec/javascripts/support/*})
-    end
-
-    JASMINE_HOST = '127.0.0.1'
-    JASMINE_PORT = '8888'
-    JASMINE_URL = "http://#{JASMINE_HOST}:#{JASMINE_PORT}/"
-
-    Thread.new do
-      require 'socket'
-
-      puts "\nWaiting for Jasmine to accept connections on #{JASMINE_URL}..."
-      wait_for_open_connection(JASMINE_HOST, JASMINE_PORT)
-      puts "Jasmine is now ready to accept connections; change a file or press ENTER run your suite."
-      puts "You can also view and run specs by visiting:"
-      puts JASMINE_URL
-
-      guard 'jasmine', :jasmine_url => JASMINE_URL do
-        watch(%r{public/javascripts/(.+)\.js})                  { |m| "spec/javascripts/#{m[1]}_spec.js" }
-        watch(%r{spec/javascripts/(.+)_spec\.js})               { |m| "spec/javascripts/#{m[1]}_spec.js" }
-        watch(%r{spec/javascripts/support/jasmine\.yml})        { "spec/javascripts" }
-        watch(%r{spec/javascripts/support/jasmine_config\.rb})  { "spec/javascripts" }
-      end
-    end
-
-    def wait_for_open_connection(host, port)
-      while true
-        begin
-          TCPSocket.new(host, port).close
-          return
-        rescue Errno::ECONNREFUSED, Errno::EHOSTUNREACH
-        end
-      end
+```ruby
+guard 'process', :name => 'Jasmine server', :command => 'bundle exec rake jasmine' do
+  watch(%r{spec/javascripts/support/*})
+end
+
+JASMINE_HOST = '127.0.0.1'
+JASMINE_PORT = '8888'
+JASMINE_URL = "http://#{JASMINE_HOST}:#{JASMINE_PORT}/"
+
+Thread.new do
+  require 'socket'
+
+  puts "\nWaiting for Jasmine to accept connections on #{JASMINE_URL}..."
+  wait_for_open_connection(JASMINE_HOST, JASMINE_PORT)
+  puts "Jasmine is now ready to accept connections; change a file or press ENTER run your suite."
+  puts "You can also view and run specs by visiting:"
+  puts JASMINE_URL
+
+  guard 'jasmine', :jasmine_url => JASMINE_URL do
+    watch(%r{public/javascripts/(.+)\.js})                  { |m| "spec/javascripts/#{m[1]}_spec.js" }
+    watch(%r{spec/javascripts/(.+)_spec\.js})               { |m| "spec/javascripts/#{m[1]}_spec.js" }
+    watch(%r{spec/javascripts/support/jasmine\.yml})        { "spec/javascripts" }
+    watch(%r{spec/javascripts/support/jasmine_config\.rb})  { "spec/javascripts" }
+  end
+end
+
+def wait_for_open_connection(host, port)
+  while true
+    begin
+      TCPSocket.new(host, port).close
+      return
+    rescue Errno::ECONNREFUSED, Errno::EHOSTUNREACH
     end
+  end
+end
+```
 
 This elegant solution is provided by [Jason Morrison](http://twitter.com/#!/jayunit), see his original
 [Gist](https://gist.github.com/1224382).
@@ -262,8 +299,57 @@ This elegant solution is provided by [Jason Morrison](http://twitter.com/#!/jayu
 It is also possible to use CoffeeScript in this setup, by using [Guard::CoffeeScript][] to compile your code and even
 specs. Just add something like this *before* Guard::Jasmine:
 
-    guard 'coffeescript', :input => 'app/coffeescripts',  :output => 'public/javascripts'
-    guard 'coffeescript', :input => 'spec/coffeescripts', :output => 'spec/javascripts'
+```ruby
+guard 'coffeescript', :input => 'app/coffeescripts',  :output => 'public/javascripts'
+guard 'coffeescript', :input => 'spec/coffeescripts', :output => 'spec/javascripts'
+```
+
+## Guard::Jasmine for your CI server
+
+Guard::Jasmine includes a little command line utility to run your specs once and output the specdoc to the console.
+
+```bash
+$ guard-jasmine
+```
+
+You can get help on the available options with the `help` task:
+
+```bash
+$ guard-jasmine help start
+  Usage:
+    guard-jasmine start
+
+  Options:
+    -u, [--url=URL]          # The url of the Jasmine test runner
+                             # Default: http://127.0.0.1:3000/jasmine
+    -b, [--bin=BIN]          # The location of the PhantomJS binary
+                             # Default: /usr/local/bin/phantomjs
+    -t, [--timeout=N]        # The maximum time in milliseconds to wait for the spec runner to finish
+                             # Default: 10000
+    -c, [--console=CONSOLE]  # Whether to show console.log statements in the spec runner, either `always`, `never` or `failure`
+                             # Default: failure
+```
+
+By default all specs are run, but you can supply multiple paths to your specs to run only a subset:
+
+```bash
+$ guard-jasmine spec/javascripts/a_spec.js.coffee spec/javascripts/another_spec.js.coffee
+```
+
+### Travis CI integration
+
+With the given `guard-jasmine` script you're able to configure [Travis CI](http://travis-ci.org/) to run Guard::Jasmine.
+Simply use the `script` setting in your `.travis.yml`:
+
+```yaml
+script: 'bundle exec guard-jasmine'
+```
+
+You can also run your Guard::Jasmine specs after your specs that are ran with `rake` by using `after_script`:
+
+```yaml
+after_script: 'bundle exec guard-jasmine'
+```
 
 ## Alternatives
 
@@ -273,34 +359,53 @@ continuous testing support.
 * [Jezebel][] a Node.js REPL and continuous test runner for [Jessie][], a Node runner for Jasmine, but has no full
 featured browser environment.
 
+## Issues
+
+You can report issues and feature requests to [GitHub Issues](https://github.com/netzpirat/guard-jasmine/issues). Try to figure out
+where the issue belongs to: Is it an issue with Guard itself or with Guard::Jasmine? Please don't
+ask question in the issue tracker, instead join us in our [Google group](http://groups.google.com/group/guard-dev) or on
+`#guard` (irc.freenode.net).
+
+When you file an issue, please try to follow to these simple rules if applicable:
+
+* 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.
+
 ## Development
 
 - Documentation hosted at [RubyDoc](http://rubydoc.info/github/guard/guard-jasmine/master/frames).
 - Source hosted at [GitHub](https://github.com/netzpirat/guard-jasmine).
-- Report issues and feature requests to [GitHub Issues](https://github.com/netzpirat/guard-jasmine/issues).
 
-Pull requests are very welcome! Please try to follow these simple "rules", though:
+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.
-- Update the README (if applicable).
-- Please **do not change** the version number.
+* Please create a topic branch for every separate change you make.
+* Make sure your patches are well tested.
+* Update the [Yard](http://yardoc.org/) documentation.
+* Update the README.
+* Update the CHANGELOG for noteworthy changes.
+* Please **do not change** the version number.
 
-For questions please join us on our [Google group](http://groups.google.com/group/guard-dev) or on `#guard`
-(irc.freenode.net).
+For questions please join us in our [Google group](http://groups.google.com/group/guard-dev) or on
+`#guard` (irc.freenode.net).
 
-### The guard-jasmine executable
+### The guard-jasmine-debug executable
 
-This Guard comes with a small executable `guard-jasmine` that can be used to run the Jasmine test runner on PhantomJS
+This Guard comes with a small executable `guard-jasmine-debug` that can be used to run the Jasmine test runner on PhantomJS
 and see the JSON result that gets evaluated by Guard::Jasmine. This comes handy when there is an issue with your specs
 and you want to see the output of the PhantomJS script.
 
-    $ guard-jasmine
+```bash
+$ guard-jasmine-debug
+```
 
 The only argument that the script takes is the URL to the Jasmine runner, which defaults to
 `http://127.0.0.1:3000/Jasmine`. So you can for example just run a subset of the specs by changing the URL:
 
-    $ guard-jasmine http://127.0.0.1:3000/Jasmine?spec=YourSpec
+```bash
+$ guard-jasmine-debug http://127.0.0.1:3000/Jasmine?spec=YourSpec
+```
 
 ## Acknowledgment
 

data/bin/guard-jasmine

@@ -1,5 +1,3 @@
 #!/usr/bin/env ruby
-
-script = File.expand_path(File.join(File.dirname(__FILE__), '..', 'lib', 'guard', 'jasmine', 'phantomjs', 'run-jasmine.coffee'))
-
-puts `phantomjs #{ script } #{ ARGV[0] } #{ ARGV[1] }`
+require 'guard/jasmine/cli'
+Guard::Jasmine::CLI.start

data/bin/guard-jasmine-debug

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+script = File.expand_path(File.join(File.dirname(__FILE__), '..', 'lib', 'guard', 'jasmine', 'phantomjs', 'run-jasmine.coffee'))
+puts `phantomjs #{ script } #{ ARGV[0] } #{ ARGV[1] }`

data/lib/guard/jasmine/cli.rb

@@ -0,0 +1,85 @@
+require 'thor'
+require 'guard/ui'
+require 'guard/jasmine/version'
+require 'guard/jasmine/runner'
+require 'guard/jasmine/formatter'
+
+module Guard
+  class Jasmine
+
+    # Small helper class to run the Jasmine runner once from the
+    # command line. This can be useful to integrate guard-jasmine
+    # into a continuous integration server.
+    #
+    # This outputs the specdoc and disables any notifications.
+    #
+    class CLI < Thor
+
+      default_task :spec
+
+      desc 'spec', 'Run the Jasmine spec runner'
+
+      method_option :url,
+                    :type => :string,
+                    :aliases => '-u',
+                    :default => 'http://127.0.0.1:3000/jasmine',
+                    :desc => 'The url of the Jasmine test runner'
+
+      method_option :bin,
+                    :type => :string,
+                    :aliases => '-b',
+                    :default => '/usr/local/bin/phantomjs',
+                    :desc => 'The location of the PhantomJS binary'
+
+      method_option :timeout,
+                    :type => :numeric,
+                    :aliases => '-t',
+                    :default => 10000,
+                    :desc => 'The maximum time in milliseconds to wait for the spec runner to finish'
+
+      method_option :console,
+                    :type => :string,
+                    :aliases => '-c',
+                    :default => 'failure',
+                    :desc => 'Whether to show console.log statements in the spec runner, either `always`, `never` or `failure`'
+
+      # Run the Guard::Jasmine::Runner with options from
+      # the command line.
+      #
+      # @param [Array<String>] paths the name of the specs to run
+      #
+      def spec(*paths)
+        paths = ['spec/javascripts'] if paths.empty?
+
+        runner = {}
+        runner[:jasmine_url] = options.url
+        runner[:phantomjs_bin] = options.bin
+        runner[:timeout] = options.timeout
+        runner[:console] = [:always, :never, :failure].include?(options.console.to_sym) ? options.console.to_sym : :failure
+
+        runner[:notification] = false
+        runner[:hide_success] = true
+        runner[:max_error_notify] = 0
+        runner[:specdoc] = :always
+
+        result = ::Guard::Jasmine::Runner.run(paths, runner)
+        Kernel.exit (result.first ? 0 : 1)
+
+      rescue Exception => e
+        ::Guard::UI.error e.message
+      end
+
+      desc 'version', 'Show the Guard::Jasmine version'
+      map %w(-v --version) => :version
+
+      # Shows the current version of Guard::Jasmine.
+      #
+      # @see Guard::Jasmine::VERSION
+      #
+      def version
+        ::Guard::UI.info "Guard::Jasmine version #{ ::Guard::JasmineVersion }"
+      end
+
+    end
+  end
+end

data/lib/guard/jasmine/version.rb

@@ -1,6 +1,6 @@
 module Guard
   module JasmineVersion
     # Guard::Jasmine version that is used for the Gem specification
-    VERSION = '0.7.2'
+    VERSION = '0.8.0'
   end
 end

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: guard-jasmine
 version: !ruby/object:Gem::Version 
-  hash: 7
+  hash: 63
   prerelease: 
   segments: 
   - 0
-  - 7
-  - 2
-  version: 0.7.2
+  - 8
+  - 0
+  version: 0.8.0
 platform: ruby
 authors: 
 - Michael Kessler
@@ -15,7 +15,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2011-10-19 00:00:00 Z
+date: 2011-10-31 00:00:00 Z
 dependencies: 
 - !ruby/object:Gem::Dependency 
   name: guard
@@ -66,9 +66,25 @@ dependencies:
   type: :runtime
   version_requirements: *id003
 - !ruby/object:Gem::Dependency 
-  name: bundler
+  name: thor
   prerelease: false
   requirement: &id004 !ruby/object:Gem::Requirement 
+    none: false
+    requirements: 
+    - - ~>
+      - !ruby/object:Gem::Version 
+        hash: 43
+        segments: 
+        - 0
+        - 14
+        - 6
+        version: 0.14.6
+  type: :runtime
+  version_requirements: *id004
+- !ruby/object:Gem::Dependency 
+  name: bundler
+  prerelease: false
+  requirement: &id005 !ruby/object:Gem::Requirement 
     none: false
     requirements: 
     - - ~>
@@ -79,11 +95,11 @@ dependencies:
         - 0
         version: "1.0"
   type: :development
-  version_requirements: *id004
+  version_requirements: *id005
 - !ruby/object:Gem::Dependency 
   name: guard-rspec
   prerelease: false
-  requirement: &id005 !ruby/object:Gem::Requirement 
+  requirement: &id006 !ruby/object:Gem::Requirement 
     none: false
     requirements: 
     - - ~>
@@ -94,11 +110,11 @@ dependencies:
         - 5
         version: "0.5"
   type: :development
-  version_requirements: *id005
+  version_requirements: *id006
 - !ruby/object:Gem::Dependency 
   name: rspec
   prerelease: false
-  requirement: &id006 !ruby/object:Gem::Requirement 
+  requirement: &id007 !ruby/object:Gem::Requirement 
     none: false
     requirements: 
     - - ~>
@@ -109,11 +125,11 @@ dependencies:
         - 7
         version: "2.7"
   type: :development
-  version_requirements: *id006
+  version_requirements: *id007
 - !ruby/object:Gem::Dependency 
   name: yard
   prerelease: false
-  requirement: &id007 !ruby/object:Gem::Requirement 
+  requirement: &id008 !ruby/object:Gem::Requirement 
     none: false
     requirements: 
     - - ~>
@@ -125,27 +141,27 @@ dependencies:
         - 3
         version: 0.7.3
   type: :development
-  version_requirements: *id007
+  version_requirements: *id008
 - !ruby/object:Gem::Dependency 
-  name: kramdown
+  name: redcarpet
   prerelease: false
-  requirement: &id008 !ruby/object:Gem::Requirement 
+  requirement: &id009 !ruby/object:Gem::Requirement 
     none: false
     requirements: 
     - - ~>
       - !ruby/object:Gem::Version 
-        hash: 45
+        hash: 87
         segments: 
-        - 0
-        - 13
-        - 3
-        version: 0.13.3
+        - 1
+        - 17
+        - 2
+        version: 1.17.2
   type: :development
-  version_requirements: *id008
+  version_requirements: *id009
 - !ruby/object:Gem::Dependency 
   name: pry
   prerelease: false
-  requirement: &id009 !ruby/object:Gem::Requirement 
+  requirement: &id010 !ruby/object:Gem::Requirement 
     none: false
     requirements: 
     - - ~>
@@ -158,18 +174,21 @@ dependencies:
         - 2
         version: 0.9.6.2
   type: :development
-  version_requirements: *id009
+  version_requirements: *id010
 description: Guard::Jasmine automatically tests your Jasmine specs on PhantomJS
 email: 
 - michi@netzpiraten.ch
 executables: 
 - guard-jasmine
+- guard-jasmine-debug
 extensions: []
 
 extra_rdoc_files: []
 
 files: 
 - bin/guard-jasmine
+- bin/guard-jasmine-debug
+- lib/guard/jasmine/cli.rb
 - lib/guard/jasmine/formatter.rb
 - lib/guard/jasmine/inspector.rb
 - lib/guard/jasmine/phantomjs/run-jasmine.coffee