Comments on: Time warp for Rails testing http://bjhess.com/blog/2007/08/12/time-warp-for-rails-testing/ Barry Hess, speaking in tongues. Sat, 22 Nov 2008 14:25:01 +0000 http://wordpress.org/?v=2.6.2 By: Barry http://bjhess.com/blog/2007/08/12/time-warp-for-rails-testing/#comment-11909 Barry Fri, 26 Oct 2007 02:04:33 +0000 http://bjhess.com/bjhessblog/2007/08/12/time-warp-for-rails-testing/#comment-11909 Thanks for the advice! Thanks for the advice!

]]> By: S. Potter http://bjhess.com/blog/2007/08/12/time-warp-for-rails-testing/#comment-11905 S. Potter Thu, 25 Oct 2007 07:17:28 +0000 http://bjhess.com/bjhessblog/2007/08/12/time-warp-for-rails-testing/#comment-11905 It sounds like you are really just trying to "stub" Time.now. If I were you I would use mocha (if you are still using Test::Unit) or use the fully integrated BDD framework, rSpec. Both mocha and rspec are open source projects hosted on Rubyforge. To "stub" the now class method on Time in rSpec you would do: Time.stub!(:now).and_return(stored_time) In mocha (though it has been a while since I used it so not sure of exact API) you could do something like: Time.expects(:now).returns(stored_time) HTH It sounds like you are really just trying to “stub” Time.now. If I were you I would use mocha (if you are still using Test::Unit) or use the fully integrated BDD framework, rSpec.

Both mocha and rspec are open source projects hosted on Rubyforge.

To “stub” the now class method on Time in rSpec you would do:

Time.stub!(:now).and_return(stored_time)

In mocha (though it has been a while since I used it so not sure of exact API) you could do something like:

Time.expects(:now).returns(stored_time)

HTH

]]> By: bjhess http://bjhess.com/blog/2007/08/12/time-warp-for-rails-testing/#comment-11478 bjhess Fri, 24 Aug 2007 21:46:45 +0000 http://bjhess.com/bjhessblog/2007/08/12/time-warp-for-rails-testing/#comment-11478 <p>That worked beautifully. Thanks, hugocf! Make sure to correct things out at dzone.</p> <p>As for formatting, I have Markdown running somewhere in here. I think that's what got ya!</p> That worked beautifully. Thanks, hugocf! Make sure to correct things out at dzone.

As for formatting, I have Markdown running somewhere in here. I think that’s what got ya!

]]> By: hugocf http://bjhess.com/blog/2007/08/12/time-warp-for-rails-testing/#comment-11475 hugocf Fri, 24 Aug 2007 14:20:56 +0000 http://bjhess.com/bjhessblog/2007/08/12/time-warp-for-rails-testing/#comment-11475 <p>(geee... :) I really can't get your comments markup right!)</p> (geee… :) I really can’t get your comments markup right!)

]]> By: hugocf http://bjhess.com/blog/2007/08/12/time-warp-for-rails-testing/#comment-11474 hugocf Fri, 24 Aug 2007 14:19:30 +0000 http://bjhess.com/bjhessblog/2007/08/12/time-warp-for-rails-testing/#comment-11474 <p>Mate, i think i might have found the "reason" for our +SystemStackError+ error. It reappeared using the `time_helper.rb` once I included it in _one-too-many_ test file.</p> <p>It has something to do with getting into a recursive declaration look, when the Time class is redefined over and over again.</p> <p>By making sure it only extends the Time class <em>once</em>, time error went away. </p> <p>See the "unless" clause wrapping the Time definition in the "time_helper.rb"</p> <p><code> unless Time.respond_to? :real_now # prevent the error: stack level too deep (SystemStackError) class Time #:nodoc: class <<self #... the same stuff as before end end end </code></p> <p>(ed: fixed some markup)</p> Mate, i think i might have found the “reason” for our +SystemStackError+ error. It reappeared using the `time_helper.rb` once I included it in _one-too-many_ test file.

It has something to do with getting into a recursive declaration look, when the Time class is redefined over and over again.

By making sure it only extends the Time class once, time error went away.

See the “unless” clause wrapping the Time definition in the “time_helper.rb”


