Toggle Details

Summary report generated on 2013-10-13T14:47:33Z (UTC) by Autobahn WebSockets Testsuite v0.5.6/v0.6.3.

Pass | Test case was executed and passed successfully.
Non-Strict | Test case was executed and passed non-strictly. A non-strict behavior is one that does not adhere to a SHOULD-behavior as described in the protocol specification or a well-defined, canonical behavior that appears to be desirable but left open in the protocol specification. An implementation with non-strict behavior is still conformant to the protocol specification.
Fail | Test case was executed and failed. An implementation which fails a test case - other than a performance/limits related one - is non-conforming to a MUST-behavior as described in the protocol specification.
Info | Informational test case which detects certain implementation behavior left unspecified by the spec but nevertheless potentially interesting to implementors.
Missing | Test case is missing, either because it was skipped via the test suite configuration or deactivated, i.e. because the implementation does not implement the tested feature or breaks during running the test case.

1 Framing | AutobahnPython/CPython
1.1 Text Messages
Case 1.1.1 | Missing
Case 1.1.2 | Missing
Case 1.1.3 | Missing
Case 1.1.4 | Missing
Case 1.1.5 | Missing
Case 1.1.6 | Missing
Case 1.1.7 | Missing
Case 1.1.8 | Missing
1 Framing | AutobahnPython/CPython
1.2 Binary Messages
Case 1.2.1 | Missing
Case 1.2.2 | Missing
Case 1.2.3 | Missing
Case 1.2.4 | Missing
Case 1.2.5 | Missing
Case 1.2.6 | Missing
Case 1.2.7 | Missing
Case 1.2.8 | Missing
2 Pings/Pongs | AutobahnPython/CPython
Case 2.1 | Missing
Case 2.2 | Missing
Case 2.3 | Missing
Case 2.4 | Missing
Case 2.5 | Missing
Case 2.6 | Missing
Case 2.7 | Missing
Case 2.8 | Missing
Case 2.9 | Missing
Case 2.10 | Missing
Case 2.11 | Missing
3 Reserved Bits | AutobahnPython/CPython
Case 3.1 | Missing
Case 3.2 | Missing
Case 3.3 | Missing
Case 3.4 | Missing
Case 3.5 | Missing
Case 3.6 | Missing
Case 3.7 | Missing
4 Opcodes | AutobahnPython/CPython
4.1 Non-control Opcodes
Case 4.1.1 | Missing
Case 4.1.2 | Missing
Case 4.1.3 | Missing
Case 4.1.4 | Missing
Case 4.1.5 | Missing
4 Opcodes | AutobahnPython/CPython
4.2 Control Opcodes
Case 4.2.1 | Missing
Case 4.2.2 | Missing
Case 4.2.3 | Missing
Case 4.2.4 | Missing
Case 4.2.5 | Missing
5 Fragmentation | AutobahnPython/CPython
Case 5.1 | Missing
Case 5.2 | Missing
Case 5.3 | Missing
Case 5.4 | Missing
Case 5.5 | Missing
Case 5.6 | Missing
Case 5.7 | Missing
Case 5.8 | Missing
Case 5.9 | Missing
Case 5.10 | Missing
Case 5.11 | Missing
Case 5.12 | Missing
Case 5.13 | Missing
Case 5.14 | Missing
Case 5.15 | Missing
Case 5.16 | Missing
Case 5.17 | Missing
Case 5.18 | Missing
Case 5.19 | Missing
Case 5.20 | Missing
6 UTF-8 Handling | AutobahnPython/CPython
6.1 Valid UTF-8 with zero payload fragments
Case 6.1.1 | Missing
Case 6.1.2 | Missing
Case 6.1.3 | Missing
6 UTF-8 Handling | AutobahnPython/CPython
6.2 Valid UTF-8 unfragmented, fragmented on code-points and within code-points
Case 6.2.1 | Missing
Case 6.2.2 | Missing
Case 6.2.3 | Missing
Case 6.2.4 | Missing
6 UTF-8 Handling | AutobahnPython/CPython
6.3 Invalid UTF-8 differently fragmented
Case 6.3.1 | Missing
Case 6.3.2 | Missing
6 UTF-8 Handling | AutobahnPython/CPython
6.4 Fail-fast on invalid UTF-8
Case 6.4.1 | Missing
Case 6.4.2 | Missing
Case 6.4.3 | Missing
Case 6.4.4 | Missing
6 UTF-8 Handling | AutobahnPython/CPython
6.5 Some valid UTF-8 sequences
Case 6.5.1 | Missing
Case 6.5.2 | Missing
Case 6.5.3 | Missing
Case 6.5.4 | Missing
Case 6.5.5 | Missing
6 UTF-8 Handling | AutobahnPython/CPython
6.6 All prefixes of a valid UTF-8 string that contains multi-byte code points
Case 6.6.1 | Missing
Case 6.6.2 | Missing
Case 6.6.3 | Missing
Case 6.6.4 | Missing
Case 6.6.5 | Missing
Case 6.6.6 | Missing
Case 6.6.7 | Missing
Case 6.6.8 | Missing
Case 6.6.9 | Missing
Case 6.6.10 | Missing
Case 6.6.11 | Missing
6 UTF-8 Handling | AutobahnPython/CPython
6.7 First possible sequence of a certain length
Case 6.7.1 | Missing
Case 6.7.2 | Missing
Case 6.7.3 | Missing
Case 6.7.4 | Missing
6 UTF-8 Handling | AutobahnPython/CPython
6.8 First possible sequence length 5/6 (invalid codepoints)
Case 6.8.1 | Missing
Case 6.8.2 | Missing
6 UTF-8 Handling | AutobahnPython/CPython
6.9 Last possible sequence of a certain length
Case 6.9.1 | Missing
Case 6.9.2 | Missing
Case 6.9.3 | Missing
Case 6.9.4 | Missing
6 UTF-8 Handling | AutobahnPython/CPython
6.10 Last possible sequence length 4/5/6 (invalid codepoints)
Case 6.10.1 | Missing
Case 6.10.2 | Missing
Case 6.10.3 | Missing
6 UTF-8 Handling | AutobahnPython/CPython
6.11 Other boundary conditions
Case 6.11.1 | Missing
Case 6.11.2 | Missing
Case 6.11.3 | Missing
Case 6.11.4 | Missing
Case 6.11.5 | Missing
6 UTF-8 Handling | AutobahnPython/CPython
6.12 Unexpected continuation bytes
Case 6.12.1 | Missing
Case 6.12.2 | Missing
Case 6.12.3 | Missing
Case 6.12.4 | Missing
Case 6.12.5 | Missing
Case 6.12.6 | Missing
Case 6.12.7 | Missing
Case 6.12.8 | Missing
6 UTF-8 Handling | AutobahnPython/CPython
6.13 Lonely start characters
Case 6.13.1 | Missing
Case 6.13.2 | Missing
Case 6.13.3 | Missing
Case 6.13.4 | Missing
Case 6.13.5 | Missing
6 UTF-8 Handling | AutobahnPython/CPython
6.14 Sequences with last continuation byte missing
Case 6.14.1 | Missing
Case 6.14.2 | Missing
Case 6.14.3 | Missing
Case 6.14.4 | Missing
Case 6.14.5 | Missing
Case 6.14.6 | Missing
Case 6.14.7 | Missing
Case 6.14.8 | Missing
Case 6.14.9 | Missing
Case 6.14.10 | Missing
6 UTF-8 Handling | AutobahnPython/CPython
6.15 Concatenation of incomplete sequences
Case 6.15.1 | Missing
6 UTF-8 Handling | AutobahnPython/CPython
6.16 Impossible bytes
Case 6.16.1 | Missing
Case 6.16.2 | Missing
Case 6.16.3 | Missing
6 UTF-8 Handling | AutobahnPython/CPython
6.17 Examples of an overlong ASCII character
Case 6.17.1 | Missing
Case 6.17.2 | Missing
Case 6.17.3 | Missing
Case 6.17.4 | Missing
Case 6.17.5 | Missing
6 UTF-8 Handling | AutobahnPython/CPython
6.18 Maximum overlong sequences
Case 6.18.1 | Missing
Case 6.18.2 | Missing
Case 6.18.3 | Missing
Case 6.18.4 | Missing
Case 6.18.5 | Missing
6 UTF-8 Handling | AutobahnPython/CPython
6.19 Overlong representation of the NUL character
Case 6.19.1 | Missing
Case 6.19.2 | Missing
Case 6.19.3 | Missing
Case 6.19.4 | Missing
Case 6.19.5 | Missing
6 UTF-8 Handling | AutobahnPython/CPython
6.20 Single UTF-16 surrogates
Case 6.20.1 | Missing
Case 6.20.2 | Missing
Case 6.20.3 | Missing
Case 6.20.4 | Missing
Case 6.20.5 | Missing
Case 6.20.6 | Missing
Case 6.20.7 | Missing
6 UTF-8 Handling | AutobahnPython/CPython
6.21 Paired UTF-16 surrogates
Case 6.21.1 | Missing
Case 6.21.2 | Missing
Case 6.21.3 | Missing
Case 6.21.4 | Missing
Case 6.21.5 | Missing
Case 6.21.6 | Missing
Case 6.21.7 | Missing
Case 6.21.8 | Missing
6 UTF-8 Handling | AutobahnPython/CPython
6.22 Non-character code points (valid UTF-8)
Case 6.22.1 | Missing
Case 6.22.2 | Missing
Case 6.22.3 | Missing
Case 6.22.4 | Missing
Case 6.22.5 | Missing
Case 6.22.6 | Missing
Case 6.22.7 | Missing
Case 6.22.8 | Missing
Case 6.22.9 | Missing
Case 6.22.10 | Missing
Case 6.22.11 | Missing
Case 6.22.12 | Missing
Case 6.22.13 | Missing
Case 6.22.14 | Missing
Case 6.22.15 | Missing
Case 6.22.16 | Missing
Case 6.22.17 | Missing
Case 6.22.18 | Missing
Case 6.22.19 | Missing
Case 6.22.20 | Missing
Case 6.22.21 | Missing
Case 6.22.22 | Missing
Case 6.22.23 | Missing
Case 6.22.24 | Missing
Case 6.22.25 | Missing
Case 6.22.26 | Missing
Case 6.22.27 | Missing
Case 6.22.28 | Missing
Case 6.22.29 | Missing
Case 6.22.30 | Missing
Case 6.22.31 | Missing
Case 6.22.32 | Missing
Case 6.22.33 | Missing
Case 6.22.34 | Missing
6 UTF-8 Handling | AutobahnPython/CPython
6.23 Unicode specials (i.e. replacement char)
Case 6.23.1 | Missing
Case 6.23.2 | Missing
Case 6.23.3 | Missing
Case 6.23.4 | Missing
Case 6.23.5 | Missing
Case 6.23.6 | Missing
Case 6.23.7 | Missing
7 Close Handling | AutobahnPython/CPython
7.1 Basic close behavior (fuzzer initiated)
Case 7.1.1 | Missing
Case 7.1.2 | Missing
Case 7.1.3 | Missing
Case 7.1.4 | Missing
Case 7.1.5 | Missing
Case 7.1.6 | Missing
7 Close Handling | AutobahnPython/CPython
7.3 Close frame structure: payload length (fuzzer initiated)
Case 7.3.1 | Missing
Case 7.3.2 | Missing
Case 7.3.3 | Missing
Case 7.3.4 | Missing
Case 7.3.5 | Missing
Case 7.3.6 | Missing
7 Close Handling | AutobahnPython/CPython
7.5 Close frame structure: payload value (fuzzer initiated)
Case 7.5.1 | Missing
7 Close Handling | AutobahnPython/CPython
7.7 Close frame structure: valid close codes (fuzzer initiated)
Case 7.7.1 | Missing
Case 7.7.2 | Missing
Case 7.7.3 | Missing
Case 7.7.4 | Missing
Case 7.7.5 | Missing
Case 7.7.6 | Missing
Case 7.7.7 | Missing
Case 7.7.8 | Missing
Case 7.7.9 | Missing
Case 7.7.10 | Missing
Case 7.7.11 | Missing
Case 7.7.12 | Missing
Case 7.7.13 | Missing
7 Close Handling | AutobahnPython/CPython
7.9 Close frame structure: invalid close codes (fuzzer initiated)
Case 7.9.1 | Missing
Case 7.9.2 | Missing
Case 7.9.3 | Missing
Case 7.9.4 | Missing
Case 7.9.5 | Missing
Case 7.9.6 | Missing
Case 7.9.7 | Missing
Case 7.9.8 | Missing
Case 7.9.9 | Missing
Case 7.9.10 | Missing
Case 7.9.11 | Missing
Case 7.9.12 | Missing
Case 7.9.13 | Missing
7 Close Handling | AutobahnPython/CPython
7.13 Informational close information (fuzzer initiated)
Case 7.13.1 | Missing
Case 7.13.2 | Missing
9 Limits/Performance | AutobahnPython/CPython
9.1 Text Message (increasing size)
Case 9.1.1 | Missing
Case 9.1.2 | Missing
Case 9.1.3 | Missing
Case 9.1.4 | Missing
Case 9.1.5 | Missing
Case 9.1.6 | Missing
9 Limits/Performance | AutobahnPython/CPython
9.2 Binary Message (increasing size)
Case 9.2.1 | Missing
Case 9.2.2 | Missing
Case 9.2.3 | Missing
Case 9.2.4 | Missing
Case 9.2.5 | Missing
Case 9.2.6 | Missing
9 Limits/Performance | AutobahnPython/CPython
9.3 Fragmented Text Message (fixed size, increasing fragment size)
Case 9.3.1 | Missing
Case 9.3.2 | Missing
Case 9.3.3 | Missing
Case 9.3.4 | Missing
Case 9.3.5 | Missing
Case 9.3.6 | Missing
Case 9.3.7 | Missing
Case 9.3.8 | Missing
Case 9.3.9 | Missing
9 Limits/Performance | AutobahnPython/CPython
9.4 Fragmented Binary Message (fixed size, increasing fragment size)
Case 9.4.1 | Missing
Case 9.4.2 | Missing
Case 9.4.3 | Missing
Case 9.4.4 | Missing
Case 9.4.5 | Missing
Case 9.4.6 | Missing
Case 9.4.7 | Missing
Case 9.4.8 | Missing
Case 9.4.9 | Missing
9 Limits/Performance | AutobahnPython/CPython
9.5 Text Message (fixed size, increasing chop size)
Case 9.5.1 | Missing
Case 9.5.2 | Missing
Case 9.5.3 | Missing
Case 9.5.4 | Missing
Case 9.5.5 | Missing
Case 9.5.6 | Missing
9 Limits/Performance | AutobahnPython/CPython
9.6 Binary Text Message (fixed size, increasing chop size)
Case 9.6.1 | Missing
Case 9.6.2 | Missing
Case 9.6.3 | Missing
Case 9.6.4 | Missing
Case 9.6.5 | Missing
Case 9.6.6 | Missing
9 Limits/Performance | AutobahnPython/CPython
9.7 Text Message Roundtrip Time (fixed number, increasing size)
Case 9.7.1 | Missing
Case 9.7.2 | Missing
Case 9.7.3 | Missing
Case 9.7.4 | Missing
Case 9.7.5 | Missing
Case 9.7.6 | Missing
9 Limits/Performance | AutobahnPython/CPython
9.8 Binary Message Roundtrip Time (fixed number, increasing size)
Case 9.8.1 | Missing
Case 9.8.2 | Missing
Case 9.8.3 | Missing
Case 9.8.4 | Missing
Case 9.8.5 | Missing
Case 9.8.6 | Missing
10 Misc | AutobahnPython/CPython
10.1 Auto-Fragmentation
Case 10.1.1 | Missing
12 WebSocket Compression | AutobahnPython/CPython
12.1 Large JSON data file (utf8, 200636 bytes)
Case 12.1.1 | Pass 270 ms [0.303/0.303] | 1000
Case 12.1.2 | Pass 280 ms [0.112/0.112] | 1000
Case 12.1.3 | Pass 290 ms [0.065/0.065] | 1000
Case 12.1.4 | Pass 320 ms [0.056/0.056] | 1000
Case 12.1.5 | Pass 440 ms [0.046/0.046] | 1000
Case 12.1.6 | Pass 590 ms [0.044/0.044] | 1000
Case 12.1.7 | Pass 850 ms [0.043/0.043] | 1000
Case 12.1.8 | Pass 1390 ms [0.042/0.042] | 1000
Case 12.1.9 | Pass 2440 ms [0.042/0.042] | 1000
Case 12.1.10 | Pass 4560 ms [0.042/0.042] | 1000
12 WebSocket Compression | AutobahnPython/CPython
12.2 Lena Picture, Bitmap 512x512 bw (binary, 263222 bytes)
Case 12.2.1 | Pass 270 ms [1.106/1.106] | 1000
Case 12.2.2 | Pass 290 ms [0.997/0.997] | 1000
Case 12.2.3 | Pass 360 ms [0.966/0.966] | 1000
Case 12.2.4 | Pass 520 ms [0.909/0.909] | 1000
Case 12.2.5 | Pass 950 ms [0.859/0.859] | 1000
Case 12.2.6 | Pass 1530 ms [0.851/0.851] | 1000
Case 12.2.7 | Pass 2830 ms [0.850/0.850] | 1000
Case 12.2.8 | Pass 5640 ms [0.851/0.851] | 1000
Case 12.2.9 | Pass 9170 ms [0.851/0.851] | 1000
Case 12.2.10 | Pass 18490 ms [0.850/0.850] | 1000
12 WebSocket Compression | AutobahnPython/CPython
12.3 Human readable text, Goethe's Faust I (German) (binary, 229647 bytes)
Case 12.3.1 | Pass 270 ms [0.727/0.727] | 1000
Case 12.3.2 | Pass 290 ms [0.535/0.535] | 1000
Case 12.3.3 | Pass 350 ms [0.470/0.470] | 1000
Case 12.3.4 | Pass 530 ms [0.413/0.413] | 1000
Case 12.3.5 | Pass 1100 ms [0.387/0.387] | 1000
Case 12.3.6 | Pass 1850 ms [0.381/0.381] | 1000
Case 12.3.7 | Pass 3320 ms [0.378/0.378] | 1000
Case 12.3.8 | Pass 6470 ms [0.377/0.377] | 1000
Case 12.3.9 | Pass 12310 ms [0.376/0.376] | 1000
Case 12.3.10 | Pass 24090 ms [0.376/0.376] | 1000
12 WebSocket Compression | AutobahnPython/CPython
12.4 Large HTML file (utf8, 384281 bytes)
Case 12.4.1 | Pass 270 ms [0.429/0.429] | 1000
Case 12.4.2 | Pass 280 ms [0.139/0.139] | 1000
Case 12.4.3 | Pass 280 ms [0.067/0.067] | 1000
Case 12.4.4 | Fail 90 ms | Fail
Case 12.4.5 | Fail 30 ms | Fail
Case 12.4.6 | Fail 20 ms | Fail
Case 12.4.7 | Fail 10 ms | Fail
Case 12.4.8 | Fail 10 ms | Fail
Case 12.4.9 | Fail 10 ms | Fail
Case 12.4.10 | Fail 20 ms | Fail
12 WebSocket Compression | AutobahnPython/CPython
12.5 A larger PDF (binary, 1042328 bytes)
Case 12.5.1 | Pass 270 ms [1.086/1.086] | 1000
Case 12.5.2 | Pass 290 ms [1.028/1.028] | 1000
Case 12.5.3 | Pass 350 ms [0.973/0.973] | 1000
Case 12.5.4 | Pass 450 ms [0.786/0.786] | 1000
Case 12.5.5 | Pass 790 ms [0.777/0.777] | 1000
Case 12.5.6 | Pass 1180 ms [0.768/0.768] | 1000
Case 12.5.7 | Pass 1960 ms [0.763/0.763] | 1000
Case 12.5.8 | Pass 3570 ms [0.761/0.761] | 1000
Case 12.5.9 | Pass 6770 ms [0.759/0.759] | 1000
Case 12.5.10 | Pass 13340 ms [0.759/0.759] | 1000

