-
Notifications
You must be signed in to change notification settings - Fork 26
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
RTL6c #406
Conversation
LGTM but will be revisited following @tcard's updates to the spe |
PTAL |
(By the way, that's up to date with ably/docs#112.) |
It wasn't really testing the right thing. Should test when connection is _already_ CONNECTED.
According to ably/docs#112.
} | ||
|
||
// RTL6c2 | ||
context("the message should be queued and delivered as soon as the connection state returns to CONNECTED if the connection is") { |
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.
The tests in this context test the message should be queued
, but don't test and delivered as soon as the connection state returns to CONNECTED
. Should we?
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.
It is tested. All of them are calling a local publish
function (line 1150) which publishes and waits for the callback. Or do you want to also subscribe to the channel and check if it's received? I don't think that's necessary, as other tests already prove that the publish callback is called upon successful delivery.
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.
Yes, you are right, leave as is
One comment but otherwise great 👍 |
No description provided.