Guard::Jest automatically tests your Jest specs when files are modified.

It runs the Jest server in watch mode, so that it can run specs more efficiently when instructed.

Add this line to your application's Gemfile:

Add Guard::Jest to your Gemfile:

group :development, :test do
  gem 'guard-jest'
end

Add the default Guard::Jest template to your Guardfile by running:

$ guard init jest

Please read the Guard usage documentation.

Guard::Jest can be adapted to all kind of projects. Please read the Guard documentation for more information about the Guardfile DSL.

guard 'jest' do
  watch(%r{spec/javascripts/spec\.(js\.coffee|js|coffee)$})         { "spec/javascripts" }
  watch(%r{spec/javascripts/.+_spec\.(js\.coffee|js|coffee)$})
  watch(%r{app/assets/javascripts/(.+?)\.(js\.coffee|js|coffee)$})  { |m| "spec/javascripts/#{m[1]}_spec.#{m[2]}" }
end

From the Guard console, typeing 'j u' and pressing enter will trigger a snaphot update.

There are many options that can customize Guard::Jest to your needs. Options are simply supplied as hash when defining the Guard in your Guardfile:

guard 'jest', jest_cmd: './node_modules/jest-cli/bin/jest.js' do
  ...
end

The server options configures the server environment that is needed to run Guard::Jest:

directory:    <cwd>                           # Directory that should be used for running Jest
config_file:  nil                             # Path to a [Jest configuration file](https://facebook.github.io/jest/docs/configuration.html)

jest_cmd:     jest                            # Command to execute in order to start the Jest server

Bug reports and pull requests are welcome on GitHub at https://github.com/nathanstitt/guard-jest.

The gem is available as open source under the terms of the MIT License.