Fix time specification #141
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 similar comments
philostler
reviewed
Sep 6, 2017
| @@ -155,9 +155,10 @@ expect(AwesomeJob).to have_enqueued_job('Awesome', true) | |||
| #### Testing scheduled jobs | |||
| *Use chainable matchers `#at` and `#in`* | |||
| ```ruby | |||
| Awesomejob.perform_at 5.minutes.from_now, 'Awesome', true | |||
| time = 5.minutes.from_now | |||
There was a problem hiding this comment.
Could you please explain how this is a fix for time specification?
There was a problem hiding this comment.
It is really kind of trivial. Two calls of 5.minutes.from_now may return different value because the current time is changing.
There was a problem hiding this comment.
Ah yes of course, that's great thanks.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.