milliseconds loss #49
mamdouni
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
We faced recently an issue in our tests using the @now expression, actually our tests fails 1 time per 10 let's say.
I think that we lose some nanoseconds after saving attributes of type date in our database. I tried to make a simple example that can be reproduced easily (without db interaction cause i think the issue is the same)
`
Feature: Test Dates
Scenario: Test 1
Given that the current time is 2020-11-01T00:00:00Z
Then now is equal to "2020-11-01T00:00:00Z"
Scenario: Test 2

Given that the current time is 2020-11-01T00:00:00.123Z
Then now is equal to "2020-11-01T00:00:00.123Z"
`
Can you tell me if this is a bug or just a misuse in my test ?
Beta Was this translation helpful? Give feedback.
All reactions