-
Notifications
You must be signed in to change notification settings - Fork 821
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow zero/negative performance timings #1769
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1769 +/- ##
==========================================
- Coverage 92.62% 92.60% -0.02%
==========================================
Files 174 174
Lines 6049 6048 -1
Branches 1289 1288 -1
==========================================
- Hits 5603 5601 -2
- Misses 446 447 +1
|
@@ -185,19 +185,23 @@ describe('utils', () => { | |||
assert.strictEqual(args[1], 123); | |||
}); | |||
}); | |||
describe('when entry has time equal to 0', () => { | |||
describe('when entry is not numeric', () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you should still have unit test when time is 0 - this is basically what you are fixing in this PR right ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good call; I updated the positive test to check 0, a negative number, and a positive number.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Now @johnbley is an approver this meets merge requirements |
Which problem is this PR solving?
Short description of the changes