-
Notifications
You must be signed in to change notification settings - Fork 127
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
Unit tests for GapWriter, using a new timeline mock utility #494
Conversation
return { | ||
"Backfilling an empty fragment": async assert => { | ||
const { txn, fragmentIdComparer, gapWriter, eventCreator } = await setup(); | ||
const emptyFragment = await createFragment(0, txn, fragmentIdComparer, { previousToken: startToken }); |
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.
can you extract the fragment id here in a variable and reuse it when you check for the results below in the store? Now the relation is implicit, by using EventKey.minKey which also happens to use fragmentId 0
, making the test work, but it's not apparent without knowing all of this.
Excellent work on the unit tests! Left some comments, and have some questions about the actual fix, we can discuss "in person" later on. |
Good to go, thanks again for this! |
No description provided.