Mindtonic

I’m using Sphinx and Ultrasphinx for the search engine on one of my projects. I have been struggling with ways to automated the indexing of the database as the commands are rake commands on the command line. Turns out that rufus-scheduler is an excellent solution to this issue. If you allow the scheduler access to the rake file, it is as simple as this schedule below – it is designed to reindex every 90 minutes. I have chose to use the ultrasphinx:bootstrap command because it also has the God like quality of making sure the search server is running at all times.

config/initializers/task_schedule.rb

require 'rake'
require 'rufus/scheduler'
load File.join( RAILS_ROOT, 'Rakefile')

scheduler = Rufus::Scheduler.start_new  

scheduler.every("90m") do
	Rake::Task["ultrasphinx:bootstrap"].invoke
end

Webrat:

• http://github.com/brynary/webrat/tree/master
• http://gitrdoc.com/brynary/webrat/tree/master
• http://codese.wordpress.com/2009/02/05/using-shoulda-webrat-to-write-integration-tests-for-rails/
• http://blog.bitmacro.com/2008/11/14/shoulda-factory_girl-webrat

Integration Testing:

• http://weblog.jamisbuck.org/2006/3/9/integration-testing-in-rails-1-1
• http://www.martinfowler.com/articles/continuousIntegration.html
• http://api.rubyonrails.org/classes/ActionController/Integration/Session.html
• http://locomotivation.squeejee.com/post/109227509/ruby-on-rails-integration-testing-with-integrity
• http://ajaxonrails.wordpress.com/2006/11/02/integration-testing-in-ruby-on-rails-how-to-maintain-sessions-while-testing-in-rails/
• http://bhanoo.blogspot.com/2007/09/rails-integration-testing.html
• http://blog.danielwellman.com/2008/06/writing-rails-integration-tests-with-webrat.html
• http://6brand.com/rails-integration-testing-how-to-learn.html

One thing I liked about rspec was the ability to define tests that you had not yet written. That way you could remind yourself when running the test suite that there are things still to do. Previously in Shoulda, I have been writing these kinds of tests in all caps and using “assert false” to trigger failure and remind me of future work. Turns out there is a nifty way to do it with Shoulda. (I should have guessed there would be!)

should_eventually "do something"

#or just leave off the block
should "do something"

Thanks to BlenderBox for bringing this to my attention while researching Shoulda integration testing.