## Case 1.1.1

Up

Case Description
Send text message with payload 0.

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

## Case 1.1.2

Up

Case Description
Send text message message with payload of length 125.

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

## Case 1.1.3

Up

Case Description
Send text message message with payload of length 126.

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

## Case 1.1.4

Up

Case Description
Send text message message with payload of length 127.

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

## Case 1.1.5

Up

Case Description
Send text message message with payload of length 128.

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

## Case 1.1.6

Up

Case Description
Send text message message with payload of length 65535.

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

## Case 1.1.7

Up

Case Description
Send text message message with payload of length 65536.

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

## Case 1.1.8

Up

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

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

## Case 1.2.1

Up

Case Description
Send binary message with payload 0.

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

## Case 1.2.2

Up

Case Description
Send binary message message with payload of length 125.

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

## Case 1.2.3

Up

Case Description
Send binary message message with payload of length 126.

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

## Case 1.2.4

Up

Case Description
Send binary message message with payload of length 127.

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

## Case 1.2.5

Up

Case Description
Send binary message message with payload of length 128.

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

## Case 1.2.6

Up

Case Description
Send binary message message with payload of length 65535.

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

## Case 1.2.7

Up

Case Description
Send binary message message with payload of length 65536.

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

## Case 1.2.8

Up

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

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

