<testsuite name="rspec2" tests="765" skipped="2" failures="0" errors="0" time="643.102538" timestamp="2024-05-29T09:58:12+00:00" hostname="fv-az1014-148">
<properties>
<property name="seed" value="56032"/>
</properties>
<testcase classname="spec.acceptance.rest.encoders_spec" name="Ably::Models::MessageEncoders with binary transport protocol with encryption with UTF-8 data applies utf-8 and cipher encoding and sets the encoding attribute to &quot;utf-8/cipher+aes-128-cbc&quot;" file="./spec/acceptance/rest/encoders_spec.rb" time="0.008415"></testcase>
<testcase classname="spec.acceptance.rest.encoders_spec" name="Ably::Models::MessageEncoders with binary transport protocol with encryption with JSON data applies json, utf-8 and cipher encoding and sets the encoding attribute to &quot;json/utf-8/cipher+aes-128-cbc&quot;" file="./spec/acceptance/rest/encoders_spec.rb" time="0.002377"></testcase>
<testcase classname="spec.acceptance.rest.encoders_spec" name="Ably::Models::MessageEncoders with binary transport protocol with encryption with binary data applies cipher encoding and sets the encoding attribute to &quot;cipher+aes-128-cbc&quot;" file="./spec/acceptance/rest/encoders_spec.rb" time="0.002121"></testcase>
<testcase classname="spec.acceptance.rest.encoders_spec" name="Ably::Models::MessageEncoders with binary transport protocol without encryption with binary data does not apply any encoding" file="./spec/acceptance/rest/encoders_spec.rb" time="0.002228"></testcase>
<testcase classname="spec.acceptance.rest.encoders_spec" name="Ably::Models::MessageEncoders with binary transport protocol without encryption with JSON data stringifies the JSON and sets the encoding attribute to &quot;json&quot;" file="./spec/acceptance/rest/encoders_spec.rb" time="0.001652"></testcase>
<testcase classname="spec.acceptance.rest.encoders_spec" name="Ably::Models::MessageEncoders with binary transport protocol without encryption with UTF-8 data does not apply any encoding" file="./spec/acceptance/rest/encoders_spec.rb" time="0.001468"></testcase>
<testcase classname="spec.acceptance.rest.encoders_spec" name="Ably::Models::MessageEncoders with text transport protocol without encryption with binary data applies a base64 encoding and sets the encoding attribute to &quot;base64&quot;" file="./spec/acceptance/rest/encoders_spec.rb" time="0.001620"></testcase>
<testcase classname="spec.acceptance.rest.encoders_spec" name="Ably::Models::MessageEncoders with text transport protocol without encryption with UTF-8 data does not apply any encoding" file="./spec/acceptance/rest/encoders_spec.rb" time="0.001587"></testcase>
<testcase classname="spec.acceptance.rest.encoders_spec" name="Ably::Models::MessageEncoders with text transport protocol without encryption with JSON data stringifies the JSON and sets the encoding attribute to &quot;json&quot;" file="./spec/acceptance/rest/encoders_spec.rb" time="0.001677"></testcase>
<testcase classname="spec.acceptance.rest.encoders_spec" name="Ably::Models::MessageEncoders with text transport protocol with encryption with binary data applies cipher and base64 encoding and sets the encoding attribute to &quot;cipher+aes-128-cbc/base64&quot;" file="./spec/acceptance/rest/encoders_spec.rb" time="0.002219"></testcase>
<testcase classname="spec.acceptance.rest.encoders_spec" name="Ably::Models::MessageEncoders with text transport protocol with encryption with UTF-8 data applies utf-8, cipher and base64 encodings and sets the encoding attribute to &quot;utf-8/cipher+aes-128-cbc/base64&quot;" file="./spec/acceptance/rest/encoders_spec.rb" time="0.002199"></testcase>
<testcase classname="spec.acceptance.rest.encoders_spec" name="Ably::Models::MessageEncoders with text transport protocol with encryption with JSON data applies json, utf-8, cipher and base64 encoding and sets the encoding attribute to &quot;json/utf-8/cipher+aes-128-cbc/base64&quot;" file="./spec/acceptance/rest/encoders_spec.rb" time="0.002193"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #presence returns a Ably::Realtime::Presence object" file="./spec/acceptance/realtime/channel_spec.rb" time="0.353670"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when it receives an ERROR ProtocolMessage should transition to the failed state and the error_reason should be set (#RTL14)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.320216"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #subscribe with no event argument subscribes for all events" file="./spec/acceptance/realtime/channel_spec.rb" time="0.435248"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #subscribe many times with different event names filters events accordingly to each callback" file="./spec/acceptance/realtime/channel_spec.rb" time="2.452164"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #subscribe with an event argument subscribes for a single event" file="./spec/acceptance/realtime/channel_spec.rb" time="0.320267"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #subscribe before attach receives messages as soon as attached" file="./spec/acceptance/realtime/channel_spec.rb" time="0.351241"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #subscribe with a callback that raises an exception logs the error and continues" file="./spec/acceptance/realtime/channel_spec.rb" time="1.386525"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol channel state change emits a ChannelStateChange object" file="./spec/acceptance/realtime/channel_spec.rb" time="0.317353"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol channel state change ChannelStateChange object has an empty reason when there is no error" file="./spec/acceptance/realtime/channel_spec.rb" time="0.335246"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol channel state change ChannelStateChange object has current state" file="./spec/acceptance/realtime/channel_spec.rb" time="0.293941"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol channel state change ChannelStateChange object has the event that generated the state change (#TA5)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.332980"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol channel state change ChannelStateChange object contains a private API protocol_message attribute that is used for special state change events" file="./spec/acceptance/realtime/channel_spec.rb" time="0.294264"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol channel state change ChannelStateChange object has a previous state" file="./spec/acceptance/realtime/channel_spec.rb" time="0.320217"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol channel state change ChannelStateChange object on failure has a reason Error object when there is an error on the channel" file="./spec/acceptance/realtime/channel_spec.rb" time="0.316725"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol channel state change ChannelStateChange object #resume (#RTL2f) is false when a channel first attaches" file="./spec/acceptance/realtime/channel_spec.rb" time="0.318703"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol channel state change ChannelStateChange object #resume (#RTL2f) is true when a connection is recovered and the channel is attached" file="./spec/acceptance/realtime/channel_spec.rb" time="0.631881"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol channel state change ChannelStateChange object #resume (#RTL2f) is false when a connection fails to recover and the channel is attached" file="./spec/acceptance/realtime/channel_spec.rb" time="0.600077"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol channel state change ChannelStateChange object #resume (#RTL2f) when a resume fails is false when a resume fails to recover and the channel is automatically re-attached" file="./spec/acceptance/realtime/channel_spec.rb" time="0.551626"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol channel state change moves to suspended all published messages awaiting an ACK do nothing (#RTL11a)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.998502"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol channel state change moves to suspended all queued messages fail with NACK (#RTL11)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.298347"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol channel state change moves to failed all published messages awaiting an ACK do nothing (#RTL11a)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.962513"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol channel state change moves to failed all queued messages fail with NACK (#RTL11)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.308269"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol automatic channel recovery if a subsequent ATTACHED is received on an ATTACHED channel emits an UPDATE only when resumed is true (#RTL12)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.307117"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol automatic channel recovery if a subsequent ATTACHED is received on an ATTACHED channel ignores the additional ATTACHED if resumed is true (#RTL12)" file="./spec/acceptance/realtime/channel_spec.rb" time="1.321959"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol automatic channel recovery if a subsequent ATTACHED is received on an ATTACHED channel emits an UPDATE when resumed is true and includes the reason error from the ProtocolMessage (#RTL12)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.306320"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol automatic channel recovery when an ATTACH request times out moves to the SUSPENDED state (#RTL4f)" file="./spec/acceptance/realtime/channel_spec.rb" time="2.275220"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish #(RTL17) when channel is failed errors when trying to send a message" file="./spec/acceptance/realtime/channel_spec.rb" time="0.305137"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish #(RTL17) when channel is detaching stops sending message" file="./spec/acceptance/realtime/channel_spec.rb" time="0.319888"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish #(RTL17) when channel is initialized sends messages only on attach" file="./spec/acceptance/realtime/channel_spec.rb" time="0.311037"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish #(RTL17) when channel is detached stops sending message" file="./spec/acceptance/realtime/channel_spec.rb" time="0.341075"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish #(RTL17) when channel is attaching sends messages only on attach" file="./spec/acceptance/realtime/channel_spec.rb" time="0.309799"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish with name and data arguments publishes the message and return true indicating success" file="./spec/acceptance/realtime/channel_spec.rb" time="0.401100"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish with name and data arguments and additional attributes publishes the message with the attributes and return true indicating success" file="./spec/acceptance/realtime/channel_spec.rb" time="0.391073"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish with name and data arguments and additional invalid attributes throws an exception" file="./spec/acceptance/realtime/channel_spec.rb" time="0.154344"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish when channel is not attached in state Initializing (#RTL6c1) publishes messages immediately and does not implicitly attach (#RTL6c1)" file="./spec/acceptance/realtime/channel_spec.rb" time="1.634748"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish when channel is Detaching (#RTL6c1) publishes messages immediately (#RTL6c1)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.668161"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish with an array of Message objects publishes an array of messages in one ProtocolMessage" file="./spec/acceptance/realtime/channel_spec.rb" time="0.429317"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish with an array of Message objects with two invalid message out of 12 before client_id is known (validated) calls the errback once" file="./spec/acceptance/realtime/channel_spec.rb" time="0.431305"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish with an array of Message objects with two invalid message out of 12 when client_id is known (validated) raises an exception" file="./spec/acceptance/realtime/channel_spec.rb" time="0.159905"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish with an array of Message objects only invalid messages when client_id is known (validated) raises an exception" file="./spec/acceptance/realtime/channel_spec.rb" time="0.155073"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish with an array of Message objects only invalid messages before client_id is known (validated) calls the errback once" file="./spec/acceptance/realtime/channel_spec.rb" time="0.421308"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish with an array of Message objects nil attributes when data is nil publishes the message without a data attribute in the payload" file="./spec/acceptance/realtime/channel_spec.rb" time="0.885084"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish with an array of Message objects nil attributes when name is nil publishes the message without a name attribute in the payload" file="./spec/acceptance/realtime/channel_spec.rb" time="0.891410"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish with an array of Message objects nil attributes with neither name or data attributes publishes the message without any attributes in the payload" file="./spec/acceptance/realtime/channel_spec.rb" time="0.388602"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish with more than allowed messages in a single publish rejects the publish" file="./spec/acceptance/realtime/channel_spec.rb" time="0.157636"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish with many many messages and many connections simultaneously publishes all messages, all success callbacks are called, and a history request confirms all messages were published" file="./spec/acceptance/realtime/channel_spec.rb" time="1.505111"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish with an array of Hash objects with :name and :data attributes publishes an array of messages in one ProtocolMessage" file="./spec/acceptance/realtime/channel_spec.rb" time="0.406852"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish with :queue_messages client option set to false (#RTL6c4) and connection state initialized (#RTL6c4) fails the deferrable" file="./spec/acceptance/realtime/channel_spec.rb" time="0.153497"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish with :queue_messages client option set to false (#RTL6c4) and connection state closed (#RTL6c4) fails the deferrable" file="./spec/acceptance/realtime/channel_spec.rb" time="0.298980"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish with :queue_messages client option set to false (#RTL6c4) and the channel state is failed (#RTL6c4) fails the deferrable" file="./spec/acceptance/realtime/channel_spec.rb" time="0.303001"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish with :queue_messages client option set to false (#RTL6c4) and connection state closing (#RTL6c4) fails the deferrable" file="./spec/acceptance/realtime/channel_spec.rb" time="0.271836"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish with :queue_messages client option set to false (#RTL6c4) and connection state connecting (#RTL6c4) fails the deferrable" file="./spec/acceptance/realtime/channel_spec.rb" time="0.156226"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish with :queue_messages client option set to false (#RTL6c4) and connection state suspended (#RTL6c4) fails the deferrable" file="./spec/acceptance/realtime/channel_spec.rb" time="0.282131"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish with :queue_messages client option set to false (#RTL6c4) and connection state connected (#RTL6c4) publishes the message" file="./spec/acceptance/realtime/channel_spec.rb" time="0.270160"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish with :queue_messages client option set to false (#RTL6c4) and connection state disconnected (#RTL6c4) fails the deferrable" file="./spec/acceptance/realtime/channel_spec.rb" time="0.270733"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish when channel is Attaching (#RTL6c1) publishes messages immediately (#RTL6c1)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.623250"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish message size exceeded (#TO3l8) and max_message_size is nil and the message size is 30 bytes should allow to send a message" file="./spec/acceptance/realtime/channel_spec.rb" time="0.330467"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish message size exceeded (#TO3l8) and max_message_size is nil and the message size is 65537 bytes should not allow to send a message" file="./spec/acceptance/realtime/channel_spec.rb" time="0.269175"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish message size exceeded (#TO3l8) and max_message_size is default (65536 bytes) should not allow to send a message (700000 bytes)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.269450"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish message size exceeded (#TO3l8) and max_message_size is default (65536 bytes) should allow to send a message (32 bytes)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.325105"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish message size exceeded (#TO3l8) and max_message_size is customized (11 bytes) and the message size is 30 bytes should not allow to send a message" file="./spec/acceptance/realtime/channel_spec.rb" time="0.273423"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish when channel is attached (#RTL6c1) publishes messages" file="./spec/acceptance/realtime/channel_spec.rb" time="0.337058"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish identified clients when anonymous and no client_id with an empty client_id in the message succeeds and publishes with an implicit client_id" file="./spec/acceptance/realtime/channel_spec.rb" time="0.851713"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish identified clients when anonymous and no client_id with a client_id in the message throws an exception" file="./spec/acceptance/realtime/channel_spec.rb" time="0.187561"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish identified clients when anonymous and no client_id with a wildcard client_id in the message throws an exception" file="./spec/acceptance/realtime/channel_spec.rb" time="0.189257"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish identified clients when authenticated with a wildcard client_id with a non-String client_id in the message throws an exception" file="./spec/acceptance/realtime/channel_spec.rb" time="0.185372"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish identified clients when authenticated with a wildcard client_id with a wildcard client_id in the message throws an exception" file="./spec/acceptance/realtime/channel_spec.rb" time="0.258788"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish identified clients when authenticated with a wildcard client_id with an empty client_id in the message succeeds and publishes without a client_id" file="./spec/acceptance/realtime/channel_spec.rb" time="0.837518"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish identified clients when authenticated with a wildcard client_id with a valid client_id in the message succeeds" file="./spec/acceptance/realtime/channel_spec.rb" time="28.755367"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish identified clients when authenticated with a valid client_id with an empty client_id in the message succeeds and publishes with an implicit client_id" file="./spec/acceptance/realtime/channel_spec.rb" time="0.857147"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish identified clients when authenticated with a valid client_id with an invalid client_id in the message throws an exception" file="./spec/acceptance/realtime/channel_spec.rb" time="0.186169"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish identified clients when authenticated with a valid client_id with a valid client_id succeeds" file="./spec/acceptance/realtime/channel_spec.rb" time="0.869152"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish identified clients when authenticated with a valid client_id with a wildcard client_id in the message throws an exception" file="./spec/acceptance/realtime/channel_spec.rb" time="0.185713"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish identified clients when authenticated with a Token string with an implicit client_id after the client is CONNECTED and the client&apos;s identity is known with an empty client_id in the message succeeds and publishes with an implicit client_id" file="./spec/acceptance/realtime/channel_spec.rb" time="0.847288"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish identified clients when authenticated with a Token string with an implicit client_id after the client is CONNECTED and the client&apos;s identity is known with a valid client_id in the message succeeds" file="./spec/acceptance/realtime/channel_spec.rb" time="0.846255"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish identified clients when authenticated with a Token string with an implicit client_id after the client is CONNECTED and the client&apos;s identity is known with an invalid client_id in the message throws an exception" file="./spec/acceptance/realtime/channel_spec.rb" time="0.310886"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish identified clients when authenticated with a Token string with an implicit client_id before the client is CONNECTED and the client&apos;s identity has been obtained with an empty client_id in the message succeeds and publishes with an implicit client_id" file="./spec/acceptance/realtime/channel_spec.rb" time="0.878052"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish identified clients when authenticated with a Token string with an implicit client_id before the client is CONNECTED and the client&apos;s identity has been obtained with an invalid client_id in the message succeeds in the client library but then fails when delivered to Ably" file="./spec/acceptance/realtime/channel_spec.rb" time="0.688986"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish identified clients when authenticated with a Token string with an implicit client_id before the client is CONNECTED and the client&apos;s identity has been obtained with a valid client_id in the message succeeds" file="./spec/acceptance/realtime/channel_spec.rb" time="0.866199"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #publish when channel is Detached (#RTL6c1) publishes messages immediately (#RTL6c1)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.659506"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol initialization with :auto_connect option set to false on connection opens a connection implicitly on #attach" file="./spec/acceptance/realtime/channel_spec.rb" time="0.302701"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol initialization with :auto_connect option set to false on connection remains initialized when accessing a channel" file="./spec/acceptance/realtime/channel_spec.rb" time="2.155664"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when connection state changes to :suspended an :attaching channel transitions state to :suspended (#RTL3c)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.156324"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when connection state changes to :suspended a :failed channel remains in the :failed state and retains the error_reason (#RTL3c)" file="./spec/acceptance/realtime/channel_spec.rb" time="1.318118"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when connection state changes to :suspended an :attached channel transitions state to :suspended (#RTL3c)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.304748"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when connection state changes to :suspended an :attached channel reattaching (#RTN15c3) sends ATTACH_RESUME flag when reattaching (RTL4j)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.438472"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when connection state changes to :suspended an :attached channel reattaching (#RTN15c3) transitions state automatically to :attaching once the connection is re-established " file="./spec/acceptance/realtime/channel_spec.rb" time="0.433318"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when connection state changes to :suspended a :detached channel remains in the :detached state (#RTL3c)" file="./spec/acceptance/realtime/channel_spec.rb" time="1.393551"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when connection state changes to :suspended a channel ATTACH request when connection SUSPENDED (#RTL4b) fails the deferrable" file="./spec/acceptance/realtime/channel_spec.rb" time="0.262812"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when connection state changes to :failed an :attached channel updates the channel error_reason (#RTL3a)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.307899"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when connection state changes to :failed an :attached channel transitions state to :failed (#RTL3a)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.308326"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when connection state changes to :failed a :detached channel remains in the :detached state (#RTL3a)" file="./spec/acceptance/realtime/channel_spec.rb" time="1.347123"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when connection state changes to :failed a channel ATTACH request fails the deferrable (#RTL4b)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.260325"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when connection state changes to :failed a :failed channel remains in the :failed state and ignores the failure error (#RTL3a)" file="./spec/acceptance/realtime/channel_spec.rb" time="1.334218"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when connection state changes to :failed an :attaching channel transitions state to :failed (#RTL3a)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.279265"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when connection state changes to :closed a :detached channel remains in the :detached state (#RTL3b)" file="./spec/acceptance/realtime/channel_spec.rb" time="1.359551"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when connection state changes to :closed a channel ATTACH request when connection CLOSED fails the deferrable (#RTL4b)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.294281"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when connection state changes to :closed an :attaching channel (#RTL3b) transitions state to :detached" file="./spec/acceptance/realtime/channel_spec.rb" time="0.155549"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when connection state changes to :closed a :failed channel remains in the :failed state and retains the error_reason (#RTL3b)" file="./spec/acceptance/realtime/channel_spec.rb" time="1.316684"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when connection state changes to :closed an :attached channel transitions state to :detached (#RTL3b)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.338097"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when connection state changes to :closed a channel ATTACH request when connection CLOSING fails the deferrable (#RTL4b)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.281849"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when connection state changes to :connected a :suspended channel is automatically reattached (#RTL3d)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.440879"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when connection state changes to :connected a :suspended channel when re-attach attempt fails returns to a suspended state (#RTL3d)" file="./spec/acceptance/realtime/channel_spec.rb" time="2.447264"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when connection state changes to :disconnected with a detached channel has no effect on the channel states (#RTL3e)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.331765"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when connection state changes to :disconnected with a failed channel has no effect on the channel states (#RTL3e)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.334458"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when connection state changes to :disconnected with an attached channel has no effect on the channel states (#RTL3e)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.304266"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when connection state changes to :disconnected with an attaching channel has no effect on the channel states (#RTL3e)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.269680"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when connection state changes to :disconnected with an initialized channel has no effect on the channel states (#RTL3e)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.269134"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #unsubscribe with no event argument unsubscribes for a single event" file="./spec/acceptance/realtime/channel_spec.rb" time="1.300302"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #unsubscribe with an event argument unsubscribes for a single event" file="./spec/acceptance/realtime/channel_spec.rb" time="1.306401"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #set_options (#RTL16a) when channel is attaching behaves like an update that sends ATTACH message sends an ATTACH message on options change" file="./spec/acceptance/realtime/channel_spec.rb" time="0.321182"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #set_options (#RTL16a) when channel is attaching behaves like an update that sends ATTACH message sends an ATTACH message on options change" file="./spec/acceptance/realtime/channel_spec.rb" time="0.201299"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #set_options (#RTL16a) when channel is initialized doesn&apos;t send ATTACH message" file="./spec/acceptance/realtime/channel_spec.rb" time="0.153465"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when it receives a server-initiated DETACHED (#RTL13) and channel is attached reattaches immediately (#RTL13a) with ATTACH_RESUME flag(RTL4j)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.338097"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when it receives a server-initiated DETACHED (#RTL13) and channel is failed does nothing (#RTL13)" file="./spec/acceptance/realtime/channel_spec.rb" time="1.341918"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when it receives a server-initiated DETACHED (#RTL13) and channel is suspended reattaches immediately (#RTL13a) with ATTACH_RESUME flag(RTL4j)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.336339"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when it receives a server-initiated DETACHED (#RTL13) and channel is suspended when connection is no longer connected will not attempt to reattach (#RTL13c)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.337982"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when it receives a server-initiated DETACHED (#RTL13) and channel is initialized (#RTL13) does nothing" file="./spec/acceptance/realtime/channel_spec.rb" time="1.285697"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol when it receives a server-initiated DETACHED (#RTL13) and channel is attaching will move to the SUSPENDED state and then attempt to ATTACH with the ATTACHING state (#RTL13b)" file="./spec/acceptance/realtime/channel_spec.rb" time="6.167056"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #detach when state is :failed fails the deferrable (#RTL5b)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.315089"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #detach when state is :attached calls the Deferrable callback on success" file="./spec/acceptance/realtime/channel_spec.rb" time="0.396975"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #detach when state is :attached detaches from a channel and calls the provided block (#RTL5d, #RTL5e)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.340108"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #detach when state is :attached emits :detaching then :detached events" file="./spec/acceptance/realtime/channel_spec.rb" time="0.349379"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #detach when state is :attached returns a SafeDeferrable that catches exceptions in callbacks and logs them" file="./spec/acceptance/realtime/channel_spec.rb" time="0.292409"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #detach when state is :attached it detaches from a channel (#RTL5d)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.330126"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #detach when state is :attached and DETACHED message is not received within realtime request timeout fails the deferrable and returns to the previous state (#RTL5f, #RTL5e)" file="./spec/acceptance/realtime/channel_spec.rb" time="2.317249"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #detach when state is :initialized returns a valid deferrable" file="./spec/acceptance/realtime/channel_spec.rb" time="0.153320"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #detach when state is :initialized does nothing as there is no channel to detach (#RTL5a)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.153419"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #detach when connection state is disconnected does the detach operation once the connection state is connected (#RTL5h)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.451910"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #detach when connection state is failed and channel is failed fails the deferrable (#RTL5b)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.316264"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #detach when connection state is failed and channel is detached fails the deferrable (#RTL5b)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.349186"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #detach when connection state is connecting does the detach operation once the connection state is connected (#RTL5h)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.354561"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #detach when connection state is closing fails the deferrable (#RTL5b)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.309528"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #detach when connection state is initialized does the detach operation once the connection state is connected (#RTL5h)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.354808"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #detach when state is :detached does nothing as the channel is detached (#RTL5a)" file="./spec/acceptance/realtime/channel_spec.rb" time="1.319425"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #detach when state is :suspended moves the channel state immediately to DETACHED state (#RTL5j)" file="./spec/acceptance/realtime/channel_spec.rb" time="1.308815"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #detach when state is :detaching ignores subsequent #detach calls but calls the callback if provided (#RTL5i)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.317080"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #detach when state is :attaching waits for the attach to complete and then moves to detached" file="./spec/acceptance/realtime/channel_spec.rb" time="0.317876"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #attach calls the SafeDeferrable callback on success (#RTL4d)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.317486"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #attach returns a SafeDeferrable that catches exceptions in callbacks and logs them" file="./spec/acceptance/realtime/channel_spec.rb" time="0.156263"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #attach with many connections and many channels on each simultaneously attaches all channels" file="./spec/acceptance/realtime/channel_spec.rb" time="5.978634"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #attach when initialized ignores subsequent #attach calls but calls the success callback if provided" file="./spec/acceptance/realtime/channel_spec.rb" time="0.307757"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #attach when initialized sends an ATTACH and waits for an ATTACHED (#RTL4c)" file="./spec/acceptance/realtime/channel_spec.rb" time="1.317239"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #attach when initialized implicitly attaches the channel (#RTL7c)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.306170"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #attach when initialized emits attaching then attached events" file="./spec/acceptance/realtime/channel_spec.rb" time="0.362350"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #attach when initialized attaches to a channel and calls the provided block (#RTL4d)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.303690"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #attach when initialized attaches to a channel" file="./spec/acceptance/realtime/channel_spec.rb" time="0.315331"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #attach when initialized sets attach_serial property after the attachment (#RTL15a)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.318278"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #attach when initialized context when channel options contain modes sends an ATTACH with options as flags (#RTL4l)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.258752"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #attach when initialized context when channel options contain modes when channel is reattaching sends ATTACH_RESUME flag along with other modes (RTL4j)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.479715"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #attach when initialized when the implicit channel attach fails registers the listener anyway (#RTL7c)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.487171"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #attach when initialized when received attached decodes flags and sets it as modes on channel options (#RTL4m)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.155288"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #attach when initialized when received attached set params as channel options params (#RTL4k1)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.156109"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #attach when initialized context when channel options contain params sends an ATTACH with params (#RTL4k)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.268601"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #attach when state is :attached does nothing (#RTL4a)" file="./spec/acceptance/realtime/channel_spec.rb" time="1.843780"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #attach when state is :failed reattaches and sets the errorReason to nil (#RTL4g)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.344843"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #attach when an ATTACHED acknowledge is not received on the current connection sends another ATTACH each time the connection becomes connected" file="./spec/acceptance/realtime/channel_spec.rb" time="1.563798"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #attach when state is :detaching does the attach operation after the completion of the pending request (#RTL4h)" file="./spec/acceptance/realtime/channel_spec.rb" time="1.364104"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #attach with connection state is disconnected (#RTL4i)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.434864"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #attach with connection state is connecting (#RTL4i)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.315866"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #attach with connection state is initialized (#RTL4i)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.313900"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #attach clean attach (RTL4j) when channel wasn&apos;t previously attached doesn&apos;t send ATTACH_RESUME" file="./spec/acceptance/realtime/channel_spec.rb" time="0.153814"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #attach clean attach (RTL4j) when channel was explicitly detached doesn&apos;t send ATTACH_RESUME" file="./spec/acceptance/realtime/channel_spec.rb" time="0.364637"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #attach failure as a result of insufficient key permissions calls the errback of the returned Deferrable (#RTL4d)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.341231"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #attach failure as a result of insufficient key permissions emits failed event (#RTL4e)" file="./spec/acceptance/realtime/channel_spec.rb" time="0.333281"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #attach failure as a result of insufficient key permissions updates the error_reason" file="./spec/acceptance/realtime/channel_spec.rb" time="0.338179"></testcase>
<testcase classname="spec.acceptance.realtime.channel_spec" name="Ably::Realtime::Channel using JSON protocol #attach failure as a result of insufficient key permissions and subsequent authorisation with suitable permissions attaches to the channel successfully and resets the channel error_reason" file="./spec/acceptance/realtime/channel_spec.rb" time="0.544755"></testcase>
<testcase classname="spec.acceptance.rest.time_spec" name="Ably::Rest::Client#time using JSON protocol fetching the service time should return the service time as a Time object" file="./spec/acceptance/rest/time_spec.rb" time="0.030322"></testcase>
<testcase classname="spec.acceptance.rest.time_spec" name="Ably::Rest::Client#time using JSON protocol fetching the service time with reconfigured HTTP timeout should raise a timeout exception" file="./spec/acceptance/rest/time_spec.rb" time="0.085565"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #status should return channel details status (#RSL8, #RSL8a)" file="./spec/acceptance/rest/channel_spec.rb" time="0.181201"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish with Messages and query params should fail to publish the message (RSL1l1)" file="./spec/acceptance/rest/channel_spec.rb" time="0.040372"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish null attributes when data is null publishes the message without a data attribute in the payload" file="./spec/acceptance/rest/channel_spec.rb" time="0.151471"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish null attributes with neither name or data attributes publishes the message without any attributes in the payload" file="./spec/acceptance/rest/channel_spec.rb" time="0.214575"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish null attributes when name is null publishes the message without a name attribute in the payload" file="./spec/acceptance/rest/channel_spec.rb" time="0.149059"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish identified clients when authenticated with TokenDetails with a valid client_id with a wildcard client_id in the message throws an exception" file="./spec/acceptance/rest/channel_spec.rb" time="0.036091"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish identified clients when authenticated with TokenDetails with a valid client_id with a valid client_id in the message succeeds" file="./spec/acceptance/rest/channel_spec.rb" time="0.158291"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish identified clients when authenticated with TokenDetails with a valid client_id with an invalid client_id in the message throws an exception" file="./spec/acceptance/rest/channel_spec.rb" time="0.038934"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish identified clients when authenticated with TokenDetails with a valid client_id with an empty client_id in the message succeeds and publishes with an implicit client_id" file="./spec/acceptance/rest/channel_spec.rb" time="0.145533"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish identified clients when authenticated with a Token string with an implicit client_id without having a confirmed identity with an invalid client_id in the message succeeds in the client library but then fails when published to Ably" file="./spec/acceptance/rest/channel_spec.rb" time="0.062340"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish identified clients when authenticated with a Token string with an implicit client_id without having a confirmed identity with a valid client_id in the message succeeds" file="./spec/acceptance/rest/channel_spec.rb" time="0.147531"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish identified clients when authenticated with a Token string with an implicit client_id without having a confirmed identity with an empty client_id in the message succeeds and publishes with an implicit client_id" file="./spec/acceptance/rest/channel_spec.rb" time="0.146250"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish identified clients when authenticated with a wildcard client_id with a valid client_id in the message succeeds" file="./spec/acceptance/rest/channel_spec.rb" time="0.148567"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish identified clients when authenticated with a wildcard client_id with a wildcard client_id in the message throws an exception" file="./spec/acceptance/rest/channel_spec.rb" time="0.033027"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish identified clients when authenticated with a wildcard client_id with an empty client_id in the message succeeds and publishes without a client_id" file="./spec/acceptance/rest/channel_spec.rb" time="0.146683"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish identified clients when anonymous and no client_id with a client_id in the message throws an exception" file="./spec/acceptance/rest/channel_spec.rb" time="0.032903"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish identified clients when anonymous and no client_id with an empty client_id in the message succeeds and publishes with an implicit client_id" file="./spec/acceptance/rest/channel_spec.rb" time="0.146171"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish identified clients when anonymous and no client_id with a wildcard client_id in the message throws an exception" file="./spec/acceptance/rest/channel_spec.rb" time="0.032449"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish message size is exceeded (#TO3l8) should raise Ably::Exceptions::MaxMessageSizeExceeded exception" file="./spec/acceptance/rest/channel_spec.rb" time="0.001476"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish with a Message object publishes the message" file="./spec/acceptance/rest/channel_spec.rb" time="0.117109"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish with an array of Message objects when max_message_size is 655 bytes and messages size (130 bytes) is smaller than the max_message_size publishes an array of messages in one HTTP request" file="./spec/acceptance/rest/channel_spec.rb" time="0.164081"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish with an array of Message objects when max_message_size is 655 bytes and messages size (177784 bytes) is bigger than the max_message_size should not publish and raise Ably::Exceptions::MaxMessageSizeExceeded" file="./spec/acceptance/rest/channel_spec.rb" time="2.770944"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish with an array of Message objects when max_message_size and max_frame_size is not set and messages size (130 bytes) is smaller than the max_message_size publishes an array of messages in one HTTP request" file="./spec/acceptance/rest/channel_spec.rb" time="0.164100"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish with an array of Message objects when max_message_size and max_frame_size is not set and messages size (177784 bytes) is bigger than the max_message_size should not publish and raise Ably::Exceptions::MaxMessageSizeExceeded" file="./spec/acceptance/rest/channel_spec.rb" time="2.748618"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish with name and data arguments publishes the message and return true indicating success" file="./spec/acceptance/rest/channel_spec.rb" time="0.150417"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish with name and data arguments and additional attributes publishes the message with the attributes and return true indicating success" file="./spec/acceptance/rest/channel_spec.rb" time="0.132413"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish with a frozen message event name succeeds and publishes with an implicit client_id" file="./spec/acceptance/rest/channel_spec.rb" time="0.140215"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish without adequate permissions on the channel raises a permission error when publishing" file="./spec/acceptance/rest/channel_spec.rb" time="0.063861"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish with an array of Hash objects with :name and :data attributes publishes an array of messages in one HTTP request" file="./spec/acceptance/rest/channel_spec.rb" time="0.161441"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish with a client_id configured in the ClientOptions publishes the message without a client_id" file="./spec/acceptance/rest/channel_spec.rb" time="0.001802"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish with a client_id configured in the ClientOptions expects a client_id to be added by the realtime service" file="./spec/acceptance/rest/channel_spec.rb" time="0.115751"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish with a non ASCII channel name stubbed correctly encodes the channel name" file="./spec/acceptance/rest/channel_spec.rb" time="0.024440"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish with a frozen payload succeeds and publishes with an implicit client_id" file="./spec/acceptance/rest/channel_spec.rb" time="0.117410"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #publish with a Message object and query params should fail to publish the message (RSL1l1)" file="./spec/acceptance/rest/channel_spec.rb" time="0.032879"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #presence returns a REST Presence object" file="./spec/acceptance/rest/channel_spec.rb" time="0.001022"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #history returns paged history using the PaginatedResult model" file="./spec/acceptance/rest/channel_spec.rb" time="0.333332"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #history returns a PaginatedResult model" file="./spec/acceptance/rest/channel_spec.rb" time="0.169935"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #history returns the current message history for the channel" file="./spec/acceptance/rest/channel_spec.rb" time="0.167847"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #history message IDs is unique" file="./spec/acceptance/rest/channel_spec.rb" time="0.178756"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #history message timestamps are after the messages were published" file="./spec/acceptance/rest/channel_spec.rb" time="0.175927"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #history direction returns paged history backwards by default" file="./spec/acceptance/rest/channel_spec.rb" time="0.173083"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #history direction returns history forward if specified in the options" file="./spec/acceptance/rest/channel_spec.rb" time="0.168320"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #history limit defaults to 100" file="./spec/acceptance/rest/channel_spec.rb" time="0.306548"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #history option when argument start is after end should raise an exception" file="./spec/acceptance/rest/channel_spec.rb" time="0.001064"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #history option :end with milliseconds since epoch value uses this value in the history request" file="./spec/acceptance/rest/channel_spec.rb" time="0.007088"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #history option :end with a Time object value converts the value to milliseconds since epoch in the hisotry request" file="./spec/acceptance/rest/channel_spec.rb" time="0.004662"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #history option :start with a Time object value converts the value to milliseconds since epoch in the hisotry request" file="./spec/acceptance/rest/channel_spec.rb" time="0.004304"></testcase>
<testcase classname="spec.acceptance.rest.channel_spec" name="Ably::Rest::Channel using JSON protocol #history option :start with milliseconds since epoch value uses this value in the history request" file="./spec/acceptance/rest/channel_spec.rb" time="0.004252"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #serial connection serial is set to 0 when a message is received back" file="./spec/acceptance/realtime/connection_spec.rb" time="0.317501"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #serial connection serial is set to -1 when a new connection is opened" file="./spec/acceptance/realtime/connection_spec.rb" time="0.280997"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #serial connection serial is set to 1 when the second message is received" file="./spec/acceptance/realtime/connection_spec.rb" time="0.368978"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #serial connection serial when a message is sent but the ACK has not yet been received the sent message msgSerial is 0 but the connection serial remains at -1" file="./spec/acceptance/realtime/connection_spec.rb" time="0.342545"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #details contains the new ConnectionDetails object once a subsequent connection is created (#RTN21)" file="./spec/acceptance/realtime/connection_spec.rb" time="0.424981"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #details contains the ConnectionDetails object once connected (#RTN21)" file="./spec/acceptance/realtime/connection_spec.rb" time="0.279293"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #details is nil before connected" file="./spec/acceptance/realtime/connection_spec.rb" time="0.153974"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #details with a different default connection_state_ttl updates the private Connection#connection_state_ttl when received from Ably in ConnectionDetails" file="./spec/acceptance/realtime/connection_spec.rb" time="0.272231"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol with many connections simultaneously opens each with a unique connection#id and connection#key" file="./spec/acceptance/realtime/connection_spec.rb" time="6.549797"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #connect with no fallbacks calls the provided block on success even if state changes to disconnected first" file="./spec/acceptance/realtime/connection_spec.rb" time="0.285009"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #connect with no fallbacks calls the Deferrable callback on success" file="./spec/acceptance/realtime/connection_spec.rb" time="0.261436"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #connect with no fallbacks returns a SafeDeferrable that catches exceptions in callbacks and logs them" file="./spec/acceptance/realtime/connection_spec.rb" time="0.153310"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #connect with no fallbacks when already connected does nothing and no further state changes are emitted" file="./spec/acceptance/realtime/connection_spec.rb" time="1.280597"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #connect with no fallbacks when explicitly reconnecting disconnected/suspended connection in retry (#RTN11c) when suspended reconnects immediately" file="./spec/acceptance/realtime/connection_spec.rb" time="0.337295"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #connect with no fallbacks when explicitly reconnecting disconnected/suspended connection in retry (#RTN11c) when disconnected reconnects immediately" file="./spec/acceptance/realtime/connection_spec.rb" time="2.799126"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #connect with no fallbacks once connected connection#id is unique for every connection" file="./spec/acceptance/realtime/connection_spec.rb" time="0.421145"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #connect with no fallbacks once connected connection#id is unique from the connection#key" file="./spec/acceptance/realtime/connection_spec.rb" time="0.274494"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #connect with no fallbacks once connected connection#id is a string" file="./spec/acceptance/realtime/connection_spec.rb" time="0.272025"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #connect with no fallbacks once connected connection#key is a string" file="./spec/acceptance/realtime/connection_spec.rb" time="0.259917"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #connect with no fallbacks once connected connection#key is unique from the connection#id" file="./spec/acceptance/realtime/connection_spec.rb" time="0.283032"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #connect with no fallbacks once connected connection#key is unique for every connection" file="./spec/acceptance/realtime/connection_spec.rb" time="0.430851"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #connect with no fallbacks connection#key is null before connecting" file="./spec/acceptance/realtime/connection_spec.rb" time="0.153005"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #connect with no fallbacks when reconnecting a failed connection transitions all channels state to initialized and cleares error_reason" file="./spec/acceptance/realtime/connection_spec.rb" time="0.405644"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #connect with no fallbacks when can&apos;t connect to host logs error on failed connection attempt" file="./spec/acceptance/realtime/connection_spec.rb" time="0.206314"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #connect with no fallbacks following a previous connection being opened and closed reconnects and is provided with a new connection ID and connection key from the server" file="./spec/acceptance/realtime/connection_spec.rb" time="0.409688"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #connect with no fallbacks when closing fails the deferrable before the connection is closed" file="./spec/acceptance/realtime/connection_spec.rb" time="0.279025"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #connect with no fallbacks with invalid auth details calls the Deferrable errback only once on connection failure" file="./spec/acceptance/realtime/connection_spec.rb" time="1.854771"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #connect with no fallbacks connection#id is null before connecting" file="./spec/acceptance/realtime/connection_spec.rb" time="0.153614"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #ping waits until the connection becomes CONNECTED when in the CONNETING state" file="./spec/acceptance/realtime/connection_spec.rb" time="0.298908"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #ping echoes a heart beat (#RTN13a)" file="./spec/acceptance/realtime/connection_spec.rb" time="0.311315"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #ping sends a unique ID in each protocol message (#RTN13e)" file="./spec/acceptance/realtime/connection_spec.rb" time="0.312929"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #ping with incompatible states when suspended fails the deferrable (#RTN13b)" file="./spec/acceptance/realtime/connection_spec.rb" time="0.270465"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #ping with incompatible states when closed fails the deferrable (#RTN13b)" file="./spec/acceptance/realtime/connection_spec.rb" time="0.307153"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #ping with incompatible states when not connected fails the deferrable (#RTN13b)" file="./spec/acceptance/realtime/connection_spec.rb" time="0.153538"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #ping with incompatible states when failed fails the deferrable (#RTN13b)" file="./spec/acceptance/realtime/connection_spec.rb" time="0.268887"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #ping with incompatible states when it becomes closed fails the deferrable (#RTN13b)" file="./spec/acceptance/realtime/connection_spec.rb" time="0.280125"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #ping when ping times out yields to the block with a nil value" file="./spec/acceptance/realtime/connection_spec.rb" time="0.261564"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #ping when ping times out fails the deferrable logs a warning (#RTN13a, #RTN13c)" file="./spec/acceptance/realtime/connection_spec.rb" time="0.383661"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #ping with a success block that raises an exception catches the exception and logs the error" file="./spec/acceptance/realtime/connection_spec.rb" time="0.299729"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol protocol failure receiving an invalid ProtocolMessage emits an error on the connection and logs a fatal error message" file="./spec/acceptance/realtime/connection_spec.rb" time="0.259312"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol when a state transition is unsupported logs the invalid state change as fatal" file="./spec/acceptance/realtime/connection_spec.rb" time="1.280901"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol intialization connects automatically" file="./spec/acceptance/realtime/connection_spec.rb" time="0.276169"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol intialization with token auth with opaque token string that contain an implicit client_id wildcard configures the Client#client_id and Auth#client_id with a wildcard once CONNECTED" file="./spec/acceptance/realtime/connection_spec.rb" time="0.310167"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol intialization with token auth with opaque token string that contain an implicit client_id string sets the Client#client_id and Auth#client_id once CONNECTED" file="./spec/acceptance/realtime/connection_spec.rb" time="0.320292"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol intialization with token auth with opaque token string that contain an implicit client_id string that is incompatible with the current client client_id fails the connection" file="./spec/acceptance/realtime/connection_spec.rb" time="0.312676"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol intialization with token auth for renewable tokens that are valid for the duration of the test with valid pre authorized token expiring in the future uses the existing token created by Auth" file="./spec/acceptance/realtime/connection_spec.rb" time="0.317490"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol intialization with token auth for renewable tokens that expire when connected with a valid non-expired token that then expires following the connection being opened and subsequent token is invalid transitions the connection to the failed state" file="./spec/acceptance/realtime/connection_spec.rb" time="2.325210"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol intialization with token auth for renewable tokens that expire when connected with a valid non-expired token that then expires following the connection being opened connection state retains messages published when disconnected three times during authentication" file="./spec/acceptance/realtime/connection_spec.rb" time="21.566955"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol intialization with token auth for renewable tokens that expire when connected with a valid non-expired token that then expires following the connection being opened the server disconnects the client, and the client automatically renews the token and then reconnects" file="./spec/acceptance/realtime/connection_spec.rb" time="5.351736"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol intialization with token auth for renewable tokens that expire opening a new connection with almost expired tokens renews token every time after it expires" file="./spec/acceptance/realtime/connection_spec.rb" time="6.224817"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol intialization with token auth for renewable tokens that expire opening a new connection with immediately expired token and no fallback hosts renews the token on connect, and makes one immediate subsequent attempt to obtain a new token (#RSA4b)" file="./spec/acceptance/realtime/connection_spec.rb" time="0.498114"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol intialization with token auth for renewable tokens that expire opening a new connection with immediately expired token and no fallback hosts using implicit token auth uses the primary host for subsequent connection and auth requests" file="./spec/acceptance/realtime/connection_spec.rb" time="0.644024"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol intialization with token auth for renewable tokens that expire opening a new connection with immediately expired token and no fallback hosts when disconnected_retry_timeout is 0.5 seconds renews the token on connect, and continues to attempt renew based on the retry schedule" file="./spec/acceptance/realtime/connection_spec.rb" time="1.973234"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol intialization with token auth for non-renewable tokens that are expired when connected transitions state to failed (#RSA4a)" file="./spec/acceptance/realtime/connection_spec.rb" time="4.316251"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol intialization with token auth for non-renewable tokens that are expired opening a new connection transitions state to failed (#RSA4a)" file="./spec/acceptance/realtime/connection_spec.rb" time="1.454133"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol intialization current_host is available immediately after the client is instanced" file="./spec/acceptance/realtime/connection_spec.rb" time="0.154704"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol intialization with :auto_connect option set to false connects when method #connect is called" file="./spec/acceptance/realtime/connection_spec.rb" time="0.269217"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol intialization with :auto_connect option set to false does not connect automatically" file="./spec/acceptance/realtime/connection_spec.rb" time="1.154636"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol Heartbeats (#RTN23) heartbeat interval when reduced artificially disconnects the transport if no heartbeat received since connected (#RTN23a)" file="./spec/acceptance/realtime/connection_spec.rb" time="5.374975"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol Heartbeats (#RTN23) heartbeat interval when reduced artificially is the sum of the max_idle_interval and realtime_request_timeout (#RTN23a)" file="./spec/acceptance/realtime/connection_spec.rb" time="0.280961"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol Heartbeats (#RTN23) heartbeat interval when reduced artificially disconnects the transport if no heartbeat received since last event received (#RTN23a)" file="./spec/acceptance/realtime/connection_spec.rb" time="8.489427"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol Heartbeats (#RTN23) transport-level heartbeats are supported in the websocket transport provides the heartbeats argument in the websocket connection params (#RTN23b)" file="./spec/acceptance/realtime/connection_spec.rb" time="0.155294"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol Heartbeats (#RTN23) transport-level heartbeats are supported in the websocket transport receives websocket heartbeat messages (#RTN23b) [slow test as need to wait for heartbeat]" file="./spec/acceptance/realtime/connection_spec.rb" time="15.265600"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol Heartbeats (#RTN23) with websocket heartbeats disabled (undocumented) does not provide the heartbeats argument in the websocket connection params (#RTN23b)" file="./spec/acceptance/realtime/connection_spec.rb" time="0.155298"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol Heartbeats (#RTN23) with websocket heartbeats disabled (undocumented) receives websocket protocol messages (#RTN23b) [slow test as need to wait for heartbeat]" file="./spec/acceptance/realtime/connection_spec.rb" time="15.281543"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol initialization state changes with implicit #connect are emitted in order" file="./spec/acceptance/realtime/connection_spec.rb" time="0.274617"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol initialization state changes with explicit #connect are emitted in order" file="./spec/acceptance/realtime/connection_spec.rb" time="0.270126"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #close calls the Deferrable callback on success" file="./spec/acceptance/realtime/connection_spec.rb" time="0.296978"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #close returns a SafeDeferrable that catches exceptions in callbacks and logs them" file="./spec/acceptance/realtime/connection_spec.rb" time="0.270008"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #close when connection state is :suspended RTN12d immediatly closes connection" file="./spec/acceptance/realtime/connection_spec.rb" time="0.023275"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #close when connection state is :initialized changes the connection state to :closing and then immediately :closed without sending a ProtocolMessage CLOSE" file="./spec/acceptance/realtime/connection_spec.rb" time="1.155549"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #close when connection state is :disconnected RTN12d immediatly closes connection" file="./spec/acceptance/realtime/connection_spec.rb" time="2.062679"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #close when connection state is :connected changes the connection state to :closing and waits for the server to confirm connection is :closed with a ProtocolMessage" file="./spec/acceptance/realtime/connection_spec.rb" time="1.314218"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #close when connection state is :connected with an unresponsive connection force closes the connection when a :closed ProtocolMessage response is not received" file="./spec/acceptance/realtime/connection_spec.rb" time="2.261537"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #close when connection state is :connecting RTN12f :connected arrive when trying to close moves to connected and then to closed" file="./spec/acceptance/realtime/connection_spec.rb" time="0.309965"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #close when connection state is :connecting RTN12f :connected does not arrive when trying to close moves to closed" file="./spec/acceptance/realtime/connection_spec.rb" time="10.165272"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #close when already closed does nothing and no further state changes are emitted" file="./spec/acceptance/realtime/connection_spec.rb" time="1.300663"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol transport_params (#RTC1f) pases transport_params to query" file="./spec/acceptance/realtime/connection_spec.rb" time="0.155610"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol transport_params (#RTC1f) when changing default param overrides default param (#RTC1f1)" file="./spec/acceptance/realtime/connection_spec.rb" time="0.155608"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol #msgSerial when messages are queued for publish before a connection is established the msgSerial is always incrementing (and not reset when the new connection is established) ensuring messages are never de-duped by the realtime service" file="./spec/acceptance/realtime/connection_spec.rb" time="1.367643"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol state change side effects when connection enters the :failed state sets all channels to failed and prevents publishing of messages on those channels" file="./spec/acceptance/realtime/connection_spec.rb" time="0.577698"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol state change side effects when connection enters the :suspended state moves the channels into the suspended state and prevents publishing of messages on those channels" file="./spec/acceptance/realtime/connection_spec.rb" time="0.385607"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol state change side effects when connection enters the :disconnected state queues messages to be sent and all channels remain attached" file="./spec/acceptance/realtime/connection_spec.rb" time="0.521789"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol undocumented method #internet_up? returns a Deferrable" file="./spec/acceptance/realtime/connection_spec.rb" time="0.155119"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol undocumented method #internet_up? when the Internet is down calls the failure callback of the Deferrable" file="./spec/acceptance/realtime/connection_spec.rb" time="0.185792"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol undocumented method #internet_up? when the Internet is down calls the block with false" file="./spec/acceptance/realtime/connection_spec.rb" time="0.169796"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol undocumented method #internet_up? when the Internet is up calls the success callback of the Deferrable" file="./spec/acceptance/realtime/connection_spec.rb" time="0.377582"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol undocumented method #internet_up? when the Internet is up calls the block with true" file="./spec/acceptance/realtime/connection_spec.rb" time="0.370702"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol undocumented method #internet_up? when the Internet is up with a TLS connection checks the Internet up URL over TLS" file="./spec/acceptance/realtime/connection_spec.rb" time="0.154856"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol undocumented method #internet_up? when the Internet is up with a non-TLS connection checks the Internet up URL over TLS" file="./spec/acceptance/realtime/connection_spec.rb" time="0.155395"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol undocumented method #internet_up? internet up URL protocol when using TLS for the connection uses TLS for the Internet check to https://internet-up.ably-realtime.com/is-the-internet-up.txt" file="./spec/acceptance/realtime/connection_spec.rb" time="0.153922"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol undocumented method #internet_up? internet up URL protocol when using a non-secured connection uses TLS for the Internet check to http://internet-up.ably-realtime.com/is-the-internet-up.txt" file="./spec/acceptance/realtime/connection_spec.rb" time="0.153855"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol version params sends the lib version param agent (#RCS7d)" file="./spec/acceptance/realtime/connection_spec.rb" time="0.155526"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol version params sends the protocol version param v (#G4, #RTN2f)" file="./spec/acceptance/realtime/connection_spec.rb" time="0.155479"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol connection state change emits event to all and single subscribers" file="./spec/acceptance/realtime/connection_spec.rb" time="0.634095"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol connection state change emits a ConnectionStateChange object" file="./spec/acceptance/realtime/connection_spec.rb" time="0.277012"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol connection state change whilst CONNECTED when a CONNECTED message with an error is received emits an UPDATE event" file="./spec/acceptance/realtime/connection_spec.rb" time="0.259478"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol connection state change whilst CONNECTED when a CONNECTED message is received (#RTN24) updates the ConnectionDetail and Connection attributes (#RTC8a1)" file="./spec/acceptance/realtime/connection_spec.rb" time="0.281318"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol connection state change whilst CONNECTED when a CONNECTED message is received (#RTN24) emits an UPDATE event" file="./spec/acceptance/realtime/connection_spec.rb" time="0.270077"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol connection state change ConnectionStateChange object has current state" file="./spec/acceptance/realtime/connection_spec.rb" time="0.278341"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol connection state change ConnectionStateChange object has a previous state" file="./spec/acceptance/realtime/connection_spec.rb" time="0.259276"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol connection state change ConnectionStateChange object contains a private API protocol_message attribute that is used for special state change events" file="./spec/acceptance/realtime/connection_spec.rb" time="0.279388"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol connection state change ConnectionStateChange object has an empty reason when there is no error" file="./spec/acceptance/realtime/connection_spec.rb" time="0.297960"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol connection state change ConnectionStateChange object has the event that generated the state change (#TH5)" file="./spec/acceptance/realtime/connection_spec.rb" time="0.263462"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol connection state change ConnectionStateChange object on failure has a reason Error object when there is an error on the connection" file="./spec/acceptance/realtime/connection_spec.rb" time="0.260406"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol connection state change ConnectionStateChange object retry_in is nil when a retry is not required" file="./spec/acceptance/realtime/connection_spec.rb" time="0.284431"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol connection state change ConnectionStateChange object retry_in is 0 when an immediate reconnect will occur" file="./spec/acceptance/realtime/connection_spec.rb" time="0.270352"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol connection state change ConnectionStateChange object retry_in is 0 when first attempt to connect fails" file="./spec/acceptance/realtime/connection_spec.rb" time="0.171431"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol connection state change ConnectionStateChange object retry_in contains the next retry period when an immediate reconnect will not occur" file="./spec/acceptance/realtime/connection_spec.rb" time="0.287461"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol recovery with :recover option with expired (missing) value sent to server connects but sets the error reason and includes the reason in the state change" file="./spec/acceptance/realtime/connection_spec.rb" time="0.271755"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol recovery with :recover option with invalid syntax raises an exception" file="./spec/acceptance/realtime/connection_spec.rb" time="0.001749"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol recovery opening a new connection using a recently disconnected connection&apos;s #recovery_key when messages have been published the new connection uses the correct msgSerial from the old connection" file="./spec/acceptance/realtime/connection_spec.rb" time="0.640479"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol recovery opening a new connection using a recently disconnected connection&apos;s #recovery_key when messages have been sent whilst the old connection is disconnected the new connection recovers server-side queued messages" file="./spec/acceptance/realtime/connection_spec.rb" time="0.929352"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol recovery opening a new connection using a recently disconnected connection&apos;s #recovery_key connection#id after recovery remains the same" file="./spec/acceptance/realtime/connection_spec.rb" time="0.545073"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol recovery opening a new connection using a recently disconnected connection&apos;s #recovery_key connection#id after recovery does not call a resume callback" file="./spec/acceptance/realtime/connection_spec.rb" time="1.040934"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol recovery opening a new connection using a recently disconnected connection&apos;s #recovery_key when messages are published before the new connection is recovered the new connection uses the correct msgSerial from the old connection for the queued messages" file="./spec/acceptance/realtime/connection_spec.rb" time="2.664442"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol recovery #recovery_key is available when connection is in one of the states: connecting, connected, disconnected" file="./spec/acceptance/realtime/connection_spec.rb" time="0.588372"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol recovery #recovery_key is nil when connection is explicitly CLOSED" file="./spec/acceptance/realtime/connection_spec.rb" time="0.302490"></testcase>
<testcase classname="spec.acceptance.realtime.connection_spec" name="Ably::Realtime::Connection using JSON protocol recovery #recovery_key is composed of connection key and serial that is kept up to date with each message ACK received" file="./spec/acceptance/realtime/connection_spec.rb" time="0.376494"></testcase>
<testcase classname="spec.acceptance.realtime.channel_history_spec" name="Ably::Realtime::Channel#history using JSON protocol returns a SafeDeferrable that catches exceptions in callbacks and logs them" file="./spec/acceptance/realtime/channel_history_spec.rb" time="0.376593"></testcase>
<testcase classname="spec.acceptance.realtime.channel_history_spec" name="Ably::Realtime::Channel#history using JSON protocol with option until_attach: true retrieves all messages before channel was attached" file="./spec/acceptance/realtime/channel_history_spec.rb" time="0.458678"></testcase>
<testcase classname="spec.acceptance.realtime.channel_history_spec" name="Ably::Realtime::Channel#history using JSON protocol with option until_attach: true fails the deferrable unless the state is attached" file="./spec/acceptance/realtime/channel_history_spec.rb" time="0.155408"></testcase>
<testcase classname="spec.acceptance.realtime.channel_history_spec" name="Ably::Realtime::Channel#history using JSON protocol with option until_attach: true and two pages of messages retrieves two pages of messages before channel was attached" file="./spec/acceptance/realtime/channel_history_spec.rb" time="1.646246"></testcase>
<testcase classname="spec.acceptance.realtime.channel_history_spec" name="Ably::Realtime::Channel#history using JSON protocol with option until_attach: true when channel receives update event after an attachment updates attach_serial" file="./spec/acceptance/realtime/channel_history_spec.rb" time="0.000017"><skipped/></testcase>
<testcase classname="spec.acceptance.realtime.channel_history_spec" name="Ably::Realtime::Channel#history using JSON protocol with two clients publishing messages on the same channel retrieves realtime history on both channels" file="./spec/acceptance/realtime/channel_history_spec.rb" time="0.721519"></testcase>
<testcase classname="spec.acceptance.realtime.channel_history_spec" name="Ably::Realtime::Channel#history using JSON protocol with lots of messages published with a single client and channel in multiple ProtocolMessages retrieves limited history forwards with pagination" file="./spec/acceptance/realtime/channel_history_spec.rb" time="3.718122"></testcase>
<testcase classname="spec.acceptance.realtime.channel_history_spec" name="Ably::Realtime::Channel#history using JSON protocol with lots of messages published with a single client and channel in multiple ProtocolMessages retrieves limited history backwards with pagination" file="./spec/acceptance/realtime/channel_history_spec.rb" time="3.825652"></testcase>
<testcase classname="spec.acceptance.realtime.channel_history_spec" name="Ably::Realtime::Channel#history using JSON protocol with lots of messages published with a single client and channel and REST history return the same results with unique matching message IDs" file="./spec/acceptance/realtime/channel_history_spec.rb" time="1.075977"></testcase>
<testcase classname="spec.acceptance.realtime.channel_history_spec" name="Ably::Realtime::Channel#history using JSON protocol with lots of messages published with a single client and channel as one ProtocolMessage retrieves history forwards with pagination through :limit option" file="./spec/acceptance/realtime/channel_history_spec.rb" time="0.931489"></testcase>
<testcase classname="spec.acceptance.realtime.channel_history_spec" name="Ably::Realtime::Channel#history using JSON protocol with lots of messages published with a single client and channel as one ProtocolMessage retrieves history backwards with pagination through :limit option" file="./spec/acceptance/realtime/channel_history_spec.rb" time="0.945118"></testcase>
<testcase classname="spec.acceptance.realtime.channel_history_spec" name="Ably::Realtime::Channel#history using JSON protocol with a single client publishing and receiving retrieves realtime history" file="./spec/acceptance/realtime/channel_history_spec.rb" time="0.398770"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #channel_subscriptions (#RSH1c) #save (#RSH1c3) fails if data is invalid" file="./spec/acceptance/rest/push_admin_spec.rb" time="1.118541"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #channel_subscriptions (#RSH1c) #save (#RSH1c3) saves the new device_id PushChannelSubscription Hash object" file="./spec/acceptance/rest/push_admin_spec.rb" time="2.080526"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #channel_subscriptions (#RSH1c) #save (#RSH1c3) allows arbitrary number of subsequent saves" file="./spec/acceptance/rest/push_admin_spec.rb" time="1.692498"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #channel_subscriptions (#RSH1c) #save (#RSH1c3) saves the new client_id PushChannelSubscription Hash object" file="./spec/acceptance/rest/push_admin_spec.rb" time="1.154757"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #channel_subscriptions (#RSH1c) #save (#RSH1c3) saves the client_id PushChannelSubscription object" file="./spec/acceptance/rest/push_admin_spec.rb" time="1.196369"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #channel_subscriptions (#RSH1c) #save (#RSH1c3) saves the device_id PushChannelSubscription object" file="./spec/acceptance/rest/push_admin_spec.rb" time="1.112963"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #channel_subscriptions (#RSH1c) #remove_where (#RSH1c5) device_id and client_id filters in the same request are not suppoorted" file="./spec/acceptance/rest/push_admin_spec.rb" time="1.520797"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #channel_subscriptions (#RSH1c) #remove_where (#RSH1c5) removes matching client_ids" file="./spec/acceptance/rest/push_admin_spec.rb" time="1.483572"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #channel_subscriptions (#RSH1c) #remove_where (#RSH1c5) removes matching channels" file="./spec/acceptance/rest/push_admin_spec.rb" time="1.406406"><skipped/></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #channel_subscriptions (#RSH1c) #remove_where (#RSH1c5) succeeds on no match" file="./spec/acceptance/rest/push_admin_spec.rb" time="1.497994"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #channel_subscriptions (#RSH1c) #remove_where (#RSH1c5) removes matching device_ids" file="./spec/acceptance/rest/push_admin_spec.rb" time="1.333914"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #channel_subscriptions (#RSH1c) #list_channels (#RSH1c2) returns an accurate number of channels after devices are deleted" file="./spec/acceptance/rest/push_admin_spec.rb" time="1.642676"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #channel_subscriptions (#RSH1c) #list_channels (#RSH1c2) supports paging" file="./spec/acceptance/rest/push_admin_spec.rb" time="1.171255"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #channel_subscriptions (#RSH1c) #list_channels (#RSH1c2) returns a PaginatedResult object containing String objects" file="./spec/acceptance/rest/push_admin_spec.rb" time="1.347919"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #channel_subscriptions (#RSH1c) #remove (#RSH1c4) removes match for PushChannelSubscription object by channel and client_id" file="./spec/acceptance/rest/push_admin_spec.rb" time="1.586996"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #channel_subscriptions (#RSH1c) #remove (#RSH1c4) removes match for Hash object by channel and client_id" file="./spec/acceptance/rest/push_admin_spec.rb" time="1.342134"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #channel_subscriptions (#RSH1c) #remove (#RSH1c4) removes match for Hash object by channel and device_id" file="./spec/acceptance/rest/push_admin_spec.rb" time="1.364747"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #channel_subscriptions (#RSH1c) #remove (#RSH1c4) removes match for PushChannelSubscription object by channel and client_id" file="./spec/acceptance/rest/push_admin_spec.rb" time="1.310506"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #channel_subscriptions (#RSH1c) #remove (#RSH1c4) succeeds even if there is no match" file="./spec/acceptance/rest/push_admin_spec.rb" time="1.201577"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #channel_subscriptions (#RSH1c) #list (#RSH1c1) provides filtering" file="./spec/acceptance/rest/push_admin_spec.rb" time="1.800990"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #channel_subscriptions (#RSH1c) #list (#RSH1c1) raises an exception if none of the required filters are provided" file="./spec/acceptance/rest/push_admin_spec.rb" time="1.320478"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #channel_subscriptions (#RSH1c) #list (#RSH1c1) returns a PaginatedResult object containing DeviceDetails objects" file="./spec/acceptance/rest/push_admin_spec.rb" time="1.261995"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #channel_subscriptions (#RSH1c) #list (#RSH1c1) supports paging" file="./spec/acceptance/rest/push_admin_spec.rb" time="1.574527"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #channel_subscriptions (#RSH1c) #list (#RSH1c1) returns an empty PaginatedResult if params do not match" file="./spec/acceptance/rest/push_admin_spec.rb" time="1.281118"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #publish accepts valid push data and recipient (#RSH1a)" file="./spec/acceptance/rest/push_admin_spec.rb" time="0.107941"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #publish recipient variable case is converted to snakeCase" file="./spec/acceptance/rest/push_admin_spec.rb" time="0.004614"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #publish invalid push data (#RSH1a) raises an error after receiving a 40x realtime response" file="./spec/acceptance/rest/push_admin_spec.rb" time="0.033508"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #publish using test environment channel recipient (#RSH1a) triggers a push notification" file="./spec/acceptance/rest/push_admin_spec.rb" time="5.081287"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #publish invalid recipient (#RSH1a) raises an error after receiving a 40x realtime response" file="./spec/acceptance/rest/push_admin_spec.rb" time="0.035409"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #publish without publish permissions raises a permissions issue exception" file="./spec/acceptance/rest/push_admin_spec.rb" time="0.067670"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #publish invalid arguments (#RHS1a) raises an exception with a nil recipient" file="./spec/acceptance/rest/push_admin_spec.rb" time="0.001058"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #publish invalid arguments (#RHS1a) raises an exception with a empty recipient" file="./spec/acceptance/rest/push_admin_spec.rb" time="0.000673"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #publish invalid arguments (#RHS1a) raises an exception with a nil recipient" file="./spec/acceptance/rest/push_admin_spec.rb" time="0.000807"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #publish invalid arguments (#RHS1a) raises an exception with a empty recipient" file="./spec/acceptance/rest/push_admin_spec.rb" time="0.000855"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #device_registrations (#RSH1b) #remove_where (#RSH1b5) removes device by device_id" file="./spec/acceptance/rest/push_admin_spec.rb" time="1.407454"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #device_registrations (#RSH1b) #remove_where (#RSH1b5) removes all matching device registrations by client_id" file="./spec/acceptance/rest/push_admin_spec.rb" time="0.886599"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #device_registrations (#RSH1b) #remove_where (#RSH1b5) succeeds even if there is no match" file="./spec/acceptance/rest/push_admin_spec.rb" time="0.939959"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #device_registrations (#RSH1b) #remove (#RSH1b4) succeeds if the item does not exist" file="./spec/acceptance/rest/push_admin_spec.rb" time="0.751492"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #device_registrations (#RSH1b) #remove (#RSH1b4) removes the provided device id string" file="./spec/acceptance/rest/push_admin_spec.rb" time="1.095150"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #device_registrations (#RSH1b) #remove (#RSH1b4) removes the provided DeviceDetails" file="./spec/acceptance/rest/push_admin_spec.rb" time="1.050018"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #device_registrations (#RSH1b) #list (#RSH1b2) returns a PaginatedResult object containing DeviceDetails objects" file="./spec/acceptance/rest/push_admin_spec.rb" time="0.864650"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #device_registrations (#RSH1b) #list (#RSH1b2) supports paging" file="./spec/acceptance/rest/push_admin_spec.rb" time="0.902449"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #device_registrations (#RSH1b) #list (#RSH1b2) returns an empty PaginatedResult if not params match" file="./spec/acceptance/rest/push_admin_spec.rb" time="0.648467"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #device_registrations (#RSH1b) #list (#RSH1b2) provides filtering" file="./spec/acceptance/rest/push_admin_spec.rb" time="0.913463"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #device_registrations (#RSH1b) #get (#RSH1b1) returns a DeviceDetails object if a DeviceDetails object is provided" file="./spec/acceptance/rest/push_admin_spec.rb" time="0.692907"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #device_registrations (#RSH1b) #get (#RSH1b1) raises a ResourceMissing exception if device ID does not exist" file="./spec/acceptance/rest/push_admin_spec.rb" time="0.852300"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #device_registrations (#RSH1b) #get (#RSH1b1) returns a DeviceDetails object if a device ID string is provided" file="./spec/acceptance/rest/push_admin_spec.rb" time="0.778577"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #device_registrations (#RSH1b) without permissions raises a permissions not authorized exception" file="./spec/acceptance/rest/push_admin_spec.rb" time="0.250935"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #device_registrations (#RSH1b) #save (#RSH1b3) saves the new DeviceDetails object" file="./spec/acceptance/rest/push_admin_spec.rb" time="0.757318"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #device_registrations (#RSH1b) #save (#RSH1b3) allows device_secret to be configured" file="./spec/acceptance/rest/push_admin_spec.rb" time="0.663092"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #device_registrations (#RSH1b) #save (#RSH1b3) fails if data is invalid" file="./spec/acceptance/rest/push_admin_spec.rb" time="0.094985"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #device_registrations (#RSH1b) #save (#RSH1b3) does not allow some fields to be configured" file="./spec/acceptance/rest/push_admin_spec.rb" time="0.720136"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #device_registrations (#RSH1b) #save (#RSH1b3) allows arbitrary number of subsequent saves" file="./spec/acceptance/rest/push_admin_spec.rb" time="1.769325"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #device_registrations (#RSH1b) #save (#RSH1b3) saves the associated DevicePushDetails" file="./spec/acceptance/rest/push_admin_spec.rb" time="0.762315"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #device_registrations (#RSH1b) #save (#RSH1b3) saves the new DeviceDetails Hash object" file="./spec/acceptance/rest/push_admin_spec.rb" time="0.685188"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #device_registrations (#RSH1b) #save (#RSH1b3) with web target saves the associated DevicePushDetails" file="./spec/acceptance/rest/push_admin_spec.rb" time="0.708716"></testcase>
<testcase classname="spec.acceptance.rest.push_admin_spec" name="Ably::Rest::Push::Admin using JSON protocol #device_registrations (#RSH1b) #save (#RSH1b3) with GCM target saves the associated DevicePushDetails" file="./spec/acceptance/rest/push_admin_spec.rb" time="0.801099"></testcase>
<testcase classname="spec.acceptance.realtime.channels_spec" name="Ably::Realtime::Channels using JSON protocol using undocumented array accessor [] method on client#channels behaves like a channel returns a channel object" file="./spec/acceptance/realtime/channels_spec.rb" time="0.153535"></testcase>
<testcase classname="spec.acceptance.realtime.channels_spec" name="Ably::Realtime::Channels using JSON protocol using undocumented array accessor [] method on client#channels behaves like a channel returns channel object and passes the provided options" file="./spec/acceptance/realtime/channels_spec.rb" time="0.153624"></testcase>
<testcase classname="spec.acceptance.realtime.channels_spec" name="Ably::Realtime::Channels using JSON protocol when channel supposed to trigger reattachment per RTL16a (#RTS3c1) will raise an error" file="./spec/acceptance/realtime/channels_spec.rb" time="0.318467"></testcase>
<testcase classname="spec.acceptance.realtime.channels_spec" name="Ably::Realtime::Channels using JSON protocol when channel supposed to trigger reattachment per RTL16a (#RTS3c1) params keys are the same but values are different will raise an error" file="./spec/acceptance/realtime/channels_spec.rb" time="0.313673"></testcase>
<testcase classname="spec.acceptance.realtime.channels_spec" name="Ably::Realtime::Channels using JSON protocol using shortcut method #channel on the client object behaves like a channel returns a channel object" file="./spec/acceptance/realtime/channels_spec.rb" time="0.153920"></testcase>
<testcase classname="spec.acceptance.realtime.channels_spec" name="Ably::Realtime::Channels using JSON protocol using shortcut method #channel on the client object behaves like a channel returns channel object and passes the provided options" file="./spec/acceptance/realtime/channels_spec.rb" time="0.153647"></testcase>
<testcase classname="spec.acceptance.realtime.channels_spec" name="Ably::Realtime::Channels using JSON protocol using #get method on client#channels behaves like a channel returns channel object and passes the provided options" file="./spec/acceptance/realtime/channels_spec.rb" time="0.153657"></testcase>
<testcase classname="spec.acceptance.realtime.channels_spec" name="Ably::Realtime::Channels using JSON protocol using #get method on client#channels behaves like a channel returns a channel object" file="./spec/acceptance/realtime/channels_spec.rb" time="0.154093"></testcase>
<testcase classname="spec.acceptance.realtime.channels_spec" name="Ably::Realtime::Channels using JSON protocol accessing an existing channel object without specifying any channel options returns the existing channel without modifying the channel options" file="./spec/acceptance/realtime/channels_spec.rb" time="0.153726"></testcase>
<testcase classname="spec.acceptance.realtime.channels_spec" name="Ably::Realtime::Channels using JSON protocol accessing an existing channel object with different options shows deprecation warning" file="./spec/acceptance/realtime/channels_spec.rb" time="0.154099"></testcase>
<testcase classname="spec.acceptance.realtime.channels_spec" name="Ably::Realtime::Channels using JSON protocol accessing an existing channel object with different options overrides the existing channel options and returns the channel object" file="./spec/acceptance/realtime/channels_spec.rb" time="0.154358"></testcase>
<testcase classname="spec.acceptance.realtime.time_spec" name="Ably::Realtime::Client#time using JSON protocol fetching the service time returns a SafeDeferrable that catches exceptions in callbacks and logs them" file="./spec/acceptance/realtime/time_spec.rb" time="0.154888"></testcase>
<testcase classname="spec.acceptance.realtime.time_spec" name="Ably::Realtime::Client#time using JSON protocol fetching the service time should return the service time as a Time object" file="./spec/acceptance/realtime/time_spec.rb" time="0.192275"></testcase>
<testcase classname="spec.acceptance.realtime.time_spec" name="Ably::Realtime::Client#time using JSON protocol fetching the service time with reconfigured HTTP timeout should raise a timeout exception" file="./spec/acceptance/realtime/time_spec.rb" time="0.222099"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message message encoding interoperability over a JSON transport when encoding binary ensures that client libraries have compatible encoding and decoding using common fixtures" file="./spec/acceptance/realtime/message_spec.rb" time="0.403897"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message message encoding interoperability over a JSON transport when decoding jsonArray ensures that client libraries have compatible encoding and decoding using common fixtures" file="./spec/acceptance/realtime/message_spec.rb" time="0.339958"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message message encoding interoperability over a JSON transport when encoding string ensures that client libraries have compatible encoding and decoding using common fixtures" file="./spec/acceptance/realtime/message_spec.rb" time="0.416149"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message message encoding interoperability over a JSON transport when encoding string ensures that client libraries have compatible encoding and decoding using common fixtures" file="./spec/acceptance/realtime/message_spec.rb" time="0.394990"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message message encoding interoperability over a JSON transport when decoding string ensures that client libraries have compatible encoding and decoding using common fixtures" file="./spec/acceptance/realtime/message_spec.rb" time="0.340601"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message message encoding interoperability over a JSON transport when encoding jsonArray ensures that client libraries have compatible encoding and decoding using common fixtures" file="./spec/acceptance/realtime/message_spec.rb" time="0.393726"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message message encoding interoperability over a JSON transport when decoding jsonObject ensures that client libraries have compatible encoding and decoding using common fixtures" file="./spec/acceptance/realtime/message_spec.rb" time="0.359460"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message message encoding interoperability over a JSON transport when decoding string ensures that client libraries have compatible encoding and decoding using common fixtures" file="./spec/acceptance/realtime/message_spec.rb" time="0.394976"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message message encoding interoperability over a JSON transport when decoding binary ensures that client libraries have compatible encoding and decoding using common fixtures" file="./spec/acceptance/realtime/message_spec.rb" time="0.437134"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message message encoding interoperability over a JSON transport when encoding jsonObject ensures that client libraries have compatible encoding and decoding using common fixtures" file="./spec/acceptance/realtime/message_spec.rb" time="0.371713"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message message encoding interoperability over a MsgPack transport when retrieving a string using JSON protocol is compatible with a publishes using MsgPack" file="./spec/acceptance/realtime/message_spec.rb" time="0.114978"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message message encoding interoperability over a MsgPack transport when retrieving a binary using JSON protocol is compatible with a publishes using MsgPack" file="./spec/acceptance/realtime/message_spec.rb" time="0.117909"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message message encoding interoperability over a MsgPack transport when retrieving a string using JSON protocol is compatible with a publishes using MsgPack" file="./spec/acceptance/realtime/message_spec.rb" time="0.114854"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message message encoding interoperability over a MsgPack transport when publishing a binary using JSON protocol receives the message over MsgPack and the data matches" file="./spec/acceptance/realtime/message_spec.rb" time="0.207439"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message message encoding interoperability over a MsgPack transport when retrieving a jsonObject using JSON protocol is compatible with a publishes using MsgPack" file="./spec/acceptance/realtime/message_spec.rb" time="0.117772"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message message encoding interoperability over a MsgPack transport when retrieving a jsonArray using JSON protocol is compatible with a publishes using MsgPack" file="./spec/acceptance/realtime/message_spec.rb" time="0.116701"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message message encoding interoperability over a MsgPack transport when publishing a jsonObject using JSON protocol receives the message over MsgPack and the data matches" file="./spec/acceptance/realtime/message_spec.rb" time="0.180652"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message message encoding interoperability over a MsgPack transport when publishing a jsonArray using JSON protocol receives the message over MsgPack and the data matches" file="./spec/acceptance/realtime/message_spec.rb" time="0.193358"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message message encoding interoperability over a MsgPack transport when publishing a string using JSON protocol receives the message over MsgPack and the data matches" file="./spec/acceptance/realtime/message_spec.rb" time="0.178767"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message message encoding interoperability over a MsgPack transport when publishing a string using JSON protocol receives the message over MsgPack and the data matches" file="./spec/acceptance/realtime/message_spec.rb" time="0.188101"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol sends a String data payload" file="./spec/acceptance/realtime/message_spec.rb" time="0.343623"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol without suitable publishing permissions calls the error callback" file="./spec/acceptance/realtime/message_spec.rb" time="0.353110"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with multiple sends from one client to another encrypts and decrypts all messages" file="./spec/acceptance/realtime/message_spec.rb" time="0.741394"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with multiple sends from one client to another receives raw messages with the correct encoding" file="./spec/acceptance/realtime/message_spec.rb" time="0.617453"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-128-CBC using crypto-data-128.json fixtures (#RTL7d) item 1 with encrypted encoding cipher+aes-128-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.322673"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-128-CBC using crypto-data-128.json fixtures (#RTL7d) item 1 with encrypted encoding cipher+aes-128-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.350280"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-128-CBC using crypto-data-128.json fixtures (#RTL7d) item 3 with encrypted encoding json/utf-8/cipher+aes-128-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.328634"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-128-CBC using crypto-data-128.json fixtures (#RTL7d) item 3 with encrypted encoding json/utf-8/cipher+aes-128-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.331841"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-128-CBC using crypto-data-128.json fixtures (#RTL7d) item 0 with encrypted encoding utf-8/cipher+aes-128-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.309380"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-128-CBC using crypto-data-128.json fixtures (#RTL7d) item 0 with encrypted encoding utf-8/cipher+aes-128-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.349067"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-128-CBC using crypto-data-128.json fixtures (#RTL7d) item 2 with encrypted encoding json/utf-8/cipher+aes-128-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.306712"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-128-CBC using crypto-data-128.json fixtures (#RTL7d) item 2 with encrypted encoding json/utf-8/cipher+aes-128-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.336368"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages publishing on an encrypted channel and subscribing on an unencrypted channel with another client logs a Cipher error (#RTL7e)" file="./spec/acceptance/realtime/message_spec.rb" time="0.613544"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages publishing on an encrypted channel and subscribing on an unencrypted channel with another client delivers the message but still encrypted with a value in the #encoding attribute (#RTL7e)" file="./spec/acceptance/realtime/message_spec.rb" time="0.626345"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages subscribing with a different transport protocol delivers a String UTF-8 payload to the receiver" file="./spec/acceptance/realtime/message_spec.rb" time="0.483747"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages subscribing with a different transport protocol delivers a String ASCII-8BIT payload to the receiver" file="./spec/acceptance/realtime/message_spec.rb" time="0.503405"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages subscribing with a different transport protocol delivers a Hash payload to the receiver" file="./spec/acceptance/realtime/message_spec.rb" time="0.490600"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages publishing on an unencrypted channel and subscribing on an encrypted channel with another client does not attempt to decrypt the message" file="./spec/acceptance/realtime/message_spec.rb" time="28.158007"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages publishing on an encrypted channel and subscribing with a different key on another client emits a Cipher error on the channel" file="./spec/acceptance/realtime/message_spec.rb" time="0.643833"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages publishing on an encrypted channel and subscribing with a different key on another client delivers the message but still encrypted with the cipher details in the #encoding attribute" file="./spec/acceptance/realtime/message_spec.rb" time="0.614436"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages publishing on an encrypted channel and subscribing with a different algorithm on another client delivers the message but still encrypted with the cipher detials in the #encoding attribute (#RTL7e)" file="./spec/acceptance/realtime/message_spec.rb" time="0.482726"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages publishing on an encrypted channel and subscribing with a different algorithm on another client emits a Cipher error on the channel (#RTL7e)" file="./spec/acceptance/realtime/message_spec.rb" time="0.610340"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 19 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.348319"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 19 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.315087"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 50 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.320977"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 50 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.333559"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 2 with encrypted encoding json/utf-8/cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.308283"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 2 with encrypted encoding json/utf-8/cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.351553"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 71 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.348719"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 71 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.318194"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 44 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.312754"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 44 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.347895"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 47 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.320015"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 47 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.345777"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 39 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.317313"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 39 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.346135"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 31 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.328430"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 31 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.307212"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 57 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.324210"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 57 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.351980"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 63 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.310321"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 63 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.350012"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 7 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.315365"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 7 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.319944"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 52 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.370177"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 52 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.317198"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 51 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.324100"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 51 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.331460"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 6 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.325898"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 6 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.310294"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 14 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.307657"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 14 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.343750"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 48 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.412505"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 48 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.326463"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 59 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.401786"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 59 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.304836"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 32 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.353125"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 32 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.304997"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 11 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.338047"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 11 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.310196"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 30 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.335247"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 30 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.350943"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 16 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.320288"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 16 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.327196"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 5 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.326935"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 5 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.355562"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 3 with encrypted encoding json/utf-8/cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.314772"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 3 with encrypted encoding json/utf-8/cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.321096"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 68 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.332277"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 68 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.305881"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 35 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.355537"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 35 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.311848"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 61 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.346065"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 61 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.295722"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 40 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.331799"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 40 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.315294"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 15 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.348906"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 15 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.323465"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 56 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.307061"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 56 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.365281"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 62 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.340302"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 62 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.370565"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 70 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.293784"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 70 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.339192"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 37 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.313247"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 37 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.380605"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 65 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.325018"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 65 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.345972"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 29 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.355328"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 29 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.320921"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 8 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.318187"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 8 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.313842"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 58 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.346185"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 58 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.327451"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 46 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.318853"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 46 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.332217"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 4 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.334936"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 4 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.319516"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 43 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.323876"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 43 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.337923"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 69 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.340132"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 69 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.316465"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 49 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.310284"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 49 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.329395"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 1 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.307947"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 1 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.346542"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 45 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.307079"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 45 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.320518"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 38 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.334953"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 38 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.294276"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 36 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.303923"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 36 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.332035"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 41 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.333061"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 41 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.330717"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 17 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.307496"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 17 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.325772"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 26 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.297950"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 26 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.346987"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 12 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.333082"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 12 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.319424"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 21 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.296410"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 21 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.336178"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 55 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.346836"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 55 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.335344"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 10 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.338126"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 10 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.293338"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 22 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.306685"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 22 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.349531"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 25 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.331313"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 25 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.354807"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 60 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.348491"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 60 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.321594"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 66 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.328494"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 66 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.296258"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 73 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.332559"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 73 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.309877"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 53 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.350649"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 53 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.304101"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 27 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.339716"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 27 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.312739"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 18 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.349612"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 18 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.309854"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 72 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.328230"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 72 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.348894"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 54 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.318249"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 54 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.317021"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 28 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.309785"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 28 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.340884"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 67 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.311160"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 67 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.352246"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 42 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.360614"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 42 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.320811"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 34 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.299326"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 34 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.352713"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 24 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.307483"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 24 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.350278"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 13 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.317933"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 13 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.356519"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 23 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.295721"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 23 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.361181"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 33 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.309256"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 33 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.340211"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 0 with encrypted encoding utf-8/cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.337141"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 0 with encrypted encoding utf-8/cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.314836"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 64 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.334965"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 64 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.308822"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 20 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.311393"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 20 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.319896"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 9 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe sends and receives messages that are encrypted &amp; decrypted by the Ably library (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.301995"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol encoding and decoding encrypted messages with AES-256-CBC using crypto-data-256.json fixtures (#RTL7d) item 9 with encrypted encoding cipher+aes-256-cbc/base64 behaves like an Ably encrypter and decrypter with #publish and #subscribe encrypts message automatically before they are pushed to the server (#RTL7d)" file="./spec/acceptance/realtime/message_spec.rb" time="0.347684"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol with supported data payload content type JSON Object (Hash) is encoded and decoded to the same hash" file="./spec/acceptance/realtime/message_spec.rb" time="0.316505"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol with supported data payload content type Binary is encoded and decoded to the same Array" file="./spec/acceptance/realtime/message_spec.rb" time="0.305635"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol with supported data payload content type JSON Array is encoded and decoded to the same Array" file="./spec/acceptance/realtime/message_spec.rb" time="0.320100"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol with supported data payload content type String is encoded and decoded to the same Array" file="./spec/acceptance/realtime/message_spec.rb" time="0.326371"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol a name with data payload (#RSL1a, #RSL1b) publishes a message" file="./spec/acceptance/realtime/message_spec.rb" time="0.301813"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol when the message publisher has a client_id contains a #client_id attribute" file="./spec/acceptance/realtime/message_spec.rb" time="0.507570"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol publishing lots of messages across two connections sends and receives the messages on both opened connections and calls the success callbacks for each message published" file="./spec/acceptance/realtime/message_spec.rb" time="1.351003"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol an array of hashes (#RSL1a) publishes three messages" file="./spec/acceptance/realtime/message_spec.rb" time="0.320773"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol with supported extra payload content type (#RTL6h, #RSL6a2) JSON Array is encoded and decoded to the same Array" file="./spec/acceptance/realtime/message_spec.rb" time="0.301925"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol with supported extra payload content type (#RTL6h, #RSL6a2) nil is encoded and decoded to the same Array" file="./spec/acceptance/realtime/message_spec.rb" time="0.186837"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol with supported extra payload content type (#RTL6h, #RSL6a2) JSON Object (Hash) is encoded and decoded to the same hash" file="./spec/acceptance/realtime/message_spec.rb" time="0.303664"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol a single Message object (#RSL1a) publishes the message" file="./spec/acceptance/realtime/message_spec.rb" time="0.296000"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol #connection_id attribute when retrieved over REST matches the sender connection#id" file="./spec/acceptance/realtime/message_spec.rb" time="0.406826"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol #connection_id attribute over realtime matches the sender connection#id" file="./spec/acceptance/realtime/message_spec.rb" time="0.506706"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol with unsupported data payload content type Boolean is raises an UnsupportedDataType 40013 exception" file="./spec/acceptance/realtime/message_spec.rb" time="0.155157"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol with unsupported data payload content type Integer is raises an UnsupportedDataType 40013 exception" file="./spec/acceptance/realtime/message_spec.rb" time="0.153973"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol with unsupported data payload content type False is raises an UnsupportedDataType 40013 exception" file="./spec/acceptance/realtime/message_spec.rb" time="0.153892"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol with unsupported data payload content type Float is raises an UnsupportedDataType 40013 exception" file="./spec/acceptance/realtime/message_spec.rb" time="0.153853"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol with ASCII_8BIT message name is converted into UTF_8" file="./spec/acceptance/realtime/message_spec.rb" time="0.334763"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol local echo when published is enabled by default" file="./spec/acceptance/realtime/message_spec.rb" time="0.336746"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol local echo when published with :echo_messages option set to false will not echo messages to the client from other REST clients publishing using that connection_key" file="./spec/acceptance/realtime/message_spec.rb" time="1.884467"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol local echo when published with :echo_messages option set to false will not echo messages to the client but will still broadcast messages to other connected clients" file="./spec/acceptance/realtime/message_spec.rb" time="2.144513"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol local echo when published with :echo_messages option set to false will echo messages with a valid connection_id to the client from other REST clients publishing using that connection_key" file="./spec/acceptance/realtime/message_spec.rb" time="1.833977"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol when message is published, the connection disconnects before the ACK is received, and the connection is resumed publishes the message again, later receives the ACK and only one message is ever received from Ably" file="./spec/acceptance/realtime/message_spec.rb" time="2.409549"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol server incorrectly resends a message that was already received by the client library discards the message and logs it as an error to the channel" file="./spec/acceptance/realtime/message_spec.rb" time="1.048673"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol when message is published, the connection disconnects before the ACK is received the connection is not resumed calls the errback for all messages" file="./spec/acceptance/realtime/message_spec.rb" time="0.392118"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol when message is published, the connection disconnects before the ACK is received the connection becomes suspended calls the errback for all messages" file="./spec/acceptance/realtime/message_spec.rb" time="0.271386"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol when message is published, the connection disconnects before the ACK is received the connection becomes failed calls the errback for all messages" file="./spec/acceptance/realtime/message_spec.rb" time="0.281229"></testcase>
<testcase classname="spec.acceptance.realtime.message_spec" name="Ably::Realtime::Channel Message using JSON protocol an array of Message objects (#RSL1a) publishes three messages" file="./spec/acceptance/realtime/message_spec.rb" time="0.331707"></testcase>
<testcase classname="spec.acceptance.rest.presence_spec" name="Ably::Rest::Presence using JSON protocol tested against presence fixture data set up in test app #get returns current members on the channel with their action set to :present" file="./spec/acceptance/rest/presence_spec.rb" time="0.061892"></testcase>
<testcase classname="spec.acceptance.rest.presence_spec" name="Ably::Rest::Presence using JSON protocol tested against presence fixture data set up in test app #get with :client_id option returns a list members filtered by the provided client ID" file="./spec/acceptance/rest/presence_spec.rb" time="12.542231"></testcase>
<testcase classname="spec.acceptance.rest.presence_spec" name="Ably::Rest::Presence using JSON protocol tested against presence fixture data set up in test app #get with :connection_id option returns a list members filtered by the provided connection ID" file="./spec/acceptance/rest/presence_spec.rb" time="0.098851"></testcase>
<testcase classname="spec.acceptance.rest.presence_spec" name="Ably::Rest::Presence using JSON protocol tested against presence fixture data set up in test app #get with :connection_id option returns a list members filtered by the provided connection ID" file="./spec/acceptance/rest/presence_spec.rb" time="0.049866"></testcase>
<testcase classname="spec.acceptance.rest.presence_spec" name="Ably::Rest::Presence using JSON protocol tested against presence fixture data set up in test app #get with :limit option returns a paged response limiting number of members per page" file="./spec/acceptance/rest/presence_spec.rb" time="0.067885"></testcase>
<testcase classname="spec.acceptance.rest.presence_spec" name="Ably::Rest::Presence using JSON protocol tested against presence fixture data set up in test app #get default :limit defaults to a limit of 100" file="./spec/acceptance/rest/presence_spec.rb" time="0.004964"></testcase>
<testcase classname="spec.acceptance.rest.presence_spec" name="Ably::Rest::Presence using JSON protocol tested against presence fixture data set up in test app #get with a non ASCII channel name stubbed correctly encodes the channel name" file="./spec/acceptance/rest/presence_spec.rb" time="0.004765"></testcase>
<testcase classname="spec.acceptance.rest.presence_spec" name="Ably::Rest::Presence using JSON protocol tested against presence fixture data set up in test app #history returns recent presence activity" file="./spec/acceptance/rest/presence_spec.rb" time="0.107833"></testcase>
<testcase classname="spec.acceptance.rest.presence_spec" name="Ably::Rest::Presence using JSON protocol tested against presence fixture data set up in test app #history default behaviour uses backwards direction" file="./spec/acceptance/rest/presence_spec.rb" time="0.078424"></testcase>
<testcase classname="spec.acceptance.rest.presence_spec" name="Ably::Rest::Presence using JSON protocol tested against presence fixture data set up in test app #history with options direction: :backwards returns recent presence activity backwards with most recent history first" file="./spec/acceptance/rest/presence_spec.rb" time="0.109781"></testcase>
<testcase classname="spec.acceptance.rest.presence_spec" name="Ably::Rest::Presence using JSON protocol tested against presence fixture data set up in test app #history with options direction: :forwards returns recent presence activity forwards with most recent history last" file="./spec/acceptance/rest/presence_spec.rb" time="0.126852"></testcase>
<testcase classname="spec.acceptance.rest.presence_spec" name="Ably::Rest::Presence using JSON protocol decoding permutations using mocked #history invalid data #get returns the messages still encoded" file="./spec/acceptance/rest/presence_spec.rb" time="0.006622"></testcase>
<testcase classname="spec.acceptance.rest.presence_spec" name="Ably::Rest::Presence using JSON protocol decoding permutations using mocked #history invalid data #get logs a cipher error" file="./spec/acceptance/rest/presence_spec.rb" time="0.005580"></testcase>
<testcase classname="spec.acceptance.rest.presence_spec" name="Ably::Rest::Presence using JSON protocol decoding permutations using mocked #history invalid data #history returns the messages still encoded" file="./spec/acceptance/rest/presence_spec.rb" time="0.005319"></testcase>
<testcase classname="spec.acceptance.rest.presence_spec" name="Ably::Rest::Presence using JSON protocol decoding permutations using mocked #history invalid data #history logs a cipher error" file="./spec/acceptance/rest/presence_spec.rb" time="0.005251"></testcase>
<testcase classname="spec.acceptance.rest.presence_spec" name="Ably::Rest::Presence using JSON protocol decoding permutations using mocked #history valid decodeable content #history automaticaly decodes presence messages" file="./spec/acceptance/rest/presence_spec.rb" time="0.005568"></testcase>
<testcase classname="spec.acceptance.rest.presence_spec" name="Ably::Rest::Presence using JSON protocol decoding permutations using mocked #history valid decodeable content #get automaticaly decodes presence messages" file="./spec/acceptance/rest/presence_spec.rb" time="0.005176"></testcase>
<testcase classname="spec.acceptance.rest.presence_spec" name="Ably::Rest::Presence using JSON protocol decoding with encoded fixture data #get decodes encoded and encryped presence fixture data automatically" file="./spec/acceptance/rest/presence_spec.rb" time="0.034866"></testcase>
<testcase classname="spec.acceptance.rest.presence_spec" name="Ably::Rest::Presence using JSON protocol decoding with encoded fixture data #history decodes encoded and encryped presence fixture data automatically" file="./spec/acceptance/rest/presence_spec.rb" time="0.043124"></testcase>
<testcase classname="spec.acceptance.rest.presence_spec" name="Ably::Rest::Presence using JSON protocol #history with options limit options default is set to 100" file="./spec/acceptance/rest/presence_spec.rb" time="0.004799"></testcase>
<testcase classname="spec.acceptance.rest.presence_spec" name="Ably::Rest::Presence using JSON protocol #history with options limit options set to 1000 is passes the limit query param value 1000" file="./spec/acceptance/rest/presence_spec.rb" time="0.003906"></testcase>
<testcase classname="spec.acceptance.rest.presence_spec" name="Ably::Rest::Presence using JSON protocol #history with options with time range options when argument start is after end should raise an exception" file="./spec/acceptance/rest/presence_spec.rb" time="0.000939"></testcase>
<testcase classname="spec.acceptance.rest.presence_spec" name="Ably::Rest::Presence using JSON protocol #history with options with time range options :start with Time object value converts the value to milliseconds since epoch in the hisotry request" file="./spec/acceptance/rest/presence_spec.rb" time="0.004035"></testcase>
<testcase classname="spec.acceptance.rest.presence_spec" name="Ably::Rest::Presence using JSON protocol #history with options with time range options :start with milliseconds since epoch value uses this value in the history request" file="./spec/acceptance/rest/presence_spec.rb" time="0.004084"></testcase>
<testcase classname="spec.acceptance.rest.presence_spec" name="Ably::Rest::Presence using JSON protocol #history with options with time range options :end with Time object value converts the value to milliseconds since epoch in the hisotry request" file="./spec/acceptance/rest/presence_spec.rb" time="0.004095"></testcase>
<testcase classname="spec.acceptance.rest.presence_spec" name="Ably::Rest::Presence using JSON protocol #history with options with time range options :end with milliseconds since epoch value uses this value in the history request" file="./spec/acceptance/rest/presence_spec.rb" time="0.004154"></testcase>
<testcase classname="spec.acceptance.realtime.stats_spec" name="Ably::Realtime::Client#stats using JSON protocol fetching stats returns a SafeDeferrable that catches exceptions in callbacks and logs them" file="./spec/acceptance/realtime/stats_spec.rb" time="0.154429"></testcase>
<testcase classname="spec.acceptance.realtime.stats_spec" name="Ably::Realtime::Client#stats using JSON protocol fetching stats returns a PaginatedResult" file="./spec/acceptance/realtime/stats_spec.rb" time="0.186366"></testcase>
<testcase classname="spec.acceptance.realtime.stats_spec" name="Ably::Realtime::Client#stats using JSON protocol fetching stats with options passes the option arguments to the REST stat method" file="./spec/acceptance/realtime/stats_spec.rb" time="0.154501"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol #request (#RSC19*, #TO3l9) get returns an HttpPaginatedResponse object" file="./spec/acceptance/rest/client_spec.rb" time="0.030138"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol #request (#RSC19*, #TO3l9) get paged results provides paging" file="./spec/acceptance/rest/client_spec.rb" time="0.438215"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol #request (#RSC19*, #TO3l9) get 404 request to invalid URL returns an object with 404 status code and error message" file="./spec/acceptance/rest/client_spec.rb" time="0.035401"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol #request (#RSC19*, #TO3l9) post supports post" file="./spec/acceptance/rest/client_spec.rb" time="0.009080"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol #request (#RSC19*, #TO3l9) post raises an exception once body size in bytes exceeded" file="./spec/acceptance/rest/client_spec.rb" time="0.003565"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol #request (#RSC19*, #TO3l9) delete supports delete" file="./spec/acceptance/rest/client_spec.rb" time="0.003605"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol #request (#RSC19*, #TO3l9) put supports put" file="./spec/acceptance/rest/client_spec.rb" time="0.003203"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol #request (#RSC19*, #TO3l9) put raises an exception once body size in bytes exceeded" file="./spec/acceptance/rest/client_spec.rb" time="0.003768"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol #request (#RSC19*, #TO3l9) patch raises an exception once body size in bytes exceeded" file="./spec/acceptance/rest/client_spec.rb" time="0.003579"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol #request (#RSC19*, #TO3l9) patch supports patch" file="./spec/acceptance/rest/client_spec.rb" time="0.003643"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol HTTP configuration options is frozen" file="./spec/acceptance/rest/client_spec.rb" time="0.000743"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol HTTP configuration options configured #http_request_timeout uses provided value" file="./spec/acceptance/rest/client_spec.rb" time="0.000595"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol HTTP configuration options configured #http_max_retry_count uses provided value" file="./spec/acceptance/rest/client_spec.rb" time="0.000728"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol HTTP configuration options configured #http_open_timeout uses provided value" file="./spec/acceptance/rest/client_spec.rb" time="0.000797"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol HTTP configuration options configured #http_max_retry_duration uses provided value" file="./spec/acceptance/rest/client_spec.rb" time="0.000782"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol HTTP configuration options defaults #http_open_timeout is 4s" file="./spec/acceptance/rest/client_spec.rb" time="0.000606"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol HTTP configuration options defaults #http_request_timeout is 10s" file="./spec/acceptance/rest/client_spec.rb" time="0.000751"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol HTTP configuration options defaults #http_max_retry_count is 3" file="./spec/acceptance/rest/client_spec.rb" time="0.000753"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol HTTP configuration options defaults #http_max_retry_duration is 15s" file="./spec/acceptance/rest/client_spec.rb" time="0.000669"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol failed request logging is absent when requests do not fail" file="./spec/acceptance/rest/client_spec.rb" time="0.028837"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol failed request logging with all requests failing is present when all requests fail" file="./spec/acceptance/rest/client_spec.rb" time="0.076056"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol failed request logging with the first request failing is present with success message when requests do not actually fail" file="./spec/acceptance/rest/client_spec.rb" time="0.072315"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol connection transport defaults for the fallback hosts is configured to timeout connection opening in 4 seconds" file="./spec/acceptance/rest/client_spec.rb" time="0.001901"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol connection transport defaults for the fallback hosts is configured to timeout connection requests in 10 seconds" file="./spec/acceptance/rest/client_spec.rb" time="0.001530"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol connection transport defaults for default host is configured to timeout connection requests in 10 seconds" file="./spec/acceptance/rest/client_spec.rb" time="0.001047"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol connection transport defaults for default host is configured to timeout connection opening in 4 seconds" file="./spec/acceptance/rest/client_spec.rb" time="0.000942"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol connection transport with custom http_open_timeout and http_request_timeout options for default host is configured to use custom request timeout" file="./spec/acceptance/rest/client_spec.rb" time="0.000946"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol connection transport with custom http_open_timeout and http_request_timeout options for default host is configured to use custom open timeout" file="./spec/acceptance/rest/client_spec.rb" time="0.000965"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol connection transport with custom http_open_timeout and http_request_timeout options for the fallback hosts is configured to timeout connection opening in 4 seconds" file="./spec/acceptance/rest/client_spec.rb" time="0.001501"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol connection transport with custom http_open_timeout and http_request_timeout options for the fallback hosts is configured to timeout connection requests in 10 seconds" file="./spec/acceptance/rest/client_spec.rb" time="0.001619"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol version headers with custom ably-ruby/1.1.1 ruby/3.1.1 agent sends a protocol version and lib version header (#G4, #RSC7a, #RSC7b)" file="./spec/acceptance/rest/client_spec.rb" time="0.004319"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol version headers with default agent sends a protocol version and lib version header (#G4, #RSC7a, #RSC7b)" file="./spec/acceptance/rest/client_spec.rb" time="0.003544"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol #initialize with an :auth_callback lambda uses token authentication" file="./spec/acceptance/rest/client_spec.rb" time="0.000760"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol #initialize with an :auth_callback lambda calls the auth lambda to get a new token" file="./spec/acceptance/rest/client_spec.rb" time="0.074768"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol #initialize with :default_token_params overides the default token params (#TO3j11)" file="./spec/acceptance/rest/client_spec.rb" time="0.035599"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol #initialize with an invalid wildcard &quot;*&quot; :client_id raises an exception" file="./spec/acceptance/rest/client_spec.rb" time="0.001006"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol #initialize with a non string :client_id raises an ArgumentError" file="./spec/acceptance/rest/client_spec.rb" time="0.000796"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol #initialize with an auth URL uses token authentication" file="./spec/acceptance/rest/client_spec.rb" time="0.000702"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol #initialize with an auth URL before any REST request sends an HTTP request to the provided auth URL to get a new token" file="./spec/acceptance/rest/client_spec.rb" time="0.070065"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol #initialize with only an API key uses basic authentication" file="./spec/acceptance/rest/client_spec.rb" time="0.001025"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol #initialize auth headers with basic auth sends the API key in authentication part of the secure URL (the Authorization: Basic header is not used with the Faraday HTTP library by default)" file="./spec/acceptance/rest/client_spec.rb" time="0.004411"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol #initialize auth headers with token auth without specifying protocol sends the token string over HTTPS in the Authorization Bearer header with Base64 encoding" file="./spec/acceptance/rest/client_spec.rb" time="0.003905"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol #initialize auth headers with token auth when setting constructor ClientOption :tls to false sends the token string over HTTP in the Authorization Bearer header with Base64 encoding" file="./spec/acceptance/rest/client_spec.rb" time="0.003875"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol #initialize with :use_token_auth set to true uses token authentication" file="./spec/acceptance/rest/client_spec.rb" time="0.000791"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol #initialize with an explicit string :token uses token authentication" file="./spec/acceptance/rest/client_spec.rb" time="0.001083"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol #initialize with an invalid API key logs an entry with a help href url matching the code #TI5" file="./spec/acceptance/rest/client_spec.rb" time="0.348251"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol #initialize with an :auth_callback lambda (clientId provided in library options instead of as a token_request param) correctly sets the clientId on the token" file="./spec/acceptance/rest/client_spec.rb" time="0.135519"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol fallback hosts when environment is NOT production (#RSC15b) and custom fallback hosts are empty does not retry failed requests with fallback hosts when there is a connection error" file="./spec/acceptance/rest/client_spec.rb" time="0.005029"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol fallback hosts when environment is NOT production (#RSC15b) and no custom fallback hosts are provided should make connection attempts to sandbox-a-fallback.ably-realtime.com, sandbox-b-fallback.ably-realtime.com, sandbox-c-fallback.ably-realtime.com, sandbox-d-fallback.ably-realtime.com, sandbox-e-fallback.ably-realtime.com (#RSC15a)" file="./spec/acceptance/rest/client_spec.rb" time="0.002030"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol fallback hosts when environment is production and server returns a 50x error with an empty array of fallback hosts provided (#RSC15b, #RSC15a, #TO3k6) does not attempt the fallback hosts as this is an authentication failure" file="./spec/acceptance/rest/client_spec.rb" time="0.004087"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol fallback hosts when environment is production and server returns a 50x error with custom fallback hosts provided attempts the fallback hosts as this is an authentication failure (#RSC15b, #RSC15a, #TO3k6)" file="./spec/acceptance/rest/client_spec.rb" time="0.007732"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol fallback hosts when environment is production and server returns a 50x error using a local web-server to fail the primary host, allow a fallback to succeed, then later trigger a fallback to the primary host (#RSC15f) succeeds and remembers fallback host preferences across requests" file="./spec/acceptance/rest/client_spec.rb" time="0.237903"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol fallback hosts when environment is production and server returns a 50x error using a local web-server to fail the primary host, allow a fallback to succeed, then later trigger a fallback to the primary host (#RSC15f) with custom :fallback_retry_timeout stops using the preferred fallback after this time" file="./spec/acceptance/rest/client_spec.rb" time="5.060712"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol fallback hosts when environment is production and server returns a 50x error using a local web-server and timing out the primary host GET with request timeout less than max_retry_duration tries the primary host, then both fallback hosts (#RSC15d)" file="./spec/acceptance/rest/client_spec.rb" time="6.011290"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol fallback hosts when environment is production and server returns a 50x error using a local web-server and timing out the primary host GET with request timeout more than max_retry_duration does not try any fallback hosts (#RSC15d)" file="./spec/acceptance/rest/client_spec.rb" time="3.005463"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol fallback hosts when environment is production and server returns a 50x error using a local web-server and timing out the primary host POST with request timeout less than max_retry_duration tries the primary host, then both fallback hosts (#RSC15d)" file="./spec/acceptance/rest/client_spec.rb" time="6.012678"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol fallback hosts when environment is production and server returns a 50x error using a local web-server and timing out the primary host POST with request timeout more than max_retry_duration does not try any fallback hosts (#RSC15d)" file="./spec/acceptance/rest/client_spec.rb" time="3.005575"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol fallback hosts when environment is production and server returns a 50x error using a local web-server and failing the primary host tries one of the fallback hosts" file="./spec/acceptance/rest/client_spec.rb" time="0.039557"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol fallback hosts configured should make connection attempts to a.ably-realtime.com, b.ably-realtime.com, c.ably-realtime.com, d.ably-realtime.com, e.ably-realtime.com (#RSC15a)" file="./spec/acceptance/rest/client_spec.rb" time="0.002271"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol fallback hosts when environment is production and first request to primary endpoint fails tries a fallback host, and for the next request tries the primary endpoint again (#RSC15e)" file="./spec/acceptance/rest/client_spec.rb" time="0.009026"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol fallback hosts when environment is production and server returns a 50x error attempts the fallback hosts as this is an authentication failure (#RSC15d)" file="./spec/acceptance/rest/client_spec.rb" time="0.007301"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol fallback hosts when environment is production and connection fails tries fallback hosts 3 times" file="./spec/acceptance/rest/client_spec.rb" time="0.006848"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol fallback hosts when environment is production and basic authentication fails does not attempt the fallback hosts as this is an authentication failure" file="./spec/acceptance/rest/client_spec.rb" time="0.003954"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol fallback hosts when environment is production and connection times out tries fallback hosts 3 times (#RSC15b, #RSC15b)" file="./spec/acceptance/rest/client_spec.rb" time="0.006531"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol fallback hosts when environment is production and connection times out and the total request time exeeds 15 seconds makes no further attempts to any fallback hosts" file="./spec/acceptance/rest/client_spec.rb" time="0.755565"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol fallback hosts when environment is not production and server returns a 50x error with an empty array of fallback hosts provided (#RSC15b, #TO3k6) does not attempt the fallback hosts as this is an authentication failure" file="./spec/acceptance/rest/client_spec.rb" time="0.005000"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol fallback hosts when environment is not production and server returns a 50x error with no fallback hosts provided (#TBC, see https://github.com/ably/wiki/issues/361) uses the default fallback hosts for that environment as this is not an authentication failure" file="./spec/acceptance/rest/client_spec.rb" time="0.009629"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol fallback hosts when environment is not production and server returns a 50x error with fallback_hosts_use_default: true (#RSC15b, #TO3k7) attempts the default fallback hosts as this is an authentication failure" file="./spec/acceptance/rest/client_spec.rb" time="0.007734"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol fallback hosts when environment is not production and server returns a 50x error with custom fallback hosts provided (#RSC15b, #TO3k6) attempts the fallback hosts as this is not an authentication failure" file="./spec/acceptance/rest/client_spec.rb" time="0.007599"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol with a custom host that does not exist fails immediately and raises a Faraday Error" file="./spec/acceptance/rest/client_spec.rb" time="0.080126"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol with a custom host that does not exist fallback hosts are never used" file="./spec/acceptance/rest/client_spec.rb" time="0.009961"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol with a custom host that times out fails immediately and raises a Faraday Error" file="./spec/acceptance/rest/client_spec.rb" time="0.004029"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol with a custom host that times out fallback hosts are never used" file="./spec/acceptance/rest/client_spec.rb" time="0.005173"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol using tokens when expired creates a new token automatically when the old token expires" file="./spec/acceptance/rest/client_spec.rb" time="1.178827"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol using tokens when expired with a different client_id in the subsequent token fails to authenticate and raises an exception" file="./spec/acceptance/rest/client_spec.rb" time="1.102738"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol using tokens when token has not expired reuses the existing token for every request" file="./spec/acceptance/rest/client_spec.rb" time="1.102676"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol request_id generation (#RSC7c) UnauthorizedRequest nonce error includes request_id in UnauthorizedRequest error due to replayed nonce" file="./spec/acceptance/rest/client_spec.rb" time="0.065174"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol request_id generation (#RSC7c) Timeout error option add_request_ids: true and specified fallback hosts request_id is the same across retries" file="./spec/acceptance/rest/client_spec.rb" time="0.013181"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol request_id generation (#RSC7c) Timeout error with option add_request_ids: true and no fallback hosts has an error with the same request_id of the request" file="./spec/acceptance/rest/client_spec.rb" time="0.003205"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol request_id generation (#RSC7c) Timeout error without request_id and no fallback hosts does not include request_id in ConnectionTimeout error" file="./spec/acceptance/rest/client_spec.rb" time="0.039770"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol request_id generation (#RSC7c) Timeout error with option add_request_ids: true and REST operations with a message body with mocks to inspect the params with a single publish succeeds and sends the request_id as a param" file="./spec/acceptance/rest/client_spec.rb" time="0.005437"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol request_id generation (#RSC7c) Timeout error with option add_request_ids: true and REST operations with a message body with mocks to inspect the params with an array publish succeeds and sends the request_id as a param" file="./spec/acceptance/rest/client_spec.rb" time="0.004715"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol request_id generation (#RSC7c) Timeout error with option add_request_ids: true and REST operations with a message body without mocks to ensure the requests are accepted with an array publish succeeds and sends the request_id as a param" file="./spec/acceptance/rest/client_spec.rb" time="0.131216"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol request_id generation (#RSC7c) Timeout error with option add_request_ids: true and REST operations with a message body without mocks to ensure the requests are accepted with a single publish succeeds and sends the request_id as a param" file="./spec/acceptance/rest/client_spec.rb" time="0.134551"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol #auth is provides access to the Auth object" file="./spec/acceptance/rest/client_spec.rb" time="0.001003"></testcase>
<testcase classname="spec.acceptance.rest.client_spec" name="Ably::Rest::Client using JSON protocol #auth configures the Auth object with all ClientOptions passed to client in the initializer" file="./spec/acceptance/rest/client_spec.rb" time="0.000655"></testcase>
</testsuite>
