Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Add acceptance tests for per-stream state updates #14263
Add acceptance tests for per-stream state updates #14263
Changes from all commits
cf8cb58
a34d35f
441f131
9a4958e
0f2aa6a
9c3bbe2
65964e0
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Is someone else working on an acceptance test to test actual per-stream resets, i.e. sync a few streams, reset one of them, and verify that only that one stream is reset in the destination and that the state looks correct?
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.
@gosusnp is. We paired today so his question about how the acceptance test are working are answered.
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.
Not exactly, I am currently working on an acceptance test for current reset behavior. I am happy to help out on that test afterwards.
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 have some room, I will work on those.
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.
My comment was more about having a check on the state type, like using the new repository done by Jimmy and check that it is legacy here. WDYT?
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.
Yeah I think it would be useful if in every place in this test where we are currently calling and just logging
apiClient.getConnectionApi().getState()
, we instead explicitly check that theConnectionState
object that was returned has the expectedstateType
and the expected state/globalState/streamState field is set to the expected value.E.g. I think after sync 1, we expect it to be a
LEGACY
state. After sync 2, we expect aSTREAM
state. After the reset, we expect aNOT_SET
state. And after sync 3, we expect aSTREAM
state again.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.
Yeah, That sounds closer to the acceptance test spirit to use the API to do any operation
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.
This will depend on our ability to control the feature flag (Passing it to the container that have the flag). This is what I am investigating at the moment but for now it should always be
LEGACY
.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.
@benmoriceau I think we can do that as a separate PR once everything is ready for use. For now, this is verifying that the existing state stuff works even with the updated connector.