[9.x] Fix time mocking in CacheRepositoryTest #41824
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
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.
setTestNow()should not be done indataProvider. dataProvider in general shouldn't modify any state as they are triggered by PHPUnit in early steps and not related to the tests done with this provider.For this case (
CacheRepositoryTest) the time should be always mocked, else stuff like$repo->getStore()->shouldReceive('put')->once()->with('foo', 'bar', 602)can't be guaranteed because few microseconds elapsed sinceCarbon::now()->addMinutes(10)->addSeconds(2)was called.Relates to #41810, #40790