Core over WSS, native task

1.1.1 Send text message with payload 0. OK

Expected

Receive echo'ed text message (with empty payload). Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 5 ms

1.1.2 Send text message message with payload of length 125. OK

Expected

Receive echo'ed text message (with payload as sent). Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

1.1.3 Send text message message with payload of length 126. OK

Expected

Receive echo'ed text message (with payload as sent). Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 3 ms

1.1.4 Send text message message with payload of length 127. OK

Expected

Receive echo'ed text message (with payload as sent). Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

1.1.5 Send text message message with payload of length 128. OK

Expected

Receive echo'ed text message (with payload as sent). Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

1.1.6 Send text message message with payload of length 65535. OK

Expected

Receive echo'ed text message (with payload as sent). Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 7 ms

1.1.7 Send text message message with payload of length 65536. OK

Expected

Receive echo'ed text message (with payload as sent). Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 4 ms

1.1.8 Send text message message with payload of length 65536. Sent out data in chops of 997 octets. OK

Expected

Receive echo'ed text message (with payload as sent). Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 10 ms

1.2.1 Send binary message with payload 0. OK

Expected

Receive echo'ed binary message (with empty payload). Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

1.2.2 Send binary message message with payload of length 125. OK

Expected

Receive echo'ed binary message (with payload as sent). Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

1.2.3 Send binary message message with payload of length 126. OK

Expected

Receive echo'ed binary message (with payload as sent). Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

1.2.4 Send binary message message with payload of length 127. OK

Expected

Receive echo'ed binary message (with payload as sent). Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

1.2.5 Send binary message message with payload of length 128. OK

Expected

Receive echo'ed binary message (with payload as sent). Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

1.2.6 Send binary message message with payload of length 65535. OK

Expected

Receive echo'ed binary message (with payload as sent). Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 17 ms

1.2.7 Send binary message message with payload of length 65536. OK

Expected

Receive echo'ed binary message (with payload as sent). Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 5 ms

1.2.8 Send binary message message with payload of length 65536. Sent out data in chops of 997 octets. OK

Expected

Receive echo'ed binary message (with payload as sent). Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 10 ms

2.1 Send ping without payload. OK

Expected

Pong (with empty payload) is sent in reply to Ping. Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

2.2 Send ping with small text payload. OK

Expected

Pong with payload echo'ed is sent in reply to Ping. Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

2.3 Send ping with small binary (non UTF-8) payload. OK

Expected

Pong with payload echo'ed is sent in reply to Ping. Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

2.4 Send ping with binary payload of 125 octets. OK

Expected

Pong with payload echo'ed is sent in reply to Ping. Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

2.5 Send ping with binary payload of 126 octets. OK

Expected

Connection is failed immediately (1002/Protocol Error), since control frames are only allowed to have payload up to and including 125 octets..

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 2 ms

2.6 Send ping with binary payload of 125 octets, send in octet-wise chops. OK

Expected

Pong with payload echo'ed is sent in reply to Ping. Implementations must be TCP clean. Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 24 ms

2.7 Send unsolicited pong without payload. Verify nothing is received. Clean close with normal code. OK

Expected

Nothing.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

2.8 Send unsolicited pong with payload. Verify nothing is received. Clean close with normal code. OK

Expected

Nothing.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

2.9 Send unsolicited pong with payload. Send ping with payload. Verify pong for ping is received. OK

Expected

Nothing in reply to own Pong, but Pong with payload echo'ed in reply to Ping. Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

2.10 Send 10 Pings with payload. OK

Expected

Pongs for our Pings with all the payloads. Note: This is not required by the Spec .. but we check for this behaviour anyway. Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 5 ms

2.11 Send 10 Pings with payload. Send out octets in octet-wise chops. OK

Expected

Pongs for our Pings with all the payloads. Note: This is not required by the Spec .. but we check for this behaviour anyway. Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 19 ms

3.1 Send small text message with RSV = 1. OK

Expected

The connection is failed immediately (1002/protocol error), since RSV must be 0, when no extension defining RSV meaning has been negotiated.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 2 ms

3.2 Send small text message, then send again with RSV = 2, then send Ping. OK

Expected

Echo for first message is received, but then connection is failed immediately, since RSV must be 0, when no extension defining RSV meaning has been negotiated. The Pong is not received.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 1 ms

3.3 Send small text message, then send again with RSV = 3, then send Ping. Octets are sent in frame-wise chops. Octets are sent in octet-wise chops. OK

Expected

