Summary report generated on 2011-12-19T02:27:42Z (UTC) by Autobahn WebSockets v0.4.10.
| 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 | WebSocket-Node Client v1.0.4 | |
| 1.1 Text Messages | ||
| Case 1.1.1 | Pass | 1000 |
| Case 1.1.2 | Pass | 1000 |
| Case 1.1.3 | Pass | 1000 |
| Case 1.1.4 | Pass | 1000 |
| Case 1.1.5 | Pass | 1000 |
| Case 1.1.6 | Pass | 1000 |
| Case 1.1.7 | Pass | 1000 |
| Case 1.1.8 | Pass | 1000 |
| 1 Framing | WebSocket-Node Client v1.0.4 | |
| 1.2 Binary Messages | ||
| Case 1.2.1 | Pass | 1000 |
| Case 1.2.2 | Pass | 1000 |
| Case 1.2.3 | Pass | 1000 |
| Case 1.2.4 | Pass | 1000 |
| Case 1.2.5 | Pass | 1000 |
| Case 1.2.6 | Pass | 1000 |
| Case 1.2.7 | Pass | 1000 |
| Case 1.2.8 | Pass | 1000 |
| 2 Pings/Pongs | WebSocket-Node Client v1.0.4 | |
| Case 2.1 | Pass | 1000 |
| Case 2.2 | Pass | 1000 |
| Case 2.3 | Pass | 1000 |
| Case 2.4 | Pass | 1000 |
| Case 2.5 | Pass | 1002 |
| Case 2.6 | Pass | 1000 |
| Case 2.7 | Pass | 1000 |
| Case 2.8 | Pass | 1000 |
| Case 2.9 | Pass | 1000 |
| Case 2.10 | Pass | 1000 |
| Case 2.11 | Pass | 1000 |
| 3 Reserved Bits | WebSocket-Node Client v1.0.4 | |
| Case 3.1 | Pass | 1002 |
| Case 3.2 | Pass | 1002 |
| Case 3.3 | Pass | 1002 |
| Case 3.4 | Pass | 1002 |
| Case 3.5 | Pass | 1002 |
| Case 3.6 | Pass | 1002 |
| Case 3.7 | Pass | 1002 |
| 4 Opcodes | WebSocket-Node Client v1.0.4 | |
| 4.1 Non-control Opcodes | ||
| Case 4.1.1 | Pass | 1002 |
| Case 4.1.2 | Pass | 1002 |
| Case 4.1.3 | Pass | 1002 |
| Case 4.1.4 | Pass | 1002 |
| Case 4.1.5 | Pass | 1002 |
| 4 Opcodes | WebSocket-Node Client v1.0.4 | |
| 4.2 Control Opcodes | ||
| Case 4.2.1 | Pass | 1002 |
| Case 4.2.2 | Pass | 1002 |
| Case 4.2.3 | Pass | 1002 |
| Case 4.2.4 | Pass | 1002 |
| Case 4.2.5 | Pass | 1002 |
| 5 Fragmentation | WebSocket-Node Client v1.0.4 | |
| Case 5.1 | Pass | 1002 |
| Case 5.2 | Pass | 1002 |
| Case 5.3 | Pass | 1000 |
| Case 5.4 | Pass | 1000 |
| Case 5.5 | Pass | 1000 |
| Case 5.6 | Pass | 1000 |
| Case 5.7 | Pass | 1000 |
| Case 5.8 | Pass | 1000 |
| Case 5.9 | Pass | 1002 |
| Case 5.10 | Pass | 1002 |
| Case 5.11 | Pass | 1002 |
| Case 5.12 | Pass | 1002 |
| Case 5.13 | Pass | 1002 |
| Case 5.14 | Pass | 1002 |
| Case 5.15 | Pass | 1002 |
| Case 5.16 | Pass | 1002 |
| Case 5.17 | Pass | 1002 |
| Case 5.18 | Pass | 1002 |
| Case 5.19 | Pass | 1000 |
| Case 5.20 | Pass | 1000 |
| 6 UTF-8 Handling | WebSocket-Node Client v1.0.4 | |
| 6.1 Valid UTF-8 with zero payload fragments | ||
| Case 6.1.1 | Pass | 1000 |
| Case 6.1.2 | Pass | 1000 |
| Case 6.1.3 | Pass | 1000 |
| 6 UTF-8 Handling | WebSocket-Node Client v1.0.4 | |
| 6.2 Valid UTF-8 unfragmented, fragmented on code-points and within code-points | ||
| Case 6.2.1 | Pass | 1000 |
| Case 6.2.2 | Pass | 1000 |
| Case 6.2.3 | Pass | 1000 |
| Case 6.2.4 | Pass | 1000 |
| 6 UTF-8 Handling | WebSocket-Node Client v1.0.4 | |
| 6.3 Invalid UTF-8 differently fragmented | ||
| Case 6.3.1 | Pass | 1007 |
| Case 6.3.2 | Pass | 1007 |
| 6 UTF-8 Handling | WebSocket-Node Client v1.0.4 | |
| 6.4 Fail-fast on invalid UTF-8 | ||
| Case 6.4.1 | Non-Strict | 1007 |
| Case 6.4.2 | Non-Strict | 1007 |
| Case 6.4.3 | Non-Strict | 1007 |
| Case 6.4.4 | Non-Strict | 1007 |
| 6 UTF-8 Handling | WebSocket-Node Client v1.0.4 | |
| 6.5 Some valid UTF-8 sequences | ||
| Case 6.5.1 | Pass | 1000 |
| 6 UTF-8 Handling | WebSocket-Node Client v1.0.4 | |
| 6.6 All prefixes of a valid UTF-8 string that contains multi-byte code points | ||
| Case 6.6.1 | Pass | 1007 |
| Case 6.6.2 | Pass | 1000 |
| Case 6.6.3 | Pass | 1007 |
| Case 6.6.4 | Pass | 1007 |
| Case 6.6.5 | Pass | 1000 |
| Case 6.6.6 | Pass | 1007 |
| Case 6.6.7 | Pass | 1000 |
| Case 6.6.8 | Pass | 1007 |
| Case 6.6.9 | Pass | 1000 |
| Case 6.6.10 | Pass | 1007 |
| Case 6.6.11 | Pass | 1000 |
| 6 UTF-8 Handling | WebSocket-Node Client v1.0.4 | |
| 6.7 First possible sequence of a certain length | ||
| Case 6.7.1 | Pass | 1000 |
| Case 6.7.2 | Pass | 1000 |
| Case 6.7.3 | Pass | 1000 |
| Case 6.7.4 | Fail | 1000 |
| 6 UTF-8 Handling | WebSocket-Node Client v1.0.4 | |
| 6.8 First possible sequence length 5/6 (invalid codepoints) | ||
| Case 6.8.1 | Pass | 1007 |
| Case 6.8.2 | Pass | 1007 |
| 6 UTF-8 Handling | WebSocket-Node Client v1.0.4 | |
| 6.9 Last possible sequence of a certain length | ||
| Case 6.9.1 | Pass | 1000 |
| Case 6.9.2 | Pass | 1000 |
| Case 6.9.3 | Pass | 1000 |
| Case 6.9.4 | Fail | 1000 |
| 6 UTF-8 Handling | WebSocket-Node Client v1.0.4 | |
| 6.10 Last possible sequence length 4/5/6 (invalid codepoints) | ||
| Case 6.10.1 | Pass | 1007 |
| Case 6.10.2 | Pass | 1007 |
| Case 6.10.3 | Pass | 1007 |
| 6 UTF-8 Handling | WebSocket-Node Client v1.0.4 | |
| 6.11 Other boundary conditions | ||
| Case 6.11.1 | Pass | 1000 |
| Case 6.11.2 | Pass | 1000 |
| Case 6.11.3 | Pass | 1000 |
| Case 6.11.4 | Fail | 1000 |
| Case 6.11.5 | Pass | 1007 |
| 6 UTF-8 Handling | WebSocket-Node Client v1.0.4 | |
| 6.12 Unexpected continuation bytes | ||
| Case 6.12.1 | Pass | 1007 |
| Case 6.12.2 | Pass | 1007 |
| Case 6.12.3 | Pass | 1007 |
| Case 6.12.4 | Pass | 1007 |
| Case 6.12.5 | Pass | 1007 |
| Case 6.12.6 | Pass | 1007 |
| Case 6.12.7 | Pass | 1007 |
| Case 6.12.8 | Pass | 1007 |
| 6 UTF-8 Handling | WebSocket-Node Client v1.0.4 | |
| 6.13 Lonely start characters | ||
| Case 6.13.1 | Pass | 1007 |
| Case 6.13.2 | Pass | 1007 |
| Case 6.13.3 | Pass | 1007 |
| Case 6.13.4 | Pass | 1007 |
| Case 6.13.5 | Pass | 1007 |
| 6 UTF-8 Handling | WebSocket-Node Client v1.0.4 | |
| 6.14 Sequences with last continuation byte missing | ||
| Case 6.14.1 | Pass | 1007 |
| Case 6.14.2 | Pass | 1007 |
| Case 6.14.3 | Pass | 1007 |
| Case 6.14.4 | Pass | 1007 |
| Case 6.14.5 | Pass | 1007 |
| Case 6.14.6 | Pass | 1007 |
| Case 6.14.7 | Pass | 1007 |
| Case 6.14.8 | Pass | 1007 |
| Case 6.14.9 | Pass | 1007 |
| Case 6.14.10 | Pass | 1007 |
| 6 UTF-8 Handling | WebSocket-Node Client v1.0.4 | |
| 6.15 Concatenation of incomplete sequences | ||
| Case 6.15.1 | Pass | 1007 |
| 6 UTF-8 Handling | WebSocket-Node Client v1.0.4 | |
| 6.16 Impossible bytes | ||
| Case 6.16.1 | Pass | 1007 |
| Case 6.16.2 | Pass | 1007 |
| Case 6.16.3 | Pass | 1007 |
| 6 UTF-8 Handling | WebSocket-Node Client v1.0.4 | |
| 6.17 Examples of an overlong ASCII character | ||
| Case 6.17.1 | Pass | 1007 |
| Case 6.17.2 | Pass | 1007 |
| Case 6.17.3 | Pass | 1007 |
| Case 6.17.4 | Pass | 1007 |
| Case 6.17.5 | Pass | 1007 |
| 6 UTF-8 Handling | WebSocket-Node Client v1.0.4 | |
| 6.18 Maximum overlong sequences | ||
| Case 6.18.1 | Pass | 1007 |
| Case 6.18.2 | Pass | 1007 |
| Case 6.18.3 | Pass | 1007 |
| Case 6.18.4 | Pass | 1007 |
| Case 6.18.5 | Pass | 1007 |
| 6 UTF-8 Handling | WebSocket-Node Client v1.0.4 | |
| 6.19 Overlong representation of the NUL character | ||
| Case 6.19.1 | Pass | 1007 |
| Case 6.19.2 | Pass | 1007 |
| Case 6.19.3 | Pass | 1007 |
| Case 6.19.4 | Pass | 1007 |
| Case 6.19.5 | Pass | 1007 |
| 6 UTF-8 Handling | WebSocket-Node Client v1.0.4 | |
| 6.20 Single UTF-16 surrogates | ||
| Case 6.20.1 | Pass | 1007 |
| Case 6.20.2 | Pass | 1007 |
| Case 6.20.3 | Pass | 1007 |
| Case 6.20.4 | Pass | 1007 |
| Case 6.20.5 | Pass | 1007 |
| Case 6.20.6 | Pass | 1007 |
| Case 6.20.7 | Pass | 1007 |
| 6 UTF-8 Handling | WebSocket-Node Client v1.0.4 | |
| 6.21 Paired UTF-16 surrogates | ||
| Case 6.21.1 | Pass | 1007 |
| Case 6.21.2 | Pass | 1007 |
| Case 6.21.3 | Pass | 1007 |
| Case 6.21.4 | Pass | 1007 |
| Case 6.21.5 | Pass | 1007 |
| Case 6.21.6 | Pass | 1007 |
| Case 6.21.7 | Pass | 1007 |
| Case 6.21.8 | Pass | 1007 |
| 6 UTF-8 Handling | WebSocket-Node Client v1.0.4 | |
| 6.22 Non-character code points (valid UTF-8) | ||
| Case 6.22.1 | Pass | 1000 |
| Case 6.22.2 | Pass | 1000 |
| Case 6.22.3 | Fail | 1000 |
| Case 6.22.4 | Fail | 1000 |
| Case 6.22.5 | Fail | 1000 |
| Case 6.22.6 | Fail | 1000 |
| Case 6.22.7 | Fail | 1000 |
| Case 6.22.8 | Fail | 1000 |
| Case 6.22.9 | Fail | 1000 |
| Case 6.22.10 | Fail | 1000 |
| Case 6.22.11 | Fail | 1000 |
| Case 6.22.12 | Fail | 1000 |
| Case 6.22.13 | Fail | 1000 |
| Case 6.22.14 | Fail | 1000 |
| Case 6.22.15 | Fail | 1000 |
| Case 6.22.16 | Fail | 1000 |
| Case 6.22.17 | Fail | 1000 |
| Case 6.22.18 | Fail | 1000 |
| Case 6.22.19 | Fail | 1000 |
| Case 6.22.20 | Fail | 1000 |
| Case 6.22.21 | Fail | 1000 |
| Case 6.22.22 | Fail | 1000 |
| Case 6.22.23 | Fail | 1000 |
| Case 6.22.24 | Fail | 1000 |
| Case 6.22.25 | Fail | 1000 |
| Case 6.22.26 | Fail | 1000 |
| Case 6.22.27 | Fail | 1000 |
| Case 6.22.28 | Fail | 1000 |
| Case 6.22.29 | Fail | 1000 |
| Case 6.22.30 | Fail | 1000 |
| Case 6.22.31 | Fail | 1000 |
| Case 6.22.32 | Fail | 1000 |
| Case 6.22.33 | Fail | 1000 |
| Case 6.22.34 | Fail | 1000 |
| 6 UTF-8 Handling | WebSocket-Node Client v1.0.4 | |
| 6.23 Unicode replacement character | ||
| Case 6.23.1 | Pass | 1000 |
| 7 Close Handling | WebSocket-Node Client v1.0.4 | |
| 7.1 Basic close behavior (fuzzer initiated) | ||
| Case 7.1.1 | Pass | 1000 |
| Case 7.1.2 | Pass | 1000 |
| Case 7.1.3 | Pass | 1000 |
| Case 7.1.4 | Pass | 1000 |
| Case 7.1.5 | Pass | 1000 |
| Case 7.1.6 | Info | None |
| 7 Close Handling | WebSocket-Node Client v1.0.4 | |
| 7.3 Close frame structure: payload length (fuzzer initiated) | ||
| Case 7.3.1 | Pass | 1000 |
| Case 7.3.2 | Pass | 1002 |
| Case 7.3.3 | Pass | 1000 |
| Case 7.3.4 | Pass | 1000 |
| Case 7.3.5 | Pass | 1000 |
| Case 7.3.6 | Pass | 1002 |
| 7 Close Handling | WebSocket-Node Client v1.0.4 | |
| 7.5 Close frame structure: payload value (fuzzer initiated) | ||
| Case 7.5.1 | Pass | 1007 |
| 7 Close Handling | WebSocket-Node Client v1.0.4 | |
| 7.7 Close frame structure: valid close codes (fuzzer initiated) | ||
| Case 7.7.1 | Pass | 1000 |
| Case 7.7.2 | Pass | 1000 |
| Case 7.7.3 | Pass | 1000 |
| Case 7.7.4 | Pass | 1000 |
| Case 7.7.5 | Pass | 1000 |
| Case 7.7.6 | Pass | 1000 |
| Case 7.7.7 | Pass | 1000 |
| Case 7.7.8 | Pass | 1000 |
| Case 7.7.9 | Pass | 1000 |
| Case 7.7.10 | Pass | 1000 |
| Case 7.7.11 | Pass | 1000 |
| Case 7.7.12 | Pass | 1000 |
| Case 7.7.13 | Pass | 1000 |
| 7 Close Handling | WebSocket-Node Client v1.0.4 | |
| 7.9 Close frame structure: invalid close codes (fuzzer initiated) | ||
| Case 7.9.1 | Pass | 1002 |
| Case 7.9.2 | Pass | 1002 |
| Case 7.9.3 | Pass | 1002 |
| Case 7.9.4 | Pass | 1002 |
| Case 7.9.5 | Pass | 1002 |
| Case 7.9.6 | Pass | 1002 |
| Case 7.9.7 | Pass | 1002 |
| Case 7.9.8 | Pass | 1002 |
| Case 7.9.9 | Pass | 1002 |
| Case 7.9.10 | Pass | 1002 |
| Case 7.9.11 | Pass | 1002 |
| Case 7.9.12 | Pass | 1002 |
| Case 7.9.13 | Pass | 1002 |
| 7 Close Handling | WebSocket-Node Client v1.0.4 | |
| 7.13 Informational close information (fuzzer initiated) | ||
| Case 7.13.1 | Info | 1002 |
| Case 7.13.2 | Info | 1002 |
| 9 Limits/Performance | WebSocket-Node Client v1.0.4 | |
| 9.1 Text Message (increasing size) | ||
| Case 9.1.1 | Pass 89 ms | 1000 |
| Case 9.1.2 | Pass 350 ms | 1000 |
| Case 9.1.3 | Pass 1363 ms | 1000 |
| Case 9.1.4 | Pass 5441 ms | 1000 |
| Case 9.1.5 | Pass 11054 ms | 1000 |
| Case 9.1.6 | Pass 21639 ms | 1000 |
| 9 Limits/Performance | WebSocket-Node Client v1.0.4 | |
| 9.2 Binary Message (increasing size) | ||
| Case 9.2.1 | Pass 45 ms | 1000 |
| Case 9.2.2 | Pass 174 ms | 1000 |
| Case 9.2.3 | Pass 710 ms | 1000 |
| Case 9.2.4 | Pass 2766 ms | 1000 |
| Case 9.2.5 | Pass 5288 ms | 1000 |
| Case 9.2.6 | Pass 10592 ms | 1000 |
| 9 Limits/Performance | WebSocket-Node Client v1.0.4 | |
| 9.3 Fragmented Text Message (fixed size, increasing fragment size) | ||
| Case 9.3.1 | Pass 7288 ms | 1000 |
| Case 9.3.2 | Pass 5975 ms | 1000 |
| Case 9.3.3 | Pass 5511 ms | 1000 |
| Case 9.3.4 | Pass 5596 ms | 1000 |
| Case 9.3.5 | Pass 5422 ms | 1000 |
| Case 9.3.6 | Pass 5324 ms | 1000 |
| Case 9.3.7 | Pass 5321 ms | 1000 |
| Case 9.3.8 | Pass 5388 ms | 1000 |
| Case 9.3.9 | Pass 5373 ms | 1000 |
| 9 Limits/Performance | WebSocket-Node Client v1.0.4 | |
| 9.4 Fragmented Binary Message (fixed size, increasing fragment size) | ||
| Case 9.4.1 | Pass 4358 ms | 1000 |
| Case 9.4.2 | Pass 3102 ms | 1000 |
| Case 9.4.3 | Pass 2849 ms | 1000 |
| Case 9.4.4 | Pass 2577 ms | 1000 |
| Case 9.4.5 | Pass 2596 ms | 1000 |
| Case 9.4.6 | Pass 2569 ms | 1000 |
| Case 9.4.7 | Pass 2557 ms | 1000 |
| Case 9.4.8 | Pass 2561 ms | 1000 |
| Case 9.4.9 | Pass 2574 ms | 1000 |
| 9 Limits/Performance | WebSocket-Node Client v1.0.4 | |
| 9.5 Text Message (fixed size, increasing chop size) | ||
| Case 9.5.1 | Pass 3131 ms | 1000 |
| Case 9.5.2 | Pass 2268 ms | 1000 |
| Case 9.5.3 | Pass 2080 ms | 1000 |
| Case 9.5.4 | Pass 1577 ms | 1000 |
| Case 9.5.5 | Pass 1474 ms | 1000 |
| Case 9.5.6 | Pass 1446 ms | 1000 |
| 9 Limits/Performance | WebSocket-Node Client v1.0.4 | |
| 9.6 Binary Text Message (fixed size, increasing chop size) | ||
| Case 9.6.1 | Pass 2439 ms | 1000 |
| Case 9.6.2 | Pass 1642 ms | 1000 |
| Case 9.6.3 | Pass 1099 ms | 1000 |
| Case 9.6.4 | Pass 910 ms | 1000 |
| Case 9.6.5 | Pass 775 ms | 1000 |
| Case 9.6.6 | Pass 729 ms | 1000 |
| 9 Limits/Performance | WebSocket-Node Client v1.0.4 | |
| 9.7 Text Message Roundtrip Time (fixed number, increasing size) | ||
| Case 9.7.1 | Pass 292 ms | 1000 |
| Case 9.7.2 | Pass 370 ms | 1000 |
| Case 9.7.3 | Pass 414 ms | 1000 |
| Case 9.7.4 | Pass 715 ms | 1000 |
| Case 9.7.5 | Pass 1820 ms | 1000 |
| Case 9.7.6 | Pass 6309 ms | 1000 |
| 9 Limits/Performance | WebSocket-Node Client v1.0.4 | |
| 9.8 Binary Message Roundtrip Time (fixed number, increasing size) | ||
| Case 9.8.1 | Pass 281 ms | 1000 |
| Case 9.8.2 | Pass 317 ms | 1000 |
| Case 9.8.3 | Pass 347 ms | 1000 |
| Case 9.8.4 | Pass 498 ms | 1000 |
| Case 9.8.5 | Pass 1092 ms | 1000 |
| Case 9.8.6 | Pass 3362 ms | 1000 |
| 10 Autobahn Protocol Options | WebSocket-Node Client v1.0.4 | |
| 10.1 Auto-Fragmentation | ||
| Case 10.1.1 | Pass | 1000 |
Case Description
Send text message with payload 0.
Case Expectation
Receive echo'ed text message (with empty payload). Clean close with normal code.
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 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 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 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 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 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 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 Description
Send binary message with payload 0.
Case Expectation
Receive echo'ed binary message (with empty payload). Clean close with normal code.
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 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 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 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 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 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 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 Description
Send ping without payload.
Case Expectation
Pong (with empty payload) is sent in reply to Ping. Clean close with normal code.
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 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 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 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 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 Description
Send unsolicited pong without payload. Verify nothing is received. Clean close with normal code.
Case Expectation
Nothing.
Case Description
Send unsolicited pong with payload. Verify nothing is received. Clean close with normal code.
Case Expectation
Nothing.
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 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 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 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 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 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 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 Description
Send small binary message with RSV = 5.
Case Expectation
The connection is failed immediately, since RSV must be 0.
Case Description
Send Ping with RSV = 6.
Case Expectation
The connection is failed immediately, since RSV must be 0.
Case Description
Send Close with RSV = 7.
Case Expectation
The connection is failed immediately, since RSV must be 0.
Case Description
Send frame with reserved non-control Opcode = 3.
Case Expectation
The connection is failed immediately.
Case Description
Send frame with reserved non-control Opcode = 4 and non-empty payload.
Case Expectation
The connection is failed immediately.
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 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 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 Description
Send frame with reserved control Opcode = 11.
Case Expectation
The connection is failed immediately.
Case Description
Send frame with reserved control Opcode = 12 and non-empty payload.
Case Expectation
The connection is failed immediately.
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 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 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 Description
Send Ping fragmented into 2 fragments.
Case Expectation
Connection is failed immediately, since control message MUST NOT be fragmented.
Case Description
Send Pong fragmented into 2 fragments.
Case Expectation
Connection is failed immediately, since control message MUST NOT be fragmented.
Case Description
Send text Message fragmented into 2 fragments.
Case Expectation
Message is processed and echo'ed back to us.
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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 Description
Send text message of length 0.
Case Expectation
A message is echo'ed back to us (with empty payload).
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 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 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 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 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 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 Description
Send invalid UTF-8 text message unfragmented.
MESSAGE:
Îºá½¹ÏƒÎ¼Îµí €edited
cebae1bdb9cf83cebcceb5eda080656469746564
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
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:
Îºá½¹ÏƒÎ¼Îµí €edited
cebae1bdb9cf83cebcceb5eda080656469746564
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
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 0x11000 encoded as in the UTF-8 integer encoding scheme, but the codepoint is invalid (out of range).
MESSAGE PARTS:
PART1 = κόσμε (cebae1bdb9cf83cebcceb5)
PART2 = ô€€ (f4908080)
PART3 = edited (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 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 = €€edited (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 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 = edited (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 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 Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
κόσμε
cebae1bdb9cf83cebcceb5
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
Î
ce
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
κ
ceba
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
뼇
cebae1
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
κá½
cebae1bd
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
κό
cebae1bdb9
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
κόÏ
cebae1bdb9cf
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
κόσ
cebae1bdb9cf83
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
κόσÎ
cebae1bdb9cf83ce
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
κόσμ
cebae1bdb9cf83cebc
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
κόσμÎ
cebae1bdb9cf83cebcce
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
κόσμε
cebae1bdb9cf83cebcceb5
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
00
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
€
c280
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
à €
e0a080
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
ð€€
f0908080
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
øˆ€€€
f888808080
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
ü„€€€€
fc8480808080
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
7f
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
ß¿
dfbf
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
ï¿¿
efbfbf
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
ô¿¿
f48fbfbf
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
÷¿¿¿
f7bfbfbf
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
û¿¿¿¿
fbbfbfbfbf
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
ý¿¿¿¿¿
fdbfbfbfbfbf
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
퟿
ed9fbf
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:

ee8080
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
�
efbfbd
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
ô¿¿
f48fbfbf
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
ô€€
f4908080
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
€
80
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
¿
bf
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
€¿
80bf
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
€¿€
80bf80
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
€¿€¿
80bf80bf
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
€¿€¿€
80bf80bf80
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
€¿€¿€¿
80bf80bf80bf
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
€‚ƒ„…†‡ˆ‰Š‹ŒŽ‘’“”•–—˜™š›œžŸ ¡¢£¤¥¦§¨©ª«¬®¯°±²³´µ¶·¸¹º»¼½¾
808182838485868788898a8b8c8d8e8f909192939495969798999a9b9c9d9e9fa0a1a2a3a4a5a6a7a8a9aaabacadaeafb0b1b2b3b4b5b6b7b8b9babbbcbdbe
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
À Á Â Ã Ä Å Æ Ç È É Ê Ë Ì Í Î Ï Ð Ñ Ò Ó Ô Õ Ö × Ø Ù Ú Û Ü Ý Þ
c020c120c220c320c420c520c620c720c820c920ca20cb20cc20cd20ce20cf20d020d120d220d320d420d520d620d720d820d920da20db20dc20dd20de20
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
à á â ã ä å æ ç è é ê ë ì í î
e020e120e220e320e420e520e620e720e820e920ea20eb20ec20ed20ee20
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
ð ñ ò ó ô õ ö
f020f120f220f320f420f520f620
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
ø ù ú
f820f920fa20
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
ü
fc20
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
À
c0
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
à€
e080
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
ð€€
f08080
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
ø€€€
f8808080
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
ü€€€€
fc80808080
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
ß
df
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
ï¿
efbf
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
÷¿¿
f7bfbf
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
û¿¿¿
fbbfbfbf
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
ý¿¿¿¿
fdbfbfbfbf
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
Àà€ð€€ø€€€ü€€€€ßï¿÷¿¿û¿¿¿ý¿¿¿¿
c0e080f08080f8808080fc80808080dfefbff7bfbffbbfbfbffdbfbfbfbf
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
þ
fe
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
ÿ
ff
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
þþÿÿ
fefeffff
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
À¯
c0af
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
à€¯
e080af
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
ð€€¯
f08080af
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
ø€€€¯
f8808080af
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
ü€€€€¯
fc80808080af
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
Á¿
c1bf
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
àŸ¿
e09fbf
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
ð¿¿
f08fbfbf
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
ø‡¿¿¿
f887bfbfbf
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
üƒ¿¿¿¿
fc83bfbfbfbf
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
À€
c080
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
à€€
e08080
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
ð€€€
f0808080
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
ø€€€€
f880808080
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
ü€€€€€
fc8080808080
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
í €
eda080
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
í¿
edadbf
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
í®€
edae80
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
í¯¿
edafbf
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
í°€
edb080
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
í¾€
edbe80
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
í¿¿
edbfbf
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
í €í°€
eda080edb080
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
í €í¿¿
eda080edbfbf
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
í¿í°€
edadbfedb080
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
í¿í¿¿
edadbfedbfbf
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
󰀀
edae80edb080
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
󰏿
edae80edbfbf
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
􏰀
edafbfedb080
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
􏿿
edafbfedbfbf
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
￾
efbfbe
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
ï¿¿
efbfbf
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
🿾
f09fbfbe
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
🿿
f09fbfbf
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
𯿾
f0afbfbe
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
𯿿
f0afbfbf
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
ð¿¿¾
f0bfbfbe
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
ð¿¿¿
f0bfbfbf
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
ñ¿¾
f18fbfbe
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
ñ¿¿
f18fbfbf
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
񟿾
f19fbfbe
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
񟿿
f19fbfbf
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
񯿾
f1afbfbe
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
񯿿
f1afbfbf
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
ñ¿¿¾
f1bfbfbe
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
ñ¿¿¿
f1bfbfbf
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
ò¿¾
f28fbfbe
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
ò¿¿
f28fbfbf
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
򟿾
f29fbfbe
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
òŸ¿¿
f29fbfbf
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
򯿾
f2afbfbe
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
򯿿
f2afbfbf
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
ò¿¿¾
f2bfbfbe
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
ò¿¿¿
f2bfbfbf
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
ó¿¾
f38fbfbe
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
ó¿¿
f38fbfbf
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
󟿾
f39fbfbe
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
óŸ¿¿
f39fbfbf
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
󯿾
f3afbfbe
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
󯿿
f3afbfbf
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
ó¿¿¾
f3bfbfbe
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
ó¿¿¿
f3bfbfbf
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
ô¿¾
f48fbfbe
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
ô¿¿
f48fbfbf
Case Expectation
The message is echo'ed back to us.
Case Description
Send a text message with payload which is valid UTF-8 in one fragment.
MESSAGE:
�
efbfbd
Case Expectation
The message is echo'ed back to us.
Case Description
Send a message followed by a close frame
Case Expectation
Echoed message followed by clean close with normal code.
Case Description
Send two close frames
Case Expectation
Clean close with normal code. Second close frame ignored.
Case Description
Send a ping after close message
Case Expectation
Clean close with normal code, no pong.
Case Description
Send text message after sending a close frame.
Case Expectation
Clean close with normal code. Text message ignored.
Case Description
Send message fragment1 followed by close then fragment
Case Expectation
Clean close with normal code.
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 Description
Send a close frame with payload length 0 (no close code, no close reason)
Case Expectation
Clean close with normal code.
Case Description
Send a close frame with payload length 1
Case Expectation
Clean close with protocol error or drop TCP.
Case Description
Send a close frame with payload length 2 (regular close with a code)
Case Expectation
Clean close with normal code.
Case Description
Send a close frame with close code and close reason
Case Expectation
Clean close with normal code.
Case Description
Send a close frame with close code and close reason of maximum length (123)
Case Expectation
Clean close with normal code.
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 Description
Send a close frame with invalid UTF8 payload
Case Expectation
Clean close with protocol error or invalid utf8 code or dropped TCP.
Case Description
Send close with valid close code 1000
Case Expectation
Clean close with normal or echoed code
Case Description
Send close with valid close code 1001
Case Expectation
Clean close with normal or echoed code
Case Description
Send close with valid close code 1002
Case Expectation
Clean close with normal or echoed code
Case Description
Send close with valid close code 1003
Case Expectation
Clean close with normal or echoed code
Case Description
Send close with valid close code 1007
Case Expectation
Clean close with normal or echoed code
Case Description
Send close with valid close code 1008
Case Expectation
Clean close with normal or echoed code
Case Description
Send close with valid close code 1009
Case Expectation
Clean close with normal or echoed code
Case Description
Send close with valid close code 1010
Case Expectation
Clean close with normal or echoed code
Case Description
Send close with valid close code 1011
Case Expectation
Clean close with normal or echoed code
Case Description
Send close with valid close code 3000
Case Expectation
Clean close with normal or echoed code
Case Description
Send close with valid close code 3999
Case Expectation
Clean close with normal or echoed code
Case Description
Send close with valid close code 4000
Case Expectation
Clean close with normal or echoed code
Case Description
Send close with valid close code 4999
Case Expectation
Clean close with normal or echoed code
Case Description
Send close with invalid close code 0
Case Expectation
Clean close with protocol error code or drop TCP
Case Description
Send close with invalid close code 999
Case Expectation
Clean close with protocol error code or drop TCP
Case Description
Send close with invalid close code 1004
Case Expectation
Clean close with protocol error code or drop TCP
Case Description
Send close with invalid close code 1005
Case Expectation
Clean close with protocol error code or drop TCP
Case Description
Send close with invalid close code 1006
Case Expectation
Clean close with protocol error code or drop TCP
Case Description
Send close with invalid close code 1012
Case Expectation
Clean close with protocol error code or drop TCP
Case Description
Send close with invalid close code 1013
Case Expectation
Clean close with protocol error code or drop TCP
Case Description
Send close with invalid close code 1014
Case Expectation
Clean close with protocol error code or drop TCP
Case Description
Send close with invalid close code 1015
Case Expectation
Clean close with protocol error code or drop TCP
Case Description
Send close with invalid close code 1016
Case Expectation
Clean close with protocol error code or drop TCP
Case Description
Send close with invalid close code 1100
Case Expectation
Clean close with protocol error code or drop TCP
Case Description
Send close with invalid close code 2000
Case Expectation
Clean close with protocol error code or drop TCP
Case Description
Send close with invalid close code 2999
Case Expectation
Clean close with protocol error code or drop TCP
Case Description
Send close with close code 5000
Case Expectation
Actual events are undefined by the spec.
Case Description
Send close with close code 65536
Case Expectation
Actual events are undefined by the spec.
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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 Description
Send text message with payload of length 65536 and autoFragmentSize = 1300.
Case Expectation
Receive echo'ed text message (with payload as sent and transmitted frame counts as expected). Clean close with normal code.