Grag,<br><br>Thanks for trying the Rspec on Merb plugin out.<br><br>Did you get any exceptions related to loading the fixtures?<br>Are you using the fixtures method in the Behaviour block?<br><br>Maybe it would be easier post your spec at:
<br><a href="http://pastie.caboo.se/">http://pastie.caboo.se/</a><br>and reply with the link.<br><br>Thanks,<br>Brian<br><br><div><span class="gmail_quote">On 5/8/07, <b class="gmail_sendername">Gregory O'Connor</b> <
<a href="mailto:goconnor@plumtv.com">goconnor@plumtv.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hey Brian and Ezra,
<br>thank you both for this very interesting code.<br>it's exciting to easily upload a couple of 1.5G files at the same time.<br><br>rake specs<br>fails for me as the fixtures/users.yml is not loaded (after editing<br>
the test/spec/spec_helper.rb for my database).<br><br>also looking at why the progress bar doesn't work for me out of the<br>box. of course the file upload ability is awesome.<br><br>regards,<br>gregory o'connor<br>
> On 5/4/07, Ezra Zygmuntowicz <ez at <a href="http://engineyard.com">engineyard.com</a>> wrote:<br>> ><br>> ><br>> > On May 4, 2007, at 3:29 PM, Brian Takita wrote:<br>> ><br>> > > A couple days ago I submitted a patch, that was committed by Ezra,
<br>> > > to the MrBlog project for the Rspec on Merb plugin.<br>> > > So far, it only works with ActiveRecord including fixtures.<br>> > > Has any played with it? If so, did you get it to work?
<br>> > ><br>> > > I'm going to be submitting a patch for Controller specs soon. It<br>> > > will be very bare bones, given my current lack of understanding of<br>> > > Merb controller development.
<br>> > > View and Helper specs will follow.<br>> > ><br>> > > I saw the question on IRC, but should ROM be folded into Merb<br>> > > itself, or act as a plugin? There are advantages and disadvantages
<br>> > > to both.<br>> > ><br>> > > A pull to integrate classes into Merb is that these classes can be<br>> > > reused by Test::Unit tests and Rspec.<br>> > > A pull to keep classes in a plugin is It can change whenever Merb
<br>> > > or Rspec changes. Since both Merb and Rspec are rapidly evolving,<br>> > > there may be a need for the plugin for a while.<br>> > > Since Test::Unit is fairly static, there may not be a need to make
<br>> > > the Test::Unit library a plugin.<br>> > ><br>> > > One flaw with Rails, that I hope does not get repeated in Merb, is<br>> > > the tight coupling with Test;:Unit (same with tight coupling with
<br>> > > Rspec). Of course Rspec did not exist when Rails was first<br>> > > developed, so this should not be much of a problem as long as we<br>> > > are vigilant. :)<br>> > ><br>> > > Brian
<br>> > ><br>> ><br>> > Hey Brian-<br>> ><br>> > I was able to get the user specs running in mrblog trunk. I<br>> > commited<br>> > a rake task to run them as 'rake specs'. The presence of a spec
<br>> > harness makes the need for proper environments in merb urgent. I<br>> will<br>> > hack up environments with different db settings this weekend so it<br>> > will make testing and deving easier.
<br>> ><br>> > I think that we should keep it as a plugin for a little<br>> while. I<br>> > don't want to go down the tightly coupled road in merb's testing<br>> > capabilities. I think there are some core helper classes I need to
<br>> > write that could go in the framework and be used by test/unit or<br>> > rspec or whatver. Like a helper for making requests thru the<br>> > dispacther and controllers to test output without booting a
<br>> > webserver, and some other stuff that will help with testing.<br>> ><br>> > I'd like to see the test helpers that are merb specific<br>> made into<br>> > libraries within merb that you can use from test/unit, test/spec or
<br>> > rspec.<br>> ><br>> > Thanks for getting this started Brian, it's a nice<br>> plugin. If you<br>> > have any questions about merb internals please feel free to ask<br>> and I
<br>> > will help you grok it quickly.<br>><br>><br>> Great. Thanks Ezra.<br>><br>> I submitted a patch for a frist stab at controller specs.<br>> <a href="http://merb.devjavu.com/projects/merb/ticket/45">
http://merb.devjavu.com/projects/merb/ticket/45</a><br>><br>> Here are some things of consideration:<br>><br>> - response.should redirect_to and response.should<br>> render_template and<br>> not implemented yet.
<br>> - The controller Description class has a controller_class<br>> accessor. If<br>> the first argument of describe is set to the controller class,<br>> the examples<br>> will know that the requests are for the controller.
<br>> - I couldn't figure out how to construct the correct uri given the<br>> controller and the action.<br>><br>><br>> Cheers-<br>> > -- Ezra Zygmuntowicz<br>> > -- Lead Rails Evangelist
<br>> > -- ez at <a href="http://engineyard.com">engineyard.com</a><br>> > -- Engine Yard, Serious Rails Hosting<br>> > -- (866) 518-YARD (9273)<br>> ><br>> ><br>> ><br><br><br>_______________________________________________
<br>Merb-devel mailing list<br><a href="mailto:Merb-devel@rubyforge.org">Merb-devel@rubyforge.org</a><br><a href="http://rubyforge.org/mailman/listinfo/merb-devel">http://rubyforge.org/mailman/listinfo/merb-devel</a><br></blockquote>
</div><br>