Thanks, your blog post was very helpful. I've got autotest working in my
plugin. One hurdle I had to jump was that the new autotest defines an
exception for vendor/plugins by default. So you can sit and define mappings
all day and never get any results because the whole plugins directory is not
being scanned. Once I added a RemoveException('vendor/plugin') to the top of
my .autotest I was able to see my mappings work and moved on with fine
tuning them.Lee David Chelimsky-2 wrote: > > > If you're looking to run them using rake, just write your own rake task. > > If you're looking to run them using autotest, check this out: > > http://blog.davidchelimsky.net/articles/2008/01/15/rspec-1-1-2-and-zentest-3-8-0 > > HTH, > David > >> >> Thanks, >> Lee >> >> >> >> Shane Mingins-3 wrote: >> > >> > >> > We have a Rails project using an engine which I want to run autotest >> > with rspec against. >> > >> > So the project specific specs are in the specs directory but the >> > common specs are in the specs directory of the engine plugin (e.g. >> > vendor/plugin/engine/specs) >> > >> > >> -- >> View this message in context: >> http://www.nabble.com/Autotest-with-RSpec-Rails-and-Engines-tp12876700p15193445.html >> Sent from the rspec-users mailing list archive at Nabble.com. >> >> _______________________________________________ >> rspec-users mailing list >> [email protected] >> http://rubyforge.org/mailman/listinfo/rspec-users >> > _______________________________________________ > rspec-users mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/rspec-users > > -- View this message in context: http://www.nabble.com/Autotest-with-RSpec-Rails-and-Engines-tp12876700p15214164.html Sent from the rspec-users mailing list archive at Nabble.com. _______________________________________________ rspec-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/rspec-users