unless Time.respond_to? :real_now # prevent the error: stack level too deep (SystemStackError)
  class Time #:nodoc:
    class <<self
      #... the same stuff as before
    end
  end
end

(ed: fixed some markup)

]]> By: hugocf http://bjhess.com/blog/2007/08/12/time-warp-for-rails-testing/#comment-11472 hugocf Fri, 24 Aug 2007 11:39:07 +0000 http://bjhess.com/bjhessblog/2007/08/12/time-warp-for-rails-testing/#comment-11472 <p>well, at least for me, "pretend<em>now</em>is()" reads as something like absolute positioning the current time and not relative to the latest timeshift eventually made before...</p> <p>.. but anyways, there's always more than one way of reading :)</p> well, at least for me, “pretendnowis()” reads as something like absolute positioning the current time and not relative to the latest timeshift eventually made before…

.. but anyways, there’s always more than one way of reading :)

]]> By: bjhess http://bjhess.com/blog/2007/08/12/time-warp-for-rails-testing/#comment-11471 bjhess Fri, 24 Aug 2007 10:22:59 +0000 http://bjhess.com/bjhessblog/2007/08/12/time-warp-for-rails-testing/#comment-11471 <p>Thanks. And thanks for sharing your other glitch. Although I wonder if it would be more appropriate to set the Time offset to 0 at the beginning of that test?</p> Thanks. And thanks for sharing your other glitch. Although I wonder if it would be more appropriate to set the Time offset to 0 at the beginning of that test?

]]> By: hugocf http://bjhess.com/blog/2007/08/12/time-warp-for-rails-testing/#comment-11467 hugocf Fri, 24 Aug 2007 03:22:03 +0000 http://bjhess.com/bjhessblog/2007/08/12/time-warp-for-rails-testing/#comment-11467 <p>Yes, it was the snipped that I originally found, but thought you were the creator.</p> <p>Nevertheless, your post was gold! ;)</p> <p>I've also found minor glitch on the original cod, which I posted back to the <a href="http://snippets.dzone.com/posts/show/1738" rel="nofollow">snippet</a> page. You might find it useful to take a look.</p> <p>(ed: I fixed the link.)</p> Yes, it was the snipped that I originally found, but thought you were the creator.

Nevertheless, your post was gold! ;)

I’ve also found minor glitch on the original cod, which I posted back to the snippet page. You might find it useful to take a look.

(ed: I fixed the link.)

]]> By: bjhess http://bjhess.com/blog/2007/08/12/time-warp-for-rails-testing/#comment-11466 bjhess Fri, 24 Aug 2007 02:00:34 +0000 http://bjhess.com/bjhessblog/2007/08/12/time-warp-for-rails-testing/#comment-11466 <p>Thanks,</p> <p>I must admit, though, that I didn't originate the code. I found the base code <a href="http://snippets.dzone.com/posts/show/1738" rel="nofollow">here</a> at snippets.dzone.com. (That's an excellent site, by the way.)</p> <p>My post was mainly to describe an error in using the code and my fix. I'm happy that helped you!</p> Thanks,

I must admit, though, that I didn’t originate the code. I found the base code here at snippets.dzone.com. (That’s an excellent site, by the way.)

My post was mainly to describe an error in using the code and my fix. I’m happy that helped you!

]]> By: hugocf http://bjhess.com/blog/2007/08/12/time-warp-for-rails-testing/#comment-11465 hugocf Fri, 24 Aug 2007 01:45:15 +0000 http://bjhess.com/bjhessblog/2007/08/12/time-warp-for-rails-testing/#comment-11465 <p>Congrats for the wonderful code! This time-based testing thing u wrote is great! </p> <p>Unfortunately, I too was at a loss with the stack-thingy, and at ~3am the brain isn't properly now... u can't imagine the joy of getting the answer straight from on the one-and-only hit google gave me! </p> <p>Love it when things work!!! :)</p> <p>(... now, back to work!)</p> Congrats for the wonderful code! This time-based testing thing u wrote is great!

Unfortunately, I too was at a loss with the stack-thingy, and at ~3am the brain isn’t properly now… u can’t imagine the joy of getting the answer straight from on the one-and-only hit google gave me!

Love it when things work!!! :)

(… now, back to work!)

]]>