## Case 2.1

Up

Case Description
Send ping without payload.

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

## Case 2.2

Up

Case Description
Send ping with small text payload.

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

## Case 2.3

Up

Case Description
Send ping with small binary (non UTF-8) payload.

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

## Case 2.4

Up

Case Description
Send ping with binary payload of 125 octets.

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

## Case 2.5

Up

Case Description
Send ping with binary payload of 126 octets.

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

## Case 2.6

Up

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

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

## Case 2.7

Up

Case Description
Send unsolicited pong without payload. Verify nothing is received. Clean close with normal code.

Case Expectation
Nothing.

## Case 2.8

Up

Case Description
Send unsolicited pong with payload. Verify nothing is received. Clean close with normal code.

Case Expectation
Nothing.

## Case 2.9

Up

Case Description
Send unsolicited pong with payload. Send ping with payload. Verify pong for ping is received.

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

## Case 2.10

Up

Case Description
Send 10 Pings with payload.

Case Expectation
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.

## Case 2.11

Up

Case Description
Send 10 Pings with payload. Send out octets in octet-wise chops.

Case Expectation
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.

## Case 3.1

Up

Case Description
Send small text message with RSV = 1.

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

## Case 3.2

Up

Case Description
Send small text message, then send again with RSV = 2, then send Ping.

