master/spec/guard/interactor_spec.rb

require 'spec_helper'

describe Guard::Interactor do
  subject { Guard::Interactor.new }

end
Extract code from signal handlers into methods This will allow building other mechanisms to interact with Guard, for example on JRuby, where signal handling tends to be unreliable. 2011-05-06 17:29:24 +00:00			`require 'spec_helper'`

			`describe Guard::Interactor do`
Work on specs 2011-09-01 21:24:45 +00:00			`subject { Guard::Interactor.new }`
Cleaning up all specs. I basically went through all specs and applied the following rules: * Use `describe` for methods and `context` for contexts. * All class methods starts with `.` and instance methods with `#`. * Removed all `it should`, because the specs _have to_. * Applied a consistant naming on all listener specs. * Make fixture usage more fail save by giving generous sleep times. * Make all behaviour description non-technical and easy to understand. The goal of this excercise was to have a documentation that is easy readable and describes the behaviour and not the implementation. Try it out by using the RSpec documentation format! 2011-05-13 09:26:05 +00:00
Extract code from signal handlers into methods This will allow building other mechanisms to interact with Guard, for example on JRuby, where signal handling tends to be unreliable. 2011-05-06 17:29:24 +00:00			`end`