-
Notifications
You must be signed in to change notification settings - Fork 487
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
FastCatchup - add unit testing for ledgerFetcher #1147
FastCatchup - add unit testing for ledgerFetcher #1147
Conversation
Fix typos
…against out-of-order committedUpTo calls. ( based on unit test only. no actual required by production code ).
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.
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.
Would be nice to have a happy case test as well
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.
Mostly looks good to my eyes, my only real concern is the pointer return discrepancy I commented.
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.
All looks good!
definitely. I'm planning to get there. however, I'm trying to prioritize the use cases which aren't covered at all by other tests first. The success case is covered by the e2e test, so it "defaults" to have a lower priority. |
Summary
Add testing for the ledgerFetcher
Notes