search for: tests_for_fil

...mmon specs are in the specs directory of the engine plugin (e.g. vendor/plugin/engine/specs) Just wondering where I would be looking to change configuration so that autotest will also look for the specs in the engine directory? is there some way of configuring using a .autotest file? The tests_for_file method did not seem to be what I wanted in that it determines the spec to run for a file where I want to determine the files themselves? It would seem that the initialize method of the class Autotest::RailsRspec sets up where it is finding the tests, yes? And is it here that I should be...

Josh Knowles http://joshknowles.com/ just let me know that ZenTest Autotest 3.50 now handles your RSpec specs. http://blog.zenspider.com/archives/2007/04/zentest_version_350_has_been_released.html That''s a great news. Josh also shared with me a quick hack to make autotest work with only the RSpec plugin installed. Add the following into your ~/.autotest file

...'': undefined method `singularize'' for "organizations":String (NoMethodError) from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.6.0/lib/ autotest.rb:395:in `call'' from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.6.0/lib/ autotest.rb:395:in `tests_for_file'' from ./vendor/plugins/rspec/lib/autotest/rspec.rb:19:in `tests_for_file'' from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.6.0/lib/ autotest.rb:319:in `find_files_to_test'' from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.6.0/lib/ autotes...

Has anyone else encountered this problem? What I mean is, rspec_autotest runs all specs, then waits. When you change a spec, it reruns that spec. However, if that spec now passes, it should run the whole suite again, so you can see the next one to work on. It no longer does this. This renders it somewhat useless. Does anyone have autotest working with rspec 0.7.5, or does anyone have any