The Zen of Auto Rspec
Several months ago, I heard that people were using a program called autotest to have their tests continue to run as you made changes to your code base, which comes with ZenTest. It’s a really nice tool written by Ryan Davis and I hadn’t gotten a chance to play with it as of yet. Well, our team isn’t spending too much time in the test/ directory these days as we jumped ship near the end of last summer and found ourselves hanging out on the Isle of BDD. The locals are quite thoughtful about these sorts of things.
I just started working on a project that has been under development for several months and as I’m getting to learn the ins/outs of the system, I find myself having to rerun the specs, which can take quite a bit of time watching. Watching your specs or tests run sometimes is as productive as watching your code compile. Oddly enough, this is as close to compilation as we really get when working with Ruby on Rails… and it’s a productivity killer for me.
There Must Be a Better Way!
So, I did a quick google search and found an announcement for Rails that ran specs through ZenTest. This was exactly what I was searching for!
Some requirements
Please makes sure that you have the following gems installed in your development environment as they are dependencies to make this all work.
- zentest
- diff-lcs
$ sudo gem install zentest diff-lcs
note I’m going to assume that you have rspec and rspec for rails installed… if not… tsk. ;-)
Install RSpec autotest
$ script/plugin install http://svn.caldersphere.net/svn/main/plugins/rspec_autotest
If you’re using subversion, you might consider installing it as an external.
$ script/plugin install -x http://svn.caldersphere.net/svn/main/plugins/rspec_autotest
Running RSpec autotest
This is where it gets tricky. ;-)
$ rake spec:autotest
Now, you can keep a terminal window open and autotest will watch your application and detect when files change. When they change, it’ll attempt to rerun your specs (specifically those that changed). This helps save you the time of having to rerun all your specs throughout the development process and keep your spec:all sanity checks for when you’re about to commit code to your repository.
I’ll post another entry in the next few days to show you how you can use Growl with RSpec Autotest to keep you from having to look at your terminal all the time.
Until then… have fun!
