Phlip wrote: >> Are you requiring your own assertions before you get to that bit of >> code? If so, and they are all in the Test::Unit::Assertions module... >> then that is weird. >> > > I tracked this one out of both Merb and RSpec. Something in the assertions' > own > architecture is popping loose. Then someone (either RSpec or the assertions > themselves) provides no clear stack trace to the problem! > > Now, how to run merb-gen to produce test cases instead of specs? I have to > stay > with specs for this project, but I'm still curious about that one... > > Adding --testing-framework=test_unit to your merb-gen command should give you a test. If you want this to be app wide, you could set:
use_test :test_unit in config/init.rb Derek --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
