fix(timecop gem): add support for Timecop 0.9.9 so that we could track proper tests' execution time when Process.clock_gettime
is mocked
#262
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.
Story
link to the internal story
Related
Changes introduced by Timecop 0.9.9:
Process.clock_gettime is mocked.
Process.clock_gettime
support travisjeffery/timecop#419Timecop 0.9.10 makes
Process.clock_gettime
optionally mocked. The default isTimecop.mock_process_clock = false
.Our old PRs related to time tracking and mocking time:
Description
Add support for Timecop 0.9.9 so that we could track proper tests' execution time when
Process.clock_gettime
is mocked.Changes
Process.clock_gettime
mocked by the Timecop gem.Checklist reminder
UNRELEASED
section of theCHANGELOG.md
, including the needed bump (ie, patch, minor, major)lib/knapsack_pro/pure/queue/rspec_pure.rb
contains pure functions that are unit tested.lib/knapsack_pro/extensions/rspec_extension.rb
encapsulates calls to RSpec internals and is integration and e2e tested.lib/knapsack_pro/runners/queue/rspec_runner.rb
invokes the pure code and the extension to produce side effects, which are integration and e2e tested.