Project

guard-motion

0.03
No commit activity in last 3 years
No release in over 3 years
There's a lot of open issues
guard-motionmordaroso/guard-motionHomepageDocumentationSource CodeBug TrackerWiki
Guard::Motion automatically run your specs (much like autotest).
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Popularity
Downloads
13,245
Stars
45
Forks
10
Watchers
7
 Releases
Current version
0.1.2
Total releases
3
First release
2012-08-10
Latest release
2013-05-23
 Issues
Open Issues
2
Closed Issues
5
Total Issues
7
Issue Closure Rate
71%
 Pull Requests
Open Pull Requests
1
Closed Pull Requests
1
Merged Pull Requests
4
Pull Request Acceptance Rate
66%
 Development
Primary Language
Ruby
Average date of last 50 commits
2012-12-19
Reverse Dependencies
5

 Dependencies

Development

bundler
>= 1.1.0
guard-rspec
~> 1.1
rspec
~> 2.10

Runtime

guard
>= 1.1.0
rake
>= 0.9
 Project Readme

Guard::Motion Build Status

Motion guard allows to automatically & intelligently launch RubyMotion specs when files are modified.

Install

Please be sure to have Guard installed before continue.

Install the gem:

$ gem install guard-motion

Add it to your Gemfile (inside development group):

gem 'guard-motion'

Add guard definition to your Guardfile by running this command:

$ guard init motion

Make sure Guard::Motion is loaded in your project Rakefile:

require 'guard/motion'

Usage

Please read Guard usage doc

Guardfile

Motion guard can be really adapted to all kind of project setup.

Typical RubyMotion App

guard 'motion' do
  watch(%r{^spec/.+_spec\.rb$})
  watch(%r{^app/(.+)\.rb$})     { |m| "spec/#{m[1]}_spec.rb" }
end

Typical RubyMotion library

guard 'motion' do
  watch(%r{^spec/.+_spec\.rb$})
  watch(%r{^lib/[^/]+/(.+)\.rb$})     { |m| "spec/#{m[1]}_spec.rb" }
end

Please read Guard doc for more information about the Guardfile DSL.

Options

By default, Guard::Motion will only look for spec files within spec in your project root. You can configure Guard::Motion to look in additional paths by using the :spec_paths option:

guard 'motion', :spec_paths => ["spec", "vendor/other_project/spec"] do
  # ...
end

If you have only one path to look, you can configure :spec_paths option with a string:

guard 'motion', :spec_paths => "test" do
  # ...
end

List of available options:

:bundler => false                 # use "bundle exec" to run the rake command, default: true
:binstubs => true                 # use "bin/rake" to run the rake command (takes precedence over :bundle), default: false
:env => {:output => 'test_unit'}  # set env variables to be used by the RubyMotion spec runner, default: {}
: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
:spec_paths => ["spec"]           # specify an array of paths that contain spec files

You can also use a custom binstubs directory using :binstubs => 'some-dir'.

Development

Pull requests are very welcome! Make sure your patches are well tested. Please create a topic branch for every separate change you make.