Echo for first message is received, but then connection is failed immediately, since RSV must be 0, when no extension defining RSV meaning has been negotiated. The Pong is not received.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 1 ms

3.4 Send small text message, then send again with RSV = 4, then send Ping. Octets are sent in octet-wise chops. OK

Expected

Echo for first message is received, but then connection is failed immediately, since RSV must be 0, when no extension defining RSV meaning has been negotiated. The Pong is not received.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 3 ms

3.5 Send small binary message with RSV = 5. OK

Expected

The connection is failed immediately, since RSV must be 0.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 1 ms

3.6 Send Ping with RSV = 6. OK

Expected

The connection is failed immediately, since RSV must be 0.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 1 ms

3.7 Send Close with RSV = 7. OK

Expected

The connection is failed immediately, since RSV must be 0.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 1 ms

4.1.1 Send frame with reserved non-control Opcode = 3. OK

Expected

The connection is failed immediately.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 1 ms

4.1.2 Send frame with reserved non-control Opcode = 4 and non-empty payload. OK

Expected

The connection is failed immediately.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 1 ms

4.1.3 Send small text message, then send frame with reserved non-control Opcode = 5, then send Ping. OK

Expected

Echo for first message is received, but then connection is failed immediately, since reserved opcode frame is used. A Pong is not received.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 1 ms

4.1.4 Send small text message, then send frame with reserved non-control Opcode = 6 and non-empty payload, then send Ping. OK

Expected

Echo for first message is received, but then connection is failed immediately, since reserved opcode frame is used. A Pong is not received.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 1 ms

4.1.5 Send small text message, then send frame with reserved non-control Opcode = 7 and non-empty payload, then send Ping. OK

Expected

Echo for first message is received, but then connection is failed immediately, since reserved opcode frame is used. A Pong is not received.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 3 ms

4.2.1 Send frame with reserved control Opcode = 11. OK

Expected

The connection is failed immediately.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 1 ms

4.2.2 Send frame with reserved control Opcode = 12 and non-empty payload. OK

Expected

The connection is failed immediately.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 1 ms

4.2.3 Send small text message, then send frame with reserved control Opcode = 13, then send Ping. OK

Expected

Echo for first message is received, but then connection is failed immediately, since reserved opcode frame is used. A Pong is not received.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 1 ms

4.2.4 Send small text message, then send frame with reserved control Opcode = 14 and non-empty payload, then send Ping. OK

Expected

Echo for first message is received, but then connection is failed immediately, since reserved opcode frame is used. A Pong is not received.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 1 ms

4.2.5 Send small text message, then send frame with reserved control Opcode = 15 and non-empty payload, then send Ping. OK

Expected

Echo for first message is received, but then connection is failed immediately, since reserved opcode frame is used. A Pong is not received.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 8 ms

5.1 Send Ping fragmented into 2 fragments. OK

Expected

Connection is failed immediately, since control message MUST NOT be fragmented.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 1 ms

5.2 Send Pong fragmented into 2 fragments. OK

Expected

Connection is failed immediately, since control message MUST NOT be fragmented.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 1 ms

5.3 Send text Message fragmented into 2 fragments. OK

Expected

Message is processed and echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

5.4 Send text Message fragmented into 2 fragments, octets are sent in frame-wise chops. OK

Expected

Message is processed and echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

5.5 Send text Message fragmented into 2 fragments, octets are sent in octet-wise chops. OK

Expected

Message is processed and echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 4 ms

5.6 Send text Message fragmented into 2 fragments, one ping with payload in-between. OK

Expected

A pong is received, then the message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

5.7 Send text Message fragmented into 2 fragments, one ping with payload in-between. Octets are sent in frame-wise chops. OK

Expected

A pong is received, then the message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

5.8 Send text Message fragmented into 2 fragments, one ping with payload in-between. Octets are sent in octet-wise chops. OK

Expected

A pong is received, then the message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 8 ms

5.9 Send unfragmented Text Message after Continuation Frame with FIN = true, where there is nothing to continue, sent in one chop. OK

Expected

The connection is failed immediately, since there is no message to continue.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 1 ms

5.10 Send unfragmented Text Message after Continuation Frame with FIN = true, where there is nothing to continue, sent in per-frame chops. OK

Expected

The connection is failed immediately, since there is no message to continue.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 1 ms

5.11 Send unfragmented Text Message after Continuation Frame with FIN = true, where there is nothing to continue, sent in octet-wise chops. OK

Expected

The connection is failed immediately, since there is no message to continue.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 2 ms