Case Expectation
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 negoiated. The Pong is not received.

## Case 3.3

Up

Case Description
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.

Case Expectation
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 negoiated. The Pong is not received.

## Case 3.4

Up

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

Case Expectation
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 negoiated. The Pong is not received.

## Case 3.5

Up

Case Description
Send small binary message with RSV = 5.

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

## Case 3.6

Up

Case Description
Send Ping with RSV = 6.

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

## Case 3.7

Up

Case Description
Send Close with RSV = 7.

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

## Case 4.1.1

Up

Case Description
Send frame with reserved non-control Opcode = 3.

Case Expectation
The connection is failed immediately.

## Case 4.1.2

Up

Case Description
Send frame with reserved non-control Opcode = 4 and non-empty payload.

Case Expectation
The connection is failed immediately.

## Case 4.1.3

Up

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

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

## Case 4.1.4

Up

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

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

## Case 4.1.5

Up

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

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

## Case 4.2.1

Up

Case Description
Send frame with reserved control Opcode = 11.

Case Expectation
The connection is failed immediately.

## Case 4.2.2

Up

Case Description
Send frame with reserved control Opcode = 12 and non-empty payload.

Case Expectation
The connection is failed immediately.

## Case 4.2.3

Up

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

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

## Case 4.2.4

Up

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

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

## Case 4.2.5

Up

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

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

## Case 5.1

Up

Case Description
Send Ping fragmented into 2 fragments.

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

## Case 5.2

Up

Case Description
Send Pong fragmented into 2 fragments.

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

## Case 5.3

Up

Case Description
Send text Message fragmented into 2 fragments.

Case Expectation
Message is processed and echo'ed back to us.

## Case 5.4

Up

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

Case Expectation
Message is processed and echo'ed back to us.

## Case 5.5

Up

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

Case Expectation
Message is processed and echo'ed back to us.

## Case 5.6

Up

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

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

## Case 5.7

Up

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

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

## Case 5.8

Up

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

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

## Case 5.9

Up

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

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

## Case 5.10

Up

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

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

## Case 5.11

Up

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

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

## Case 5.12

Up

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

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

## Case 5.13

Up

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

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

## Case 5.14

Up

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

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

## Case 5.15

Up

Case Description
Send text Message fragmented into 2 fragments, then Continuation Frame with FIN = false where there is nothing to continue, then unfragmented Text Message, all sent in one chop.

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

## Case 5.16

Up

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

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

## Case 5.17

Up

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

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

## Case 5.18

Up

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

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

## Case 5.19

Up

Case Description
A fragmented text message is sent in multiple frames. After sending the first 2 frames of the text message, a Ping is sent. Then we wait 1s, then we send 2 more text fragments, another Ping and then the final text fragment. Everything is legal.

Case Expectation
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.

## Case 5.20

Up

Case Description
Same as Case 5.19, but send all frames with SYNC = True. Note, this does not change the octets sent in any way, only how the stream is chopped up on the wire.

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

## Case 6.1.1

Up

Case Description
Send text message of length 0.

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

## Case 6.1.2

Up

Case Description
Send fragmented text message, 3 fragments each of length 0.

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

## Case 6.1.3

Up

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

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

## Case 6.2.1

Up

Case Description
Send a valid UTF-8 text message in one fragment.
MESSAGE:
Hello-µ@ßöäüàá-UTF-8!!
48656c6c6f2dc2b540c39fc3b6c3a4c3bcc3a0c3a12d5554462d382121

Case Expectation
The message is echo'ed back to us.

## Case 6.2.2

Up

Case Description
Send a valid UTF-8 text message in two fragments, fragmented on UTF-8 code point boundary.
MESSAGE FRAGMENT 1:
Hello-µ@ßöä
48656c6c6f2dc2b540c39fc3b6c3a4
MESSAGE FRAGMENT 2:
üàá-UTF-8!!
c3bcc3a0c3a12d5554462d382121

Case Expectation
The message is echo'ed back to us.

## Case 6.2.3

Up

Case Description
Send a valid UTF-8 text message in fragments of 1 octet, resulting in frames ending on positions which are not code point ends.
MESSAGE:
Hello-µ@ßöäüàá-UTF-8!!
48656c6c6f2dc2b540c39fc3b6c3a4c3bcc3a0c3a12d5554462d382121

Case Expectation
The message is echo'ed back to us.

## Case 6.2.4

Up

Case Description
Send a valid UTF-8 text message in fragments of 1 octet, resulting in frames ending on positions which are not code point ends.
MESSAGE:
κόσμε
cebae1bdb9cf83cebcceb5

Case Expectation
The message is echo'ed back to us.

## Case 6.3.1

Up

Case Description
Send invalid UTF-8 text message unfragmented.
MESSAGE:
cebae1bdb9cf83cebcceb5eda080656469746564

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

## Case 6.3.2

Up

Case Description
Send invalid UTF-8 text message in fragments of 1 octet, resulting in frames ending on positions which are not code point ends.
MESSAGE:
cebae1bdb9cf83cebcceb5eda080656469746564

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

## Case 6.4.1

Up

Case Description
Send invalid UTF-8 text message in 3 fragments (frames). First frame payload is valid, then wait, then 2nd frame which contains the payload making the sequence invalid, then wait, then 3rd frame with rest. Note that PART1 and PART3 are valid UTF-8 in themselves, PART2 is a 0x110000 encoded as in the UTF-8 integer encoding scheme, but the codepoint is invalid (out of range).
MESSAGE PARTS:
PART1 = cebae1bdb9cf83cebcceb5
PART2 = f4908080
PART3 = 656469746564

Case Expectation
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.

## Case 6.4.2

Up

Case Description
Same as Case 6.4.1, but in 2nd frame, we send only up to and including the octet making the complete payload invalid.
MESSAGE PARTS:
PART1 = cebae1bdb9cf83cebcceb5f4
PART2 = 90
PART3 = 8080656469746564

Case Expectation
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.

## Case 6.4.3

Up

Case Description
Same as Case 6.4.1, but we send message not in 3 frames, but in 3 chops of the same message frame.
MESSAGE PARTS:
PART1 = cebae1bdb9cf83cebcceb5
PART2 = f4908080
PART3 = 656469746564

Case Expectation
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.

## Case 6.4.4

Up

Case Description
Same as Case 6.4.2, but we send message not in 3 frames, but in 3 chops of the same message frame.
MESSAGE PARTS:
PART1 = cebae1bdb9cf83cebcceb5f4
PART2 = 90
PART3 =

Case Expectation
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.

## Case 6.5.1

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0x68656c6c6f24776f726c64

Case Expectation
The message is echo'ed back to us.

