A couple days ago I submitted a patch, that was committed by Ezra, to the MrBlog project for the Rspec on Merb plugin. So far, it only works with ActiveRecord including fixtures. Has any played with it? If so, did you get it to work?
I'm going to be submitting a patch for Controller specs soon. It will be very bare bones, given my current lack of understanding of Merb controller development. View and Helper specs will follow. I saw the question on IRC, but should ROM be folded into Merb itself, or act as a plugin? There are advantages and disadvantages to both. A pull to integrate classes into Merb is that these classes can be reused by Test::Unit tests and Rspec. A pull to keep classes in a plugin is It can change whenever Merb or Rspec changes. Since both Merb and Rspec are rapidly evolving, there may be a need for the plugin for a while. Since Test::Unit is fairly static, there may not be a need to make the Test::Unit library a plugin. One flaw with Rails, that I hope does not get repeated in Merb, is the tight coupling with Test;:Unit (same with tight coupling with Rspec). Of course Rspec did not exist when Rails was first developed, so this should not be much of a problem as long as we are vigilant. :) Brian
_______________________________________________ Merb-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/merb-devel