5.12 Send unfragmented Text Message after Continuation Frame with FIN = false, where there is nothing to continue, sent in one chop. OK

Expected

The connection is failed immediately, since there is no message to continue.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 1 ms

5.13 Send unfragmented Text Message after Continuation Frame with FIN = false, where there is nothing to continue, sent in per-frame chops. OK

Expected

The connection is failed immediately, since there is no message to continue.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 2 ms

5.14 Send unfragmented Text Message after Continuation Frame with FIN = false, where there is nothing to continue, sent in octet-wise chops. OK

Expected

The connection is failed immediately, since there is no message to continue.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 2 ms

5.15 Send text Message fragmented into 2 fragments, then Continuation Frame with FIN = false where there is nothing to continue, then unfragmented Text… OK

Expected

The connection is failed immediately, since there is no message to continue.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 2 ms

5.16 Repeated 2x: Continuation Frame with FIN = false (where there is nothing to continue), then text Message fragmented into 2 fragments. OK

Expected

The connection is failed immediately, since there is no message to continue.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 2 ms

5.17 Repeated 2x: Continuation Frame with FIN = true (where there is nothing to continue), then text Message fragmented into 2 fragments. OK

Expected

The connection is failed immediately, since there is no message to continue.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 2 ms

5.18 Send text Message fragmented into 2 fragments, with both frame opcodes set to text, sent in one chop. OK

Expected

The connection is failed immediately, since all data frames after the initial data frame must have opcode 0.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 1 ms

5.19 A fragmented text message is sent in multiple frames. After OK

Expected

The peer immediately answers the first Ping before
it has received the last text message fragment. The peer pong's back the Ping's
payload exactly, and echo's the payload of the fragmented message back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1012 ms

5.20 Same as Case 5.19, but send all frames with SYNC = True. OK

Expected

Same as Case 5.19. Implementations must be agnostic to how
octet stream is chopped up on wire (must be TCP clean).

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1016 ms

6.1.1 Send text message of length 0. OK

Expected

A message is echo'ed back to us (with empty payload).

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.1.2 Send fragmented text message, 3 fragments each of length 0. OK

Expected

A message is echo'ed back to us (with empty payload).

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.1.3 Send fragmented text message, 3 fragments, first and last of length 0, middle non-empty. OK

Expected

A message is echo'ed back to us (with payload = payload of middle fragment).

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.2.1 Send a valid UTF-8 text message in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.2.2 Send a valid UTF-8 text message in two fragments, fragmented on UTF-8 code point boundary. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.2.3 Send a valid UTF-8 text message in fragments of 1 octet, resulting in frames ending on positions which are not code point ends. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 9 ms

6.2.4 Send a valid UTF-8 text message in fragments of 1 octet, resulting in frames ending on positions which are not code point ends. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.3.1 Send invalid UTF-8 text message unfragmented. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.3.2 Send invalid UTF-8 text message in fragments of 1 octet, resulting in frames ending on positions which are not code point ends. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.4.1 Send invalid UTF-8 text message in 3 fragments (frames). Non-strict

Expected

The first frame is accepted, we expect to timeout on the first wait. The 2nd frame should be rejected immediately (fail fast on UTF-8). If we timeout, we expect the connection is failed at least then, since the complete message payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 2011 ms

6.4.2 Same as Case 6.4.1, but in 2nd frame, we send only up to and including the octet making the complete payload invalid. Non-strict

Expected

The first frame is accepted, we expect to timeout on the first wait. The 2nd frame should be rejected immediately (fail fast on UTF-8). If we timeout, we expect the connection is failed at least then, since the complete message payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 2009 ms

6.4.3 Same as Case 6.4.1, but we send message not in 3 frames, but in 3 chops of the same message frame. Non-strict

Expected

The first chop is accepted, we expect to timeout on the first wait. The 2nd chop should be rejected immediately (fail fast on UTF-8). If we timeout, we expect the connection is failed at least then, since the complete message payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 2012 ms

6.4.4 Same as Case 6.4.2, but we send message not in 3 frames, but in 3 chops of the same message frame. Non-strict

Expected

The first chop is accepted, we expect to timeout on the first wait. The 2nd chop should be rejected immediately (fail fast on UTF-8). If we timeout, we expect the connection is failed at least then, since the complete message payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 2009 ms

6.5.1 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 4 ms

6.5.2 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 3 ms

6.5.3 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.5.4 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.5.5 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 3 ms

6.6.1 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.6.2 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.6.3 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.6.4 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 5 ms