## Case 6.5.2

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0x68656c6c6fc2a2776f726c64

Case Expectation
The message is echo'ed back to us.

## Case 6.5.3

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0x68656c6c6fe282ac776f726c64

Case Expectation
The message is echo'ed back to us.

## Case 6.5.4

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0x68656c6c6ff0a4ada2776f726c64

Case Expectation
The message is echo'ed back to us.

## Case 6.5.5

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xcebae1bdb9cf83cebcceb5

Case Expectation
The message is echo'ed back to us.

## Case 6.6.1

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xce

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

## Case 6.6.2

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xceba

Case Expectation
The message is echo'ed back to us.

## Case 6.6.3

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xcebae1

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

## Case 6.6.4

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xcebae1bd

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

## Case 6.6.5

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xcebae1bdb9

Case Expectation
The message is echo'ed back to us.

## Case 6.6.6

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xcebae1bdb9cf

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

## Case 6.6.7

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xcebae1bdb9cf83

Case Expectation
The message is echo'ed back to us.

## Case 6.6.8

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xcebae1bdb9cf83ce

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

## Case 6.6.9

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xcebae1bdb9cf83cebc

Case Expectation
The message is echo'ed back to us.

## Case 6.6.10

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xcebae1bdb9cf83cebcce

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

## Case 6.6.11

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xcebae1bdb9cf83cebcceb5

Case Expectation
The message is echo'ed back to us.

## Case 6.7.1

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0x00

Case Expectation
The message is echo'ed back to us.

## Case 6.7.2

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xc280

Case Expectation
The message is echo'ed back to us.

## Case 6.7.3

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xe0a080

Case Expectation
The message is echo'ed back to us.

## Case 6.7.4

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf0908080

Case Expectation
The message is echo'ed back to us.

## Case 6.8.1

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xf888808080

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

## Case 6.8.2

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xfc8480808080

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

## Case 6.9.1

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0x7f

Case Expectation
The message is echo'ed back to us.

## Case 6.9.2

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xdfbf

Case Expectation
The message is echo'ed back to us.

## Case 6.9.3

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xefbfbf

Case Expectation
The message is echo'ed back to us.

## Case 6.9.4

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf48fbfbf

Case Expectation
The message is echo'ed back to us.

## Case 6.10.1

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xf7bfbfbf

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

## Case 6.10.2

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xfbbfbfbfbf

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

## Case 6.10.3

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xfdbfbfbfbfbf

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

## Case 6.11.1

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xed9fbf

Case Expectation
The message is echo'ed back to us.

## Case 6.11.2

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xee8080

Case Expectation
The message is echo'ed back to us.

## Case 6.11.3

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xefbfbd

Case Expectation
The message is echo'ed back to us.

## Case 6.11.4

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf48fbfbf

Case Expectation
The message is echo'ed back to us.

## Case 6.11.5

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xf4908080

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

## Case 6.12.1

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0x80

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

## Case 6.12.2

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xbf

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

## Case 6.12.3

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0x80bf

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

## Case 6.12.4

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0x80bf80

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

## Case 6.12.5

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0x80bf80bf

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

## Case 6.12.6

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0x80bf80bf80

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

## Case 6.12.7

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0x80bf80bf80bf

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

## Case 6.12.8

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0x808182838485868788898a8b8c8d8e8f909192939495969798999a9b9c9d9e9fa0a1a2a3a4a5a6a7a8a9aaabacadaeafb0b1b2b3b4b5b6b7b8b9babbbcbdbe

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

## Case 6.13.1

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xc020c120c220c320c420c520c620c720c820c920ca20cb20cc20cd20ce20cf20d020d120d220d320d420d520d620d720d820d920da20db20dc20dd20de20

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

## Case 6.13.2

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xe020e120e220e320e420e520e620e720e820e920ea20eb20ec20ed20ee20

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

## Case 6.13.3

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xf020f120f220f320f420f520f620

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

## Case 6.13.4

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xf820f920fa20

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

## Case 6.13.5

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xfc20

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

## Case 6.14.1

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xc0

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

## Case 6.14.2

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xe080

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

## Case 6.14.3

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xf08080

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

## Case 6.14.4

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xf8808080

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

## Case 6.14.5

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xfc80808080

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

## Case 6.14.6

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xdf

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

## Case 6.14.7

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xefbf

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

## Case 6.14.8

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xf7bfbf

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

## Case 6.14.9

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xfbbfbfbf

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

## Case 6.14.10

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xfdbfbfbfbf

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

## Case 6.15.1

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xc0e080f08080f8808080fc80808080dfefbff7bfbffbbfbfbffdbfbfbfbf

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

## Case 6.16.1

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xfe

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

## Case 6.16.2

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xff

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

## Case 6.16.3

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xfefeffff

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

## Case 6.17.1

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xc0af

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

## Case 6.17.2

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xe080af

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

## Case 6.17.3

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xf08080af

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

## Case 6.17.4

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xf8808080af

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

## Case 6.17.5

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xfc80808080af

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

## Case 6.18.1

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xc1bf

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

## Case 6.18.2

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xe09fbf

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

## Case 6.18.3

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xf08fbfbf

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

## Case 6.18.4

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xf887bfbfbf

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

## Case 6.18.5

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xfc83bfbfbfbf

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

## Case 6.19.1

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xc080

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

## Case 6.19.2

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xe08080

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

## Case 6.19.3

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xf0808080

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

## Case 6.19.4

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xf880808080

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

## Case 6.19.5

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xfc8080808080

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

## Case 6.20.1

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xeda080

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

## Case 6.20.2

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xedadbf

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

## Case 6.20.3

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xedae80

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

## Case 6.20.4

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xedafbf

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

## Case 6.20.5

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xedb080

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

## Case 6.20.6

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xedbe80

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

## Case 6.20.7

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xedbfbf

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

## Case 6.21.1

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xeda080edb080

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

## Case 6.21.2

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xeda080edbfbf

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

## Case 6.21.3

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xedadbfedb080

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

## Case 6.21.4

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xedadbfedbfbf

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

## Case 6.21.5

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xedae80edb080

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

## Case 6.21.6

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xedae80edbfbf

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

## Case 6.21.7

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xedafbfedb080

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

## Case 6.21.8

Up

Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xedafbfedbfbf

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

## Case 6.22.1

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xefbfbe

Case Expectation
The message is echo'ed back to us.

## Case 6.22.2

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xefbfbf

Case Expectation
The message is echo'ed back to us.

## Case 6.22.3

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf09fbfbe

Case Expectation
The message is echo'ed back to us.

## Case 6.22.4

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf09fbfbf

Case Expectation
The message is echo'ed back to us.

## Case 6.22.5

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf0afbfbe

Case Expectation
The message is echo'ed back to us.

## Case 6.22.6

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf0afbfbf

Case Expectation
The message is echo'ed back to us.

## Case 6.22.7

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf0bfbfbe

Case Expectation
The message is echo'ed back to us.

## Case 6.22.8

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf0bfbfbf

Case Expectation
The message is echo'ed back to us.

## Case 6.22.9

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf18fbfbe

Case Expectation
The message is echo'ed back to us.

## Case 6.22.10

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf18fbfbf

Case Expectation
The message is echo'ed back to us.

## Case 6.22.11

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf19fbfbe

Case Expectation
The message is echo'ed back to us.

## Case 6.22.12

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf19fbfbf

Case Expectation
The message is echo'ed back to us.

## Case 6.22.13

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf1afbfbe

