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

Delete unnecessary recover error test #662

Merged
merged 1 commit into from
Aug 20, 2024
Merged

Delete unnecessary recover error test #662

merged 1 commit into from
Aug 20, 2024

Conversation

amnonbc
Copy link
Contributor

@amnonbc amnonbc commented Aug 19, 2024

The test removed in this commit expects that using an invalid recovery key leads to an ERROR protocol message being returned which thus fails the connection, but this isn't part of the spec, we make no guarantee that invalid recovery keys are rejected with an ERROR, and in fact returning a CONNECTED protocol message with the error field indicating the recovery key was invalid is a perfectly good response, which is what we will start to do in the future.

The RTN15c4 test was removed from ably-dotnet for this reason.
This PR removes it from ably-go.

Copy link
Collaborator

@sacOO7 sacOO7 left a comment

Choose a reason for hiding this comment

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

Btw, this test is related to spec https://sdk.ably.com/builds/ably/specification/main/features/#RTN15c4. Are we planning to remove spec since we are deleting related integration tests? This also means we are changing server behaviour not to act like RTN15c4

Copy link
Collaborator

@sacOO7 sacOO7 left a comment

Choose a reason for hiding this comment

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

lgtm

@lmars lmars merged commit f749c38 into main Aug 20, 2024
13 of 14 checks passed
@lmars lmars deleted the remove_RTN15c4 branch August 20, 2024 11:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants