-
-
Notifications
You must be signed in to change notification settings - Fork 2
SlidingWindowCounter testing suite #78
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
Conversation
|
I am going to set all the tests to skip so that Travis does not fail on this PR |
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.
The tests seems reasonable for the most part. I think that they can benefit from
- additional assertions for success on the rate limiter response,
- clearer test names (e.g. fixed window is full => previous window is full)
- some additional tests for edge cases unique to sliding window.
There's a good chance I misinterpreted one of the tests. If you disagree/have questions let me know and we can discuss in person.
Good work!
…o jd/slideTest
…-Gate into jd/slideTest
evanmcneely
left a comment
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 did not go through all the math involved to check the expected results of the overlapping sliding window tests. This looks thorough and and covers all cases I can think about.
shalarewicz
left a comment
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.
Looks good! Great work. This should give us pretty thorough coverage.
|
Closes #78 |
Summary
Took TokenBucket tests as a template and added/removed a few tests specific to each limiting algorithm, respectively.
Type of Change
Issues
#70