Case Expectation
The message is echo'ed back to us.

## Case 6.22.14

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf1afbfbf

Case Expectation
The message is echo'ed back to us.

## Case 6.22.15

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf1bfbfbe

Case Expectation
The message is echo'ed back to us.

## Case 6.22.16

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf1bfbfbf

Case Expectation
The message is echo'ed back to us.

## Case 6.22.17

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf28fbfbe

Case Expectation
The message is echo'ed back to us.

## Case 6.22.18

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf28fbfbf

Case Expectation
The message is echo'ed back to us.

## Case 6.22.19

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf29fbfbe

Case Expectation
The message is echo'ed back to us.

## Case 6.22.20

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf29fbfbf

Case Expectation
The message is echo'ed back to us.

## Case 6.22.21

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf2afbfbe

Case Expectation
The message is echo'ed back to us.

## Case 6.22.22

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf2afbfbf

Case Expectation
The message is echo'ed back to us.

## Case 6.22.23

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf2bfbfbe

Case Expectation
The message is echo'ed back to us.

## Case 6.22.24

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf2bfbfbf

Case Expectation
The message is echo'ed back to us.

## Case 6.22.25

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf38fbfbe

Case Expectation
The message is echo'ed back to us.

## Case 6.22.26

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf38fbfbf

Case Expectation
The message is echo'ed back to us.

## Case 6.22.27

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf39fbfbe

Case Expectation
The message is echo'ed back to us.

## Case 6.22.28

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf39fbfbf

Case Expectation
The message is echo'ed back to us.

## Case 6.22.29

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf3afbfbe

Case Expectation
The message is echo'ed back to us.

## Case 6.22.30

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf3afbfbf

Case Expectation
The message is echo'ed back to us.

## Case 6.22.31

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf3bfbfbe

Case Expectation
The message is echo'ed back to us.

## Case 6.22.32

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf3bfbfbf

Case Expectation
The message is echo'ed back to us.

## Case 6.22.33

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf48fbfbe

Case Expectation
The message is echo'ed back to us.

## Case 6.22.34

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xf48fbfbf

Case Expectation
The message is echo'ed back to us.

## Case 6.23.1

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xefbfb9

Case Expectation
The message is echo'ed back to us.

## Case 6.23.2

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xefbfba

Case Expectation
The message is echo'ed back to us.

## Case 6.23.3

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xefbfbb

Case Expectation
The message is echo'ed back to us.

## Case 6.23.4

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xefbfbc

Case Expectation
The message is echo'ed back to us.

## Case 6.23.5

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xefbfbd

Case Expectation
The message is echo'ed back to us.

## Case 6.23.6

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xefbfbe

Case Expectation
The message is echo'ed back to us.

## Case 6.23.7

Up

Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
Payload: 0xefbfbf

Case Expectation
The message is echo'ed back to us.

## Case 7.1.1

Up

Case Description
Send a message followed by a close frame

Case Expectation
Echoed message followed by clean close with normal code.

## Case 7.1.2

Up

Case Description
Send two close frames

Case Expectation
Clean close with normal code. Second close frame ignored.

## Case 7.1.3

Up

Case Description
Send a ping after close message

Case Expectation
Clean close with normal code, no pong.

## Case 7.1.4

Up

Case Description
Send text message after sending a close frame.

Case Expectation
Clean close with normal code. Text message ignored.

## Case 7.1.5

Up

Case Description
Send message fragment1 followed by close then fragment

Case Expectation
Clean close with normal code.

## Case 7.1.6

Up

Case Description
Send 256K message followed by close then a ping

Case Expectation
Case outcome depends on implimentation 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 asyncronous processing models) the close frame is processed first and the text message may not be recieved or may only be partially recieved.

## Case 7.3.1

Up

Case Description
Send a close frame with payload length 0 (no close code, no close reason)

Case Expectation
Clean close with normal code.

## Case 7.3.2

Up

Case Description
Send a close frame with payload length 1

Case Expectation
Clean close with protocol error or drop TCP.

## Case 7.3.3

Up

Case Description
Send a close frame with payload length 2 (regular close with a code)

Case Expectation
Clean close with normal code.

## Case 7.3.4

Up

Case Description
Send a close frame with close code and close reason

Case Expectation
Clean close with normal code.

## Case 7.3.5

Up

Case Description
Send a close frame with close code and close reason of maximum length (123)

Case Expectation
Clean close with normal code.

## Case 7.3.6

Up

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

Case Expectation
Clean close with protocol error code or dropped TCP connection.

## Case 7.5.1

Up

Case Description
Send a close frame with invalid UTF8 payload

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

## Case 7.7.1

Up

Case Description
Send close with valid close code 1000

Case Expectation
Clean close with normal or echoed code

## Case 7.7.2

Up

Case Description
Send close with valid close code 1001

Case Expectation
Clean close with normal or echoed code

## Case 7.7.3

Up

Case Description
Send close with valid close code 1002

Case Expectation
Clean close with normal or echoed code

## Case 7.7.4

Up

Case Description
Send close with valid close code 1003

Case Expectation
Clean close with normal or echoed code

## Case 7.7.5

Up

Case Description
Send close with valid close code 1007

Case Expectation
Clean close with normal or echoed code

## Case 7.7.6

Up

Case Description
Send close with valid close code 1008

Case Expectation
Clean close with normal or echoed code

## Case 7.7.7

Up

Case Description
Send close with valid close code 1009

Case Expectation
Clean close with normal or echoed code

## Case 7.7.8

Up

Case Description
Send close with valid close code 1010

Case Expectation
Clean close with normal or echoed code

## Case 7.7.9

Up

Case Description
Send close with valid close code 1011

Case Expectation
Clean close with normal or echoed code

## Case 7.7.10

Up

Case Description
Send close with valid close code 3000

Case Expectation
Clean close with normal or echoed code

## Case 7.7.11

Up

Case Description
Send close with valid close code 3999

Case Expectation
Clean close with normal or echoed code

## Case 7.7.12

Up

Case Description
Send close with valid close code 4000

Case Expectation
Clean close with normal or echoed code

## Case 7.7.13

Up

Case Description
Send close with valid close code 4999

Case Expectation
Clean close with normal or echoed code

## Case 7.9.1

Up

Case Description
Send close with invalid close code 0

Case Expectation
Clean close with protocol error code or drop TCP

## Case 7.9.2

Up

Case Description
Send close with invalid close code 999

Case Expectation
Clean close with protocol error code or drop TCP

## Case 7.9.3

Up

Case Description
Send close with invalid close code 1004

Case Expectation
Clean close with protocol error code or drop TCP

## Case 7.9.4

Up

Case Description
Send close with invalid close code 1005

Case Expectation
Clean close with protocol error code or drop TCP

## Case 7.9.5

Up

Case Description
Send close with invalid close code 1006

Case Expectation
Clean close with protocol error code or drop TCP

## Case 7.9.6

Up

Case Description
Send close with invalid close code 1012

Case Expectation
Clean close with protocol error code or drop TCP

## Case 7.9.7

Up

Case Description
Send close with invalid close code 1013

Case Expectation
Clean close with protocol error code or drop TCP

## Case 7.9.8

Up

Case Description
Send close with invalid close code 1014

Case Expectation
Clean close with protocol error code or drop TCP

## Case 7.9.9

Up

Case Description
Send close with invalid close code 1015

Case Expectation
Clean close with protocol error code or drop TCP

## Case 7.9.10

Up

Case Description
Send close with invalid close code 1016

Case Expectation
Clean close with protocol error code or drop TCP

## Case 7.9.11

Up

Case Description
Send close with invalid close code 1100

Case Expectation
Clean close with protocol error code or drop TCP

## Case 7.9.12

Up

Case Description
Send close with invalid close code 2000

Case Expectation
Clean close with protocol error code or drop TCP

## Case 7.9.13

Up

Case Description
Send close with invalid close code 2999

Case Expectation
Clean close with protocol error code or drop TCP

## Case 7.13.1

Up

Case Description
Send close with close code 5000

Case Expectation
Actual events are undefined by the spec.

## Case 7.13.2

Up

Case Description
Send close with close code 65536

Case Expectation
Actual events are undefined by the spec.

## Case 9.1.1

Up

Case Description
Send text message message with payload of length 64 * 2**10 (64k).

Case Expectation
Receive echo'ed text message (with payload as sent).

## Case 9.1.2

Up

Case Description
Send text message message with payload of length 256 * 2**10 (256k).

Case Expectation
Receive echo'ed text message (with payload as sent).

## Case 9.1.3

Up

Case Description
Send text message message with payload of length 1 * 2**20 (1M).

Case Expectation
Receive echo'ed text message (with payload as sent).

## Case 9.1.4

Up

Case Description
Send text message message with payload of length 4 * 2**20 (4M).

Case Expectation
Receive echo'ed text message (with payload as sent).

## Case 9.1.5

Up

Case Description
Send text message message with payload of length 8 * 2**20 (8M).

Case Expectation
Receive echo'ed text message (with payload as sent).

## Case 9.1.6

Up

Case Description
Send text message message with payload of length 16 * 2**20 (16M).

Case Expectation
Receive echo'ed text message (with payload as sent).

## Case 9.2.1

Up

Case Description
Send binary message message with payload of length 64 * 2**10 (64k).

Case Expectation
Receive echo'ed binary message (with payload as sent).

## Case 9.2.2

Up

Case Description
Send binary message message with payload of length 256 * 2**10 (256k).

Case Expectation
Receive echo'ed binary message (with payload as sent).

## Case 9.2.3

Up

Case Description
Send binary message message with payload of length 1 * 2**20 (1M).

Case Expectation
Receive echo'ed binary message (with payload as sent).

## Case 9.2.4

Up

Case Description
Send binary message message with payload of length 4 * 2**20 (4M).

Case Expectation
Receive echo'ed binary message (with payload as sent).

## Case 9.2.5

Up

Case Description
Send binary message message with payload of length 8 * 2**20 (16M).

Case Expectation
Receive echo'ed binary message (with payload as sent).

## Case 9.2.6

Up

Case Description
Send binary message message with payload of length 16 * 2**20 (16M).

Case Expectation
Receive echo'ed binary message (with payload as sent).

## Case 9.3.1

Up

Case Description
Send fragmented text message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 64.

Case Expectation
Receive echo'ed text message (with payload as sent).

## Case 9.3.2

Up

Case Description
Send fragmented text message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 256.

Case Expectation
Receive echo'ed text message (with payload as sent).

## Case 9.3.3

Up

Case Description
Send fragmented text message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 1k.

Case Expectation
Receive echo'ed text message (with payload as sent).

## Case 9.3.4

Up

Case Description
Send fragmented text message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 4k.

Case Expectation
Receive echo'ed text message (with payload as sent).

## Case 9.3.5

Up

Case Description
Send fragmented text message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 16k.

Case Expectation
Receive echo'ed text message (with payload as sent).

## Case 9.3.6

Up

Case Description
Send fragmented text message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 64k.

Case Expectation
Receive echo'ed text message (with payload as sent).

## Case 9.3.7

Up

Case Description
Send fragmented text message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 256k.

Case Expectation
Receive echo'ed text message (with payload as sent).

## Case 9.3.8

Up

Case Description
Send fragmented text message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 1M.

Case Expectation
Receive echo'ed text message (with payload as sent).

## Case 9.3.9

Up

Case Description
Send fragmented text message message with message payload of length 4 * 2**20 (8M). Sent out in fragments of 4M.

Case Expectation
Receive echo'ed text message (with payload as sent).

## Case 9.4.1

Up

Case Description
Send fragmented binary message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 64.

Case Expectation
Receive echo'ed binary message (with payload as sent).

## Case 9.4.2

Up

Case Description
Send fragmented binary message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 256.

Case Expectation
Receive echo'ed binary message (with payload as sent).

## Case 9.4.3

Up

Case Description
Send fragmented binary message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 1k.

Case Expectation
Receive echo'ed binary message (with payload as sent).

## Case 9.4.4

Up

Case Description
Send fragmented binary message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 4k.

Case Expectation
Receive echo'ed binary message (with payload as sent).

## Case 9.4.5

Up

Case Description
Send fragmented binary message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 16k.

Case Expectation
Receive echo'ed binary message (with payload as sent).

## Case 9.4.6

Up

Case Description
Send fragmented binary message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 64k.

Case Expectation
Receive echo'ed binary message (with payload as sent).

## Case 9.4.7

Up

Case Description
Send fragmented binary message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 256k.

Case Expectation
Receive echo'ed binary message (with payload as sent).

## Case 9.4.8

Up

Case Description
Send fragmented binary message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 1M.

Case Expectation
Receive echo'ed binary message (with payload as sent).

## Case 9.4.9

Up

Case Description
Send fragmented binary message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 4M.

Case Expectation
Receive echo'ed binary message (with payload as sent).

## Case 9.5.1

Up

Case Description
Send text message message with payload of length 1 * 2**20 (1M). Sent out data in chops of 64 octets.

Case Expectation
Receive echo'ed text message (with payload as sent).

## Case 9.5.2

Up

Case Description
Send text message message with payload of length 1 * 2**20 (1M). Sent out data in chops of 128 octets.

Case Expectation
Receive echo'ed text message (with payload as sent).

## Case 9.5.3

Up

Case Description
Send text message message with payload of length 1 * 2**20 (1M). Sent out data in chops of 256 octets.

Case Expectation
Receive echo'ed text message (with payload as sent).

## Case 9.5.4

Up

Case Description
Send text message message with payload of length 1 * 2**20 (1M). Sent out data in chops of 512 octets.

Case Expectation
Receive echo'ed text message (with payload as sent).

## Case 9.5.5

Up

Case Description
Send text message message with payload of length 1 * 2**20 (1M). Sent out data in chops of 1024 octets.

Case Expectation
Receive echo'ed text message (with payload as sent).

## Case 9.5.6

Up

Case Description
Send text message message with payload of length 1 * 2**20 (1M). Sent out data in chops of 2048 octets.

Case Expectation
Receive echo'ed text message (with payload as sent).

## Case 9.6.1

Up

Case Description
Send binary message message with payload of length 1 * 2**20 (1M). Sent out data in chops of 64 octets.

Case Expectation
Receive echo'ed binary message (with payload as sent).

## Case 9.6.2

Up

Case Description
Send binary message message with payload of length 1 * 2**20 (1M). Sent out data in chops of 128 octets.

Case Expectation
Receive echo'ed text message (with payload as sent).

## Case 9.6.3

Up

Case Description
Send binary message message with payload of length 1 * 2**20 (1M). Sent out data in chops of 256 octets.

Case Expectation
Receive echo'ed text message (with payload as sent).

## Case 9.6.4

Up

Case Description
Send binary message message with payload of length 1 * 2**20 (1M). Sent out data in chops of 512 octets.

Case Expectation
Receive echo'ed text message (with payload as sent).

## Case 9.6.5

Up

Case Description
Send binary message message with payload of length 1 * 2**20 (1M). Sent out data in chops of 1024 octets.

Case Expectation
Receive echo'ed text message (with payload as sent).

## Case 9.6.6

Up

Case Description
Send binary message message with payload of length 1 * 2**20 (1M). Sent out data in chops of 2048 octets.

Case Expectation
Receive echo'ed text message (with payload as sent).

## Case 9.7.1

Up

Case Description
Send 1000 text messages of payload size 0 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed text messages (with payload as sent). Timeout case after 60 secs.

## Case 9.7.2

Up

Case Description
Send 1000 text messages of payload size 16 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed text messages (with payload as sent). Timeout case after 60 secs.

## Case 9.7.3

Up

Case Description
Send 1000 text messages of payload size 64 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed text messages (with payload as sent). Timeout case after 60 secs.

## Case 9.7.4

Up

Case Description
Send 1000 text messages of payload size 256 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed text messages (with payload as sent). Timeout case after 120 secs.

## Case 9.7.5

Up

Case Description
Send 1000 text messages of payload size 1024 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed text messages (with payload as sent). Timeout case after 240 secs.

## Case 9.7.6

Up

Case Description
Send 1000 text messages of payload size 4096 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed text messages (with payload as sent). Timeout case after 480 secs.

## Case 9.8.1

Up

Case Description
Send 1000 binary messages of payload size 0 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed binary messages (with payload as sent). Timeout case after 60 secs.

## Case 9.8.2

Up

Case Description
Send 1000 binary messages of payload size 16 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed binary messages (with payload as sent). Timeout case after 60 secs.

## Case 9.8.3

Up

Case Description
Send 1000 binary messages of payload size 64 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed binary messages (with payload as sent). Timeout case after 60 secs.

## Case 9.8.4

Up

Case Description
Send 1000 binary messages of payload size 256 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed binary messages (with payload as sent). Timeout case after 120 secs.

## Case 9.8.5

Up

Case Description
Send 1000 binary messages of payload size 1024 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed binary messages (with payload as sent). Timeout case after 240 secs.

## Case 9.8.6

Up

Case Description
Send 1000 binary messages of payload size 4096 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed binary messages (with payload as sent). Timeout case after 480 secs.

## Case 10.1.1

Up

Case Description
Send text message with payload of length 65536 auto-fragmented with autoFragmentSize = 1300.

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

## Case 12.1.1

Up

Case Description
Send 1000 messages of payload size 16 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 60 secs.

## Case 12.1.2

Up

Case Description
Send 1000 messages of payload size 64 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 60 secs.

## Case 12.1.3

Up

Case Description
Send 1000 messages of payload size 256 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 120 secs.

## Case 12.1.4

Up

Case Description
Send 1000 messages of payload size 1024 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 240 secs.

## Case 12.1.5

Up

Case Description
Send 1000 messages of payload size 4096 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

## Case 12.1.6

Up

Case Description
Send 1000 messages of payload size 8192 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

## Case 12.1.7

Up

Case Description
Send 1000 messages of payload size 16384 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

## Case 12.1.8

Up

Case Description
Send 1000 messages of payload size 32768 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

## Case 12.1.9

Up

Case Description
Send 1000 messages of payload size 65536 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

## Case 12.1.10

Up

Case Description
Send 1000 messages of payload size 131072 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

## Case 12.2.1

Up

Case Description
Send 1000 messages of payload size 16 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 60 secs.

## Case 12.2.2

Up

Case Description
Send 1000 messages of payload size 64 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 60 secs.

## Case 12.2.3

Up

Case Description
Send 1000 messages of payload size 256 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 120 secs.

## Case 12.2.4

Up

Case Description
Send 1000 messages of payload size 1024 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 240 secs.

## Case 12.2.5

Up

Case Description
Send 1000 messages of payload size 4096 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

## Case 12.2.6

Up

Case Description
Send 1000 messages of payload size 8192 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

## Case 12.2.7

Up

Case Description
Send 1000 messages of payload size 16384 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

## Case 12.2.8

Up

Case Description
Send 1000 messages of payload size 32768 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

## Case 12.2.9

Up

Case Description
Send 1000 messages of payload size 65536 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

## Case 12.2.10

Up

Case Description
Send 1000 messages of payload size 131072 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

## Case 12.3.1

Up

Case Description
Send 1000 messages of payload size 16 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 60 secs.

## Case 12.3.2

Up

Case Description
Send 1000 messages of payload size 64 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 60 secs.

## Case 12.3.3

Up

Case Description
Send 1000 messages of payload size 256 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 120 secs.

## Case 12.3.4

Up

Case Description
Send 1000 messages of payload size 1024 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 240 secs.

## Case 12.3.5

Up

Case Description
Send 1000 messages of payload size 4096 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

## Case 12.3.6

Up

Case Description
Send 1000 messages of payload size 8192 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

## Case 12.3.7

Up

Case Description
Send 1000 messages of payload size 16384 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

## Case 12.3.8

Up

Case Description
Send 1000 messages of payload size 32768 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

## Case 12.3.9

Up

Case Description
Send 1000 messages of payload size 65536 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

## Case 12.3.10

Up

Case Description
Send 1000 messages of payload size 131072 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

## Case 12.4.1

Up

Case Description
Send 1000 messages of payload size 16 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 60 secs.

## Case 12.4.2

Up

Case Description
Send 1000 messages of payload size 64 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 60 secs.

## Case 12.4.3

Up

Case Description
Send 1000 messages of payload size 256 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 120 secs.

## Case 12.4.4

Up

Case Description
Send 1000 messages of payload size 1024 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 240 secs.

## Case 12.4.5

Up

Case Description
Send 1000 messages of payload size 4096 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

## Case 12.4.6

Up

Case Description
Send 1000 messages of payload size 8192 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

## Case 12.4.7

Up

Case Description
Send 1000 messages of payload size 16384 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

## Case 12.4.8

Up

Case Description
Send 1000 messages of payload size 32768 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

## Case 12.4.9

Up

Case Description
Send 1000 messages of payload size 65536 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

## Case 12.4.10

Up

Case Description
Send 1000 messages of payload size 131072 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

## Case 12.5.1

Up

Case Description
Send 1000 messages of payload size 16 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 60 secs.

## Case 12.5.2

Up

Case Description
Send 1000 messages of payload size 64 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 60 secs.

## Case 12.5.3

Up

Case Description
Send 1000 messages of payload size 256 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 120 secs.

## Case 12.5.4

Up

Case Description
Send 1000 messages of payload size 1024 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 240 secs.

## Case 12.5.5

Up

Case Description
Send 1000 messages of payload size 4096 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

## Case 12.5.6

Up

Case Description
Send 1000 messages of payload size 8192 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

## Case 12.5.7

Up

Case Description
Send 1000 messages of payload size 16384 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

## Case 12.5.8

Up

Case Description
Send 1000 messages of payload size 32768 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

## Case 12.5.9

Up

Case Description
Send 1000 messages of payload size 65536 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

## Case 12.5.10

Up

Case Description
Send 1000 messages of payload size 131072 to measure implementation/network RTT (round trip time) / latency.

Case Expectation
Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.