6.6.5 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.6.6 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.6.7 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.6.8 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.6.9 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.6.10 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.6.11 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.7.1 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.7.2 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 4 ms

6.7.3 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.7.4 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.8.1 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.8.2 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.9.1 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.9.2 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.9.3 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.9.4 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.10.1 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.10.2 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.10.3 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.11.1 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.11.2 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 4 ms

6.11.3 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.11.4 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.11.5 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.12.1 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.12.2 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.12.3 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.12.4 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.12.5 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.12.6 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 4 ms

6.12.7 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.12.8 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.13.1 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.13.2 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.13.3 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.13.4 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.13.5 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.14.1 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.14.2 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.14.3 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.14.4 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.14.5 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 9 ms

6.14.6 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.14.7 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.14.8 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.14.9 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.14.10 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.15.1 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 5 ms

6.16.1 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.16.2 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.16.3 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.17.1 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 9 ms

6.17.2 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.17.3 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.17.4 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.17.5 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.18.1 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.18.2 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.18.3 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.18.4 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.18.5 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 5 ms

6.19.1 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.19.2 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.19.3 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.19.4 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.19.5 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.20.1 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.20.2 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.20.3 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.20.4 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.20.5 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.20.6 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.20.7 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.21.1 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.21.2 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.21.3 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.21.4 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.21.5 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.21.6 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.21.7 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.21.8 Send a text message with payload which is not valid UTF-8 in one fragment. OK

Expected

The connection is failed immediately, since the payload is not valid UTF-8.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.22.1 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.22.2 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.22.3 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.22.4 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 6 ms

6.22.5 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.22.6 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.22.7 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.22.8 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.22.9 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.22.10 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.22.11 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.22.12 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 10 ms

6.22.13 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.22.14 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.22.15 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.22.16 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.22.17 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.22.18 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.22.19 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 7 ms

6.22.20 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.22.21 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.22.22 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.22.23 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 4 ms

6.22.24 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.22.25 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.22.26 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.22.27 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.22.28 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.22.29 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

6.22.30 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.22.31 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.22.32 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 3 ms

6.22.33 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.22.34 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.23.1 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.23.2 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.23.3 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.23.4 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.23.5 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.23.6 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

6.23.7 Send a text message with payload which is valid UTF-8 in one fragment. OK

Expected

The message is echo'ed back to us.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

7.1.1 Send a message followed by a close frame OK

Expected

Echoed message followed by clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

7.1.2 Send two close frames OK

Expected

Clean close with normal code. Second close frame ignored.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

7.1.3 Send a ping after close message OK

Expected

Clean close with normal code, no pong.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

7.1.4 Send text message after sending a close frame. OK

Expected

Clean close with normal code. Text message ignored.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

7.1.5 Send message fragment1 followed by close then fragment OK

Expected

Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 2 ms

7.1.6 Send 256K message followed by close then a ping Informational

Expected

Case outcome depends on implementation defined close behavior. Message and close frame are sent back to back. If the close frame is processed before the text message write is complete (as can happen in asynchronous processing models) the close frame is processed first and the text message may not be received or may only be partially received.

Observed

Close was processed before text message could be returned.

The spec requires the connection to be failed cleanly here

Remote close: Not recorded
Local close: 1000
Clean close: No
Duration: 6 ms

7.3.1 Send a close frame with payload length 0 (no close code, no close reason) OK

Expected

Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: Not recorded
Local close: Not recorded
Clean close: Yes
Duration: 1 ms

7.3.2 Send a close frame with payload length 1 OK

Expected

Clean close with protocol error or drop TCP.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: Not recorded
Clean close: Yes
Duration: 1 ms

7.3.3 Send a close frame with payload length 2 (regular close with a code) OK

Expected

Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

7.3.4 Send a close frame with close code and close reason OK

Expected

Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

7.3.5 Send a close frame with close code and close reason of maximum length (123) OK

Expected

Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

7.3.6 Send a close frame with close code and close reason which is too long (124) - total frame payload 126 octets OK

Expected

Clean close with protocol error code or dropped TCP connection.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1000
Clean close: Yes
Duration: 1 ms

7.5.1 Send a close frame with invalid UTF8 payload OK

Expected

Clean close with protocol error or invalid utf8 code or dropped TCP.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1000
Clean close: Yes
Duration: 1 ms

7.7.1 Send close with valid close code 1000 OK

Expected

Clean close with normal or echoed code

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 1 ms

7.7.2 Send close with valid close code 1001 OK

