How about both top and bottom posting?
Francis Hwang
http://fhwang.net/
On May 6, 2009, at 8:46 PM, Ben Mabey wrote:
lol.. Yes. :) Sarcasm somethings doesn't come across well over
email I suppose.
How about both top and bottom posting?
Francis Hwang
http://fhwan
uot;it should do this"
> it "should do this" do
> puts "runs in transaction=#{self.run_in_transaction?}"
> end
> runs as expected, providing false when the uses_transaction is set, and true
> otherwise (assuming config.use_transactional_fixtures = true).
> R
On Wed, May 6, 2009 at 9:47 AM, Nicholas Van Weerdenburg
wrote:
> As far as I can tell, RSpec simply uses inherited TestCase capabilities for
> transactions, including use_transactional_fixtures (it's config setting is
> simply passed on) and likely uses_transaction.
> I'm guessing you can do some
Sorry if this has been answered elsewhere, Google was not very helpful
to me on this one. If I'm running a model spec and am one of those
benighted souls who wants to hit the DB while doing so, is there a way
for me to tell RSpec to skip transactions? In Test::Unit I can say
"uses_transaction :test
Yup, that's exactly what I needed -- thanks,
Francis Hwang
http://fhwang.net/
On Jul 9, 2008, at 9:53 PM, David Chelimsky wrote:
On Jul 9, 2008, at 5:36 PM, Francis Hwang wrote:
... is there a way to do this? We have some REST-ish POSTs we'd
like to spec out. In the controller
... is there a way to do this? We have some REST-ish POSTs we'd like
to spec out. In the controller this gets accessed with
request.raw_post.to_s, is there a way to set this with rspec?
Thanks as always,
Francis
___
rspec-users mailing list
rspec-u
ifting to try to nail down with a well-structured design. Sometimes
you just release code that amorphously hints at a future design --
and in those cases, a strong test suite is what prevents you from
shooting yourself in the foot.
Francis Hwang
http://fhwang.net/
that are easier to test is a great advantage to how we all
worked 10 or more years ago ... I suspect part of that luxury
translates in being able to actually design _less_, since the cost of
fixing our design mistakes in the future goes down significantly.
Francis Hwang
http://fhwang.net/
_
On Dec 30, 2007, at 1:52 PM, Jay Levitt wrote:
> On 12/29/2007 5:46 PM, Francis Hwang wrote:
>
>> - How quickly the business needs change. Designs for medical imaging
>> software are likely to change less quickly than those of a consumer-
>> facing website, which means you
On Dec 30, 2007, at 1:42 AM, Zach Dennis wrote:
> On Dec 29, 2007 5:46 PM, Francis Hwang <[EMAIL PROTECTED]> wrote:
>> I don't know if anyone else will find this thought useful, but:
>>
>>
>> I think different programmers have different situations, and
my life neatening up. And if I do lose
something, I may not find it instantly, but I can spend a little
while and look for it. It's got to be somewhere in my apartment, and
the whole thing's not even that big.
Francis Hwang
http://fhwang.net/
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
Arg, please disregard that last email. My route and my request are
just different; I had to actually write that crazy long email, send
it out, and then read it again to see the mistake.
Francis Hwang
http://fhwang.net/
On Dec 23, 2007, at 9:23 AM, Francis Hwang wrote:
> Hey all,
ge? works
correctly, and link_to_unless_current works correctly.
But, when I'm running current_page? from my spec, I get "/writing"
for url_string and "/abstracts?index%5Bselect%5D=new" for
@controller.request.request_uri -- so current_page? works incorrectly
and so does l
rts of mocks is much more time-consuming.
If you haven't seen it before, Martin Fowler has a pretty good
article about the differences in styles: http://martinfowler.com/
articles/mocksArentStubs.html
Francis Hwang
http://fhwang.net/
On Dec 16, 2007, at 5:59 PM, Dan North wrote:
documents', :action => 'show'
Is there a way to have a controller spec test site-wide routing? It
seems to me that the get and post methods are just controller-
specific routing. If I can't do it in a controller spec, where else
s
at in RSpec. Is there a less-documented feature
I'm missing?
Thanks,
Francis Hwang
http://fhwang.net/
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
16 matches
Mail list logo
