Help us understand the problem. What is going on with this article?

Time.currentとDBに入れた値との比較テストを書くときに微妙に差が出てつらい問題

More than 3 years have passed since last update.
Timecop.freeze do
  hoge.activate!

  assert_equal Time.current, hogs.activated_at
end
No visible difference in the ActiveSupport::TimeWithZone#inspect output.

こんなのが出る。

調べてみると、

Time.current.to_f # => 1442454360.028926
hoge.activated_at # => 1442454360.0

microsecの差分のせいなので、そこを無視するようにTime.freezeする。

Timecop.freeze(Time.current.change(usec: 0))
Timecop.freeze(Time.current.change(usec: 0)) do
  hoge.activate!

  assert_equal Time.current, hogs.activated_at
end
Why not register and get more from Qiita?
  1. We will deliver articles that match you
    By following users and tags, you can catch up information on technical fields that you are interested in as a whole
  2. you can read useful information later efficiently
    By "stocking" the articles you like, you can search right away
Comments
No comments
Sign up for free and join this conversation.
If you already have a Qiita account
Why do not you register as a user and use Qiita more conveniently?
You need to log in to use this function. Qiita can be used more conveniently after logging in.
You seem to be reading articles frequently this month. Qiita can be used more conveniently after logging in.
  1. We will deliver articles that match you
    By following users and tags, you can catch up information on technical fields that you are interested in as a whole
  2. you can read useful information later efficiently
    By "stocking" the articles you like, you can search right away
ユーザーは見つかりませんでした