Skip to content
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

feat: test bi-directional syncing in update test #144

Closed
wants to merge 2 commits into from

Conversation

stbrody
Copy link
Collaborator

@stbrody stbrody commented Jun 13, 2024

Builds on #143.

Testing that syncing works in both directions in the update test lets us remove the (much slower and more expensive) ceramic-ceramic-integration.test.ts as then there's nothing it's testing that isn't covered by other tests

@stbrody stbrody self-assigned this Jun 13, 2024
Copy link

linear bot commented Jun 13, 2024

const expectedContent = { step: ComposeDbUrls.length }
// `step` is incremented once for the first r/w node and twice for each subsequent node,
// during the `update` test, so use the length of the r/w URL array to test the content.
const expectedContent = { step: 1 + (ComposeDbUrls.length - 1) * 2 }
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

note this is going to break the longevity tests for existing streams in the database that were created with the old version of the update test that had fewer steps. We might need to coordinate merging this PR with clearing out the dynamodb database to prevent spurious failures, unfortunately

@stbrody
Copy link
Collaborator Author

stbrody commented Jun 13, 2024

Nevermind! This test already tests syncing in both directions!

@stbrody stbrody closed this Jun 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant