[rspec-users] using RSpec's trunk in non-rails projects w/ Autotest

Scott Taylor mailing_lists at railsnewbie.com
Wed Aug 8 16:27:50 EDT 2007

Hey Nick,

Good to hear from you (as the original developer of the autotest  
compatibility issue).

I was working on the same issue David was (to fix autotest to work  
for RSpec's trunk), only to find that David had modified it.

I have refactored the autotest plugin to use vendor/plugin/rspec/bin  
if that exists, and have spec'ed out most of the Autotest.  This  
means that a non-rails project could use vendor/plugins w/ rspec  
checked out, and autotest should work out of the box.

Right now spec coverage is at 99.7%, so I'm working on finishing up  
the specs for RSpec's autotest.  (David, I assume this would be  


On Aug 8, 2007, at 4:17 PM, Nick Sieger wrote:

> On 8/6/07, Scott Taylor <mailing_lists at railsnewbie.com> wrote:
> I believe for rails projects you can put rspec's code repos into
> vendor/plugins, and autotest will automatically use the rspec binary
> in that directory, and not the gem installed.
> Is there an easy way to do this for non-rails projects?  There are a
> few advancements on trunk which I would like to take advantage of.
> Tips welcome ; ).
> Check out the trunk somewhere and set RUBYLIB=/path/to/rspec/trunk?
> Emulate the Rails vendor structure somewhat and have a bootstrap  
> script that adds RSpec in that location to the load path?
> /Nick
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users

More information about the rspec-users mailing list