Comments (6)
That's odd. Are you sure you have no other calls to Timecop? The output prepended with "2." is particularly confusing. Based on what you're seeing in your scenarios (UTC time), I'd expect that to also be UTC time. Something isn't adding up.
from timecop.
Yes I know, thats really baffled me. All I can say so far is that going back to 0.3.1 fixed the problem. I will let you know if I find out anything else, or if I get some further ideas from the Cucumber mailing list.
from timecop.
I think I have a related issue. I had a test that failed unless I called Time.now.utc somewhere before the business logic executed. Reverting to 0.3.1 fixed it.
from timecop.
Interesting. Is there any way you can wrap this up into a tidy failing test case? Even a sample app that I can work with?
from timecop.
Here's the output from an irb session (Rails 2.3.5 console session, to be exact) replicating this bug. http://gist.github.com/416133
from timecop.
A simple failing test case: http://github.com/lmarburger/timecop/commit/dbd59dd0806c1849633c62fac4d9eebf202c5702
Overridden methods in 0.3.4 always return the same instance of Time. I haven't been in the code long enough to know what a good solution would be, but my initial reaction is to return a cloned instance. Any objections?
from timecop.
Related Issues (20)
- Is call to Timecop.travel(some random time) atomic in nature? HOT 1
- Time#travel should be side-effect free and not resume system clock HOT 10
- .
- Timecop.thread_safe = true by default HOT 1
- Timecop handles GMT/UTC Time objects incorrectly HOT 2
- Doesn't work for `Rails.cache` with `expires_in` HOT 2
- ruby 3.1 support
- Date.strptime returns wrong month for %Y HOT 6
- %W is not handled properly HOT 1
- Ruby 2.5 seems to work? HOT 4
- Using timecop with psych 4.0.5, behavior differs between the test environment and other environments HOT 3
- Timecop.scale to mock existing times HOT 2
- Timecop.freeze not working with expect().to receive HOT 3
- Test
- Need a proper test for making sure we don't change timezones inadvertently
- DateTime parse without date not working properly HOT 5
- DateTime.parse("Wednesday 12:00") format is always returning midnight HOT 1
- Time.now sometimes has greater-than-nanosecond precision when called under Timecop.travel HOT 3
- DateTime.parse does not handle CWeek correctly
- Mocking `Process.clock_gettime` causes `Concurrent::IVar` with timeout to wait indefinitely HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from timecop.