Expected

Clean close with normal or echoed code

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1001
Local close: 1001
Clean close: Yes
Duration: 1 ms

7.7.3 Send close with valid close code 1002 OK

Expected

Clean close with normal or echoed code

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1002
Clean close: Yes
Duration: 1 ms

7.7.4 Send close with valid close code 1003 OK

Expected

Clean close with normal or echoed code

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1003
Local close: 1003
Clean close: Yes
Duration: 1 ms

7.7.5 Send close with valid close code 1007 OK

Expected

Clean close with normal or echoed code

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1007
Local close: 1007
Clean close: Yes
Duration: 1 ms

7.7.6 Send close with valid close code 1008 OK

Expected

Clean close with normal or echoed code

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1008
Local close: 1008
Clean close: Yes
Duration: 5 ms

7.7.7 Send close with valid close code 1009 OK

Expected

Clean close with normal or echoed code

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1009
Local close: 1009
Clean close: Yes
Duration: 1 ms

7.7.8 Send close with valid close code 1010 OK

Expected

Clean close with normal or echoed code

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1010
Local close: 1010
Clean close: Yes
Duration: 1 ms

7.7.9 Send close with valid close code 1011 OK

Expected

Clean close with normal or echoed code

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1011
Local close: 1011
Clean close: Yes
Duration: 1 ms

7.7.10 Send close with valid close code 3000 OK

Expected

Clean close with normal or echoed code

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 3000
Local close: 3000
Clean close: Yes
Duration: 1 ms

7.7.11 Send close with valid close code 3999 OK

Expected

Clean close with normal or echoed code

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 3999
Local close: 3999
Clean close: Yes
Duration: 1 ms

7.7.12 Send close with valid close code 4000 OK

Expected

Clean close with normal or echoed code

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 4000
Local close: 4000
Clean close: Yes
Duration: 1 ms

7.7.13 Send close with valid close code 4999 OK

Expected

Clean close with normal or echoed code

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 4999
Local close: 4999
Clean close: Yes
Duration: 1 ms

7.9.1 Send close with invalid close code 0 OK

Expected

Clean close with protocol error code or drop TCP

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 0
Clean close: Yes
Duration: 1 ms

7.9.2 Send close with invalid close code 999 OK

Expected

Clean close with protocol error code or drop TCP

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 999
Clean close: Yes
Duration: 1 ms

7.9.3 Send close with invalid close code 1004 OK

Expected

Clean close with protocol error code or drop TCP

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1004
Clean close: Yes
Duration: 1 ms

7.9.4 Send close with invalid close code 1005 OK

Expected

Clean close with protocol error code or drop TCP

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1005
Clean close: Yes
Duration: 1 ms

7.9.5 Send close with invalid close code 1006 OK

Expected

Clean close with protocol error code or drop TCP

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1006
Clean close: Yes
Duration: 1 ms

7.9.6 Send close with invalid close code 1016 OK

Expected

Clean close with protocol error code or drop TCP

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1016
Clean close: Yes
Duration: 1 ms

7.9.7 Send close with invalid close code 1100 OK

Expected

Clean close with protocol error code or drop TCP

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 1100
Clean close: Yes
Duration: 1 ms

7.9.8 Send close with invalid close code 2000 OK

Expected

Clean close with protocol error code or drop TCP

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 2000
Clean close: Yes
Duration: 1 ms

7.9.9 Send close with invalid close code 2999 OK

Expected

Clean close with protocol error code or drop TCP

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1002
Local close: 2999
Clean close: Yes
Duration: 1 ms

7.13.1 Send close with close code 5000 Informational

Expected

Actual events are undefined by the spec.

Observed

Actual events are undefined by the spec.

Connection was properly closed

Remote close: 1002
Local close: 5000
Clean close: Yes
Duration: 1 ms

7.13.2 Send close with close code 65535 Informational

Expected

Actual events are undefined by the spec.

Observed

Actual events are undefined by the spec.

Connection was properly closed

Remote close: 1002
Local close: 65535
Clean close: Yes
Duration: 1 ms

10.1.1 Send text message with payload of length 65536 auto-fragmented with autoFragmentSize = 1300. OK

Expected

Receive echo'ed text message (with payload as sent and transmitted frame counts as expected). Clean close with normal code.

Observed

Actual events match at least one expected.

Connection was properly closed

Remote close: 1000
Local close: 1000
Clean close: Yes
Duration: 7 ms

247 cases, in suite order.

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected

Observed

Expected