Toggle Details

Autobahn WebSockets Testsuite Report
Autobahn WebSockets

Summary report generated on 2013-12-29T02:11:35Z (UTC) by Autobahn WebSockets Testsuite v0.5.2/v0.5.9.

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 JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
1.1 Text Messages
Case 1.1.1 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 1.1.2 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 1.1.3 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 1.1.4 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 1.1.5 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 1.1.6 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 1.1.7 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 1.1.8 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
1 Framing JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
1.2 Binary Messages
Case 1.2.1 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 1.2.2 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 1.2.3 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 1.2.4 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 1.2.5 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 1.2.6 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 1.2.7 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 1.2.8 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
2 Pings/Pongs JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
Case 2.1 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 2.2 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 2.3 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 2.4 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 2.5 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 2.6 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 2.7 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 2.8 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 2.9 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 2.10 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 2.11 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
3 Reserved Bits JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
Case 3.1 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 3.2 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 3.3 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 3.4 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 3.5 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 3.6 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 3.7 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
4 Opcodes JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
4.1 Non-control Opcodes
Case 4.1.1 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 4.1.2 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 4.1.3 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 4.1.4 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 4.1.5 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
4 Opcodes JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
4.2 Control Opcodes
Case 4.2.1 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 4.2.2 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 4.2.3 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 4.2.4 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 4.2.5 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
5 Fragmentation JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
Case 5.1 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 5.2 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 5.3 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 5.4 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 5.5 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 5.6 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 5.7 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 5.8 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 5.9 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 5.10 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 5.11 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 5.12 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 5.13 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 5.14 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 5.15 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 5.16 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 5.17 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 5.18 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 5.19 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 5.20 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
6 UTF-8 Handling JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
6.1 Valid UTF-8 with zero payload fragments
Case 6.1.1 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 6.1.2 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 6.1.3 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
6 UTF-8 Handling JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
6.2 Valid UTF-8 unfragmented, fragmented on code-points and within code-points
Case 6.2.1 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 6.2.2 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 6.2.3 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 6.2.4 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
6 UTF-8 Handling JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
6.3 Invalid UTF-8 differently fragmented
Case 6.3.1 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.3.2 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
6 UTF-8 Handling JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
6.4 Fail-fast on invalid UTF-8
Case 6.4.1 Non-Strict1007 Non-Strict1007 Non-Strict1007 Non-Strict1007 Non-Strict1007 Non-Strict1007 Non-Strict1007 Non-Strict1007 Non-Strict1007
Case 6.4.2 Non-Strict1007 Non-Strict1007 Non-Strict1007 Non-Strict1007 Non-Strict1007 Non-Strict1007 Non-Strict1007 Non-Strict1007 Non-Strict1007
Case 6.4.3 Non-Strict1007 Non-Strict1007 Non-Strict1007 Non-Strict1007 Non-Strict1007 Non-Strict1007 Non-Strict1007 Non-Strict1007 Non-Strict1007
Case 6.4.4 Non-Strict1007 Non-Strict1007 Non-Strict1007 Non-Strict1007 Non-Strict1007 Non-Strict1007 Non-Strict1007 Non-Strict1007 Non-Strict1007
6 UTF-8 Handling JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
6.5 Some valid UTF-8 sequences
Case 6.5.1 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
6 UTF-8 Handling JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
6.6 All prefixes of a valid UTF-8 string that contains multi-byte code points
Case 6.6.1 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.6.2 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 6.6.3 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.6.4 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.6.5 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 6.6.6 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.6.7 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 6.6.8 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.6.9 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 6.6.10 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.6.11 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
6 UTF-8 Handling JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
6.7 First possible sequence of a certain length
Case 6.7.1 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 6.7.2 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 6.7.3 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 6.7.4 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
6 UTF-8 Handling JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
6.8 First possible sequence length 5/6 (invalid codepoints)
Case 6.8.1 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.8.2 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
6 UTF-8 Handling JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
6.9 Last possible sequence of a certain length
Case 6.9.1 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 6.9.2 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 6.9.3 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 6.9.4 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
6 UTF-8 Handling JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
6.10 Last possible sequence length 4/5/6 (invalid codepoints)
Case 6.10.1 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.10.2 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.10.3 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
6 UTF-8 Handling JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
6.11 Other boundary conditions
Case 6.11.1 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 6.11.2 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 6.11.3 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 6.11.4 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.11.5 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
6 UTF-8 Handling JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
6.12 Unexpected continuation bytes
Case 6.12.1 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.12.2 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.12.3 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.12.4 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.12.5 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.12.6 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.12.7 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.12.8 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
6 UTF-8 Handling JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
6.13 Lonely start characters
Case 6.13.1 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.13.2 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.13.3 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.13.4 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.13.5 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
6 UTF-8 Handling JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
6.14 Sequences with last continuation byte missing
Case 6.14.1 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.14.2 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.14.3 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.14.4 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.14.5 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.14.6 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.14.7 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.14.8 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.14.9 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.14.10 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
6 UTF-8 Handling JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
6.15 Concatenation of incomplete sequences
Case 6.15.1 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
6 UTF-8 Handling JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
6.16 Impossible bytes
Case 6.16.1 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.16.2 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.16.3 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
6 UTF-8 Handling JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
6.17 Examples of an overlong ASCII character
Case 6.17.1 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.17.2 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.17.3 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.17.4 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.17.5 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
6 UTF-8 Handling JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
6.18 Maximum overlong sequences
Case 6.18.1 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.18.2 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.18.3 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.18.4 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.18.5 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
6 UTF-8 Handling JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
6.19 Overlong representation of the NUL character
Case 6.19.1 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.19.2 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.19.3 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.19.4 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.19.5 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
6 UTF-8 Handling JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
6.20 Single UTF-16 surrogates
Case 6.20.1 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.20.2 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.20.3 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.20.4 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.20.5 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.20.6 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.20.7 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
6 UTF-8 Handling JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
6.21 Paired UTF-16 surrogates
Case 6.21.1 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.21.2 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.21.3 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.21.4 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.21.5 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.21.6 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.21.7 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 6.21.8 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
6 UTF-8 Handling JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
6.22 Non-character code points (valid UTF-8)
Case 6.22.1 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 6.22.2 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 6.22.3 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.4 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.5 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.6 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.7 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.8 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.9 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.10 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.11 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.12 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.13 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.14 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.15 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.16 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.17 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.18 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.19 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.20 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.21 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.22 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.23 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.24 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.25 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.26 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.27 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.28 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.29 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.30 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.31 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.32 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.33 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
Case 6.22.34 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Fail1001 Fail1001 Pass1000
6 UTF-8 Handling JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
6.23 Unicode replacement character
Case 6.23.1 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
7 Close Handling JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
7.1 Basic close behavior (fuzzer initiated)
Case 7.1.1 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 7.1.2 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 7.1.3 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 7.1.4 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 7.1.5 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 7.1.6 Info1000 Info1000 Info1000 Info1000 Info1000 Info1000 Info1000 Info1000 Info1000
7 Close Handling JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
7.3 Close frame structure: payload length (fuzzer initiated)
Case 7.3.1 PassNone PassNone PassNone PassNone PassNone PassNone PassNone PassNone PassNone
Case 7.3.2 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 7.3.3 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 7.3.4 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 7.3.5 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 7.3.6 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
7 Close Handling JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
7.5 Close frame structure: payload value (fuzzer initiated)
Case 7.5.1 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
7 Close Handling JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
7.7 Close frame structure: valid close codes (fuzzer initiated)
Case 7.7.1 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000
Case 7.7.2 Pass1001 Pass1001 Pass1001 Pass1001 Pass1001 Pass1001 Pass1001 Pass1001 Pass1001
Case 7.7.3 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 7.7.4 Pass1003 Pass1003 Pass1003 Pass1003 Pass1003 Pass1003 Pass1003 Pass1003 Pass1003
Case 7.7.5 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007 Pass1007
Case 7.7.6 Pass1008 Pass1008 Pass1008 Pass1008 Pass1008 Pass1008 Pass1008 Pass1008 Pass1008
Case 7.7.7 Pass1009 Pass1009 Pass1009 Pass1009 Pass1009 Pass1009 Pass1009 Pass1009 Pass1009
Case 7.7.8 Pass1010 Pass1010 Pass1010 Pass1010 Pass1010 Pass1010 Pass1010 Pass1010 Pass1010
Case 7.7.9 Pass1011 Pass1011 Pass1011 Pass1011 Pass1011 Pass1011 Pass1011 Pass1011 Pass1011
Case 7.7.10 Pass3000 Pass3000 Pass3000 Pass3000 Pass3000 Pass3000 Pass3000 Pass3000 Pass3000
Case 7.7.11 Pass3999 Pass3999 Pass3999 Pass3999 Pass3999 Pass3999 Pass3999 Pass3999 Pass3999
Case 7.7.12 Pass4000 Pass4000 Pass4000 Pass4000 Pass4000 Pass4000 Pass4000 Pass4000 Pass4000
Case 7.7.13 Pass4999 Pass4999 Pass4999 Pass4999 Pass4999 Pass4999 Pass4999 Pass4999 Pass4999
7 Close Handling JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
7.9 Close frame structure: invalid close codes (fuzzer initiated)
Case 7.9.1 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 7.9.2 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 7.9.3 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 7.9.4 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 7.9.5 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 7.9.6 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 7.9.7 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 7.9.8 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 7.9.9 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 7.9.10 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 7.9.11 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 7.9.12 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
Case 7.9.13 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002 Pass1002
7 Close Handling JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
7.13 Informational close information (fuzzer initiated)
Case 7.13.1 Info1002 Info1002 Info1002 Info1002 Info1002 Info1002 Info1002 Info1002 Info1002
Case 7.13.2 Info1002 Info1002 Info1002 Info1002 Info1002 Info1002 Info1002 Info1002 Info1002
9 Limits/Performance JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
9.1 Text Message (increasing size)
Case 9.1.1 Pass
104 ms
1000 Pass
72 ms
1000 Pass
83 ms
1000 Pass
68 ms
1000 Pass
72 ms
1000 Pass
47 ms
1000 Pass
44 ms
1000 Pass
55 ms
1000 Pass
45 ms
1000
Case 9.1.2 Pass
246 ms
1000 Pass
201 ms
1000 Pass
231 ms
1000 Pass
189 ms
1000 Pass
252 ms
1000 Pass
162 ms
1000 Pass
164 ms
1000 Pass
181 ms
1000 Pass
167 ms
1000
Case 9.1.3 Pass
967 ms
1000 Pass
788 ms
1000 Pass
790 ms
1000 Pass
789 ms
1000 Pass
902 ms
1000 Pass
620 ms
1000 Pass
618 ms
1000 Pass
633 ms
1000 Pass
710 ms
1000
Case 9.1.4 Pass
6211 ms
1000 Pass
4124 ms
1000 Pass
3013 ms
1000 Pass
2951 ms
1000 Pass
3725 ms
1000 Pass
2473 ms
1000 Pass
2448 ms
1000 Pass
2299 ms
1000 Pass
2542 ms
1000
Case 9.1.5 Pass
8013 ms
1000 Pass
6540 ms
1000 Pass
5974 ms
1000 Pass
5818 ms
1000 Pass
7603 ms
1000 Pass
4840 ms
1000 Pass
4973 ms
1000 Pass
4753 ms
1000 Pass
4993 ms
1000
Case 9.1.6 Pass
19753 ms
1000 Pass
15683 ms
1000 Pass
12011 ms
1000 Pass
11530 ms
1000 Pass
14283 ms
1000 Pass
9769 ms
1000 Pass
9468 ms
1000 Pass
9588 ms
1000 Pass
9886 ms
1000
9 Limits/Performance JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
9.2 Binary Message (increasing size)
Case 9.2.1 Pass
61 ms
1000 Pass
64 ms
1000 Pass
60 ms
1000 Pass
57 ms
1000 Pass
66 ms
1000 Pass
19 ms
1000 Pass
17 ms
1000 Pass
17 ms
1000 Pass
17 ms
1000
Case 9.2.2 Pass
123 ms
1000 Pass
135 ms
1000 Pass
109 ms
1000 Pass
111 ms
1000 Pass
116 ms
1000 Pass
67 ms
1000 Pass
75 ms
1000 Pass
65 ms
1000 Pass
64 ms
1000
Case 9.2.3 Pass
548 ms
1000 Pass
462 ms
1000 Pass
520 ms
1000 Pass
354 ms
1000 Pass
473 ms
1000 Pass
236 ms
1000 Pass
236 ms
1000 Pass
213 ms
1000 Pass
243 ms
1000
Case 9.2.4 Pass
1836 ms
1000 Pass
1498 ms
1000 Pass
1601 ms
1000 Pass
1428 ms
1000 Pass
1548 ms
1000 Pass
893 ms
1000 Pass
898 ms
1000 Pass
811 ms
1000 Pass
923 ms
1000
Case 9.2.5 Pass
4365 ms
1000 Pass
2994 ms
1000 Pass
2739 ms
1000 Pass
2891 ms
1000 Pass
3295 ms
1000 Pass
1758 ms
1000 Pass
1786 ms
1000 Pass
1651 ms
1000 Pass
1911 ms
1000
Case 9.2.6 Pass
8017 ms
1000 Pass
7118 ms
1000 Pass
5448 ms
1000 Pass
6000 ms
1000 Pass
6697 ms
1000 Pass
3606 ms
1000 Pass
3634 ms
1000 Pass
3408 ms
1000 Pass
3678 ms
1000
9 Limits/Performance JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
9.3 Fragmented Text Message (fixed size, increasing fragment size)
Case 9.3.1 Pass
13993 ms
1000 Pass
12313 ms
1000 Pass
4333 ms
1000 Pass
3789 ms
1000 Pass
5201 ms
1000 Pass
3582 ms
1000 Pass
4614 ms
1000 Pass
3320 ms
1000 Pass
3688 ms
1000
Case 9.3.2 Pass
5893 ms
1000 Pass
5373 ms
1000 Pass
3340 ms
1000 Pass
3319 ms
1000 Pass
4179 ms
1000 Pass
2748 ms
1000 Pass
3307 ms
1000 Pass
2602 ms
1000 Pass
2764 ms
1000
Case 9.3.3 Pass
4537 ms
1000 Pass
3807 ms
1000 Pass
3076 ms
1000 Pass
3169 ms
1000 Pass
3545 ms
1000 Pass
2551 ms
1000 Pass
2632 ms
1000 Pass
2435 ms
1000 Pass
2625 ms
1000
Case 9.3.4 Pass
3812 ms
1000 Pass
3102 ms
1000 Pass
3006 ms
1000 Pass
2917 ms
1000 Pass
3456 ms
1000 Pass
2512 ms
1000 Pass
2453 ms
1000 Pass
2645 ms
1000 Pass
2544 ms
1000
Case 9.3.5 Pass
3716 ms
1000 Pass
3126 ms
1000 Pass
3146 ms
1000 Pass
3236 ms
1000 Pass
3474 ms
1000 Pass
2498 ms
1000 Pass
2446 ms
1000 Pass
2603 ms
1000 Pass
2526 ms
1000
Case 9.3.6 Pass
3962 ms
1000 Pass
3160 ms
1000 Pass
3105 ms
1000 Pass
3155 ms
1000 Pass
3541 ms
1000 Pass
2478 ms
1000 Pass
2546 ms
1000 Pass
2598 ms
1000 Pass
2519 ms
1000
Case 9.3.7 Pass
3586 ms
1000 Pass
3326 ms
1000 Pass
3012 ms
1000 Pass
3201 ms
1000 Pass
3614 ms
1000 Pass
2518 ms
1000 Pass
2495 ms
1000 Pass
2261 ms
1000 Pass
2477 ms
1000
Case 9.3.8 Pass
3603 ms
1000 Pass
3179 ms
1000 Pass
2993 ms
1000 Pass
2981 ms
1000 Pass
3435 ms
1000 Pass
2470 ms
1000 Pass
2328 ms
1000 Pass
2277 ms
1000 Pass
2512 ms
1000
Case 9.3.9 Pass
3815 ms
1000 Pass
3050 ms
1000 Pass
3467 ms
1000 Pass
3466 ms
1000 Pass
4047 ms
1000 Pass
2427 ms
1000 Pass
2483 ms
1000 Pass
2520 ms
1000 Pass
2540 ms
1000
9 Limits/Performance JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
9.4 Fragmented Binary Message (fixed size, increasing fragment size)
Case 9.4.1 Pass
8048 ms
1000 Pass
7782 ms
1000 Pass
2357 ms
1000 Pass
2253 ms
1000 Pass
2724 ms
1000 Pass
1932 ms
1000 Pass
3696 ms
1000 Pass
2095 ms
1000 Pass
1896 ms
1000
Case 9.4.2 Pass
4988 ms
1000 Pass
3156 ms
1000 Pass
1552 ms
1000 Pass
1455 ms
1000 Pass
1930 ms
1000 Pass
1067 ms
1000 Pass
1630 ms
1000 Pass
1094 ms
1000 Pass
1192 ms
1000
Case 9.4.3 Pass
2528 ms
1000 Pass
1985 ms
1000 Pass
1303 ms
1000 Pass
1263 ms
1000 Pass
1625 ms
1000 Pass
824 ms
1000 Pass
1059 ms
1000 Pass
838 ms
1000 Pass
938 ms
1000
Case 9.4.4 Pass
2016 ms
1000 Pass
1809 ms
1000 Pass
1267 ms
1000 Pass
1233 ms
1000 Pass
1491 ms
1000 Pass
795 ms
1000 Pass
928 ms
1000 Pass
792 ms
1000 Pass
903 ms
1000
Case 9.4.5 Pass
1738 ms
1000 Pass
1474 ms
1000 Pass
1239 ms
1000 Pass
1206 ms
1000 Pass
1470 ms
1000 Pass
766 ms
1000 Pass
922 ms
1000 Pass
752 ms
1000 Pass
869 ms
1000
Case 9.4.6 Pass
2155 ms
1000 Pass
1496 ms
1000 Pass
1247 ms
1000 Pass
1213 ms
1000 Pass
1467 ms
1000 Pass
750 ms
1000 Pass
882 ms
1000 Pass
746 ms
1000 Pass
872 ms
1000
Case 9.4.7 Pass
2083 ms
1000 Pass
1483 ms
1000 Pass
1218 ms
1000 Pass
1215 ms
1000 Pass
1383 ms
1000 Pass
751 ms
1000 Pass
837 ms
1000 Pass
791 ms
1000 Pass
870 ms
1000
Case 9.4.8 Pass
1649 ms
1000 Pass
1604 ms
1000 Pass
1255 ms
1000 Pass
1208 ms
1000 Pass
1504 ms
1000 Pass
744 ms
1000 Pass
834 ms
1000 Pass
798 ms
1000 Pass
872 ms
1000
Case 9.4.9 Pass
1677 ms
1000 Pass
1424 ms
1000 Pass
1207 ms
1000 Pass
1217 ms
1000 Pass
1390 ms
1000 Pass
761 ms
1000 Pass
826 ms
1000 Pass
753 ms
1000 Pass
862 ms
1000
9 Limits/Performance JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
9.5 Text Message (fixed size, increasing chop size)
Case 9.5.1 Pass
2174 ms
1000 Pass
1904 ms
1000 Pass
1764 ms
1000 Pass
1908 ms
1000 Pass
2051 ms
1000 Pass
1468 ms
1000 Pass
1959 ms
1000 Pass
1344 ms
1000 Pass
1618 ms
1000
Case 9.5.2 Pass
1445 ms
1000 Pass
1326 ms
1000 Pass
1253 ms
1000 Pass
1335 ms
1000 Pass
1429 ms
1000 Pass
967 ms
1000 Pass
1183 ms
1000 Pass
975 ms
1000 Pass
1102 ms
1000
Case 9.5.3 Pass
1143 ms
1000 Pass
990 ms
1000 Pass
969 ms
1000 Pass
1054 ms
1000 Pass
1237 ms
1000 Pass
776 ms
1000 Pass
813 ms
1000 Pass
776 ms
1000 Pass
862 ms
1000
Case 9.5.4 Pass
1027 ms
1000 Pass
852 ms
1000 Pass
844 ms
1000 Pass
909 ms
1000 Pass
1037 ms
1000 Pass
674 ms
1000 Pass
701 ms
1000 Pass
690 ms
1000 Pass
765 ms
1000
Case 9.5.5 Pass
973 ms
1000 Pass
795 ms
1000 Pass
744 ms
1000 Pass
870 ms
1000 Pass
954 ms
1000 Pass
627 ms
1000 Pass
654 ms
1000 Pass
637 ms
1000 Pass
715 ms
1000
Case 9.5.6 Pass
904 ms
1000 Pass
778 ms
1000 Pass
780 ms
1000 Pass
837 ms
1000 Pass
950 ms
1000 Pass
593 ms
1000 Pass
641 ms
1000 Pass
600 ms
1000 Pass
676 ms
1000
9 Limits/Performance JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
9.6 Binary Text Message (fixed size, increasing chop size)
Case 9.6.1 Pass
1494 ms
1000 Pass
1173 ms
1000 Pass
1375 ms
1000 Pass
1461 ms
1000 Pass
1567 ms
1000 Pass
1003 ms
1000 Pass
1141 ms
1000 Pass
1069 ms
1000 Pass
1196 ms
1000
Case 9.6.2 Pass
898 ms
1000 Pass
858 ms
1000 Pass
790 ms
1000 Pass
876 ms
1000 Pass
959 ms
1000 Pass
607 ms
1000 Pass
638 ms
1000 Pass
602 ms
1000 Pass
708 ms
1000
Case 9.6.3 Pass
666 ms
1000 Pass
637 ms
1000 Pass
552 ms
1000 Pass
606 ms
1000 Pass
673 ms
1000 Pass
419 ms
1000 Pass
492 ms
1000 Pass
401 ms
1000 Pass
463 ms
1000
Case 9.6.4 Pass
566 ms
1000 Pass
449 ms
1000 Pass
437 ms
1000 Pass
501 ms
1000 Pass
519 ms
1000 Pass
322 ms
1000 Pass
351 ms
1000 Pass
307 ms
1000 Pass
355 ms
1000
Case 9.6.5 Pass
494 ms
1000 Pass
398 ms
1000 Pass
334 ms
1000 Pass
417 ms
1000 Pass
449 ms
1000 Pass
284 ms
1000 Pass
287 ms
1000 Pass
266 ms
1000 Pass
295 ms
1000
Case 9.6.6 Pass
444 ms
1000 Pass
384 ms
1000 Pass
315 ms
1000 Pass
369 ms
1000 Pass
375 ms
1000 Pass
247 ms
1000 Pass
259 ms
1000 Pass
245 ms
1000 Pass
270 ms
1000
9 Limits/Performance JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
9.7 Text Message Roundtrip Time (fixed number, increasing size)
Case 9.7.1 Pass
767 ms
1000 Pass
1322 ms
1000 Pass
612 ms
1000 Pass
342 ms
1000 Pass
293 ms
1000 Pass
222 ms
1000 Pass
619 ms
1000 Pass
499 ms
1000 Pass
266 ms
1000
Case 9.7.2 Pass
854 ms
1000 Pass
1066 ms
1000 Pass
660 ms
1000 Pass
394 ms
1000 Pass
404 ms
1000 Pass
266 ms
1000 Pass
703 ms
1000 Pass
535 ms
1000 Pass
310 ms
1000
Case 9.7.3 Pass
922 ms
1000 Pass
1481 ms
1000 Pass
878 ms
1000 Pass
437 ms
1000 Pass
449 ms
1000 Pass
399 ms
1000 Pass
969 ms
1000 Pass
591 ms
1000 Pass
363 ms
1000
Case 9.7.4 Pass
1258 ms
1000 Pass
1579 ms
1000 Pass
1496 ms
1000 Pass
747 ms
1000 Pass
751 ms
1000 Pass
915 ms
1000 Pass
1283 ms
1000 Pass
669 ms
1000 Pass
599 ms
1000
Case 9.7.5 Pass
2402 ms
1000 Pass
3880 ms
1000 Pass
3131 ms
1000 Pass
1712 ms
1000 Pass
1858 ms
1000 Pass
2074 ms
1000 Pass
2298 ms
1000 Pass
1375 ms
1000 Pass
1247 ms
1000
Case 9.7.6 Pass
6438 ms
1000 Pass
9303 ms
1000 Pass
9433 ms
1000 Pass
5137 ms
1000 Pass
5539 ms
1000 Pass
3292 ms
1000 Pass
5622 ms
1000 Pass
3529 ms
1000 Pass
3582 ms
1000
9 Limits/Performance JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
9.8 Binary Message Roundtrip Time (fixed number, increasing size)
Case 9.8.1 Pass
546 ms
1000 Pass
811 ms
1000 Pass
573 ms
1000 Pass
373 ms
1000 Pass
265 ms
1000 Pass
335 ms
1000 Pass
612 ms
1000 Pass
411 ms
1000 Pass
237 ms
1000
Case 9.8.2 Pass
595 ms
1000 Pass
516 ms
1000 Pass
602 ms
1000 Pass
382 ms
1000 Pass
305 ms
1000 Pass
488 ms
1000 Pass
564 ms
1000 Pass
379 ms
1000 Pass
230 ms
1000
Case 9.8.3 Pass
634 ms
1000 Pass
1124 ms
1000 Pass
776 ms
1000 Pass
451 ms
1000 Pass
322 ms
1000 Pass
543 ms
1000 Pass
696 ms
1000 Pass
559 ms
1000 Pass
277 ms
1000
Case 9.8.4 Pass
845 ms
1000 Pass
816 ms
1000 Pass
989 ms
1000 Pass
537 ms
1000 Pass
510 ms
1000 Pass
738 ms
1000 Pass
985 ms
1000 Pass
769 ms
1000 Pass
389 ms
1000
Case 9.8.5 Pass
1404 ms
1000 Pass
2149 ms
1000 Pass
2015 ms
1000 Pass
1072 ms
1000 Pass
1029 ms
1000 Pass
1408 ms
1000 Pass
1674 ms
1000 Pass
1283 ms
1000 Pass
694 ms
1000
Case 9.8.6 Pass
3704 ms
1000 Pass
5651 ms
1000 Pass
5394 ms
1000 Pass
2782 ms
1000 Pass
2963 ms
1000 Pass
2628 ms
1000 Pass
3366 ms
1000 Pass
2658 ms
1000 Pass
1753 ms
1000
10 Misc JRuby 1.9.3 JRuby 2.0.0 MRI 1.9.3 MRI 2.0.0 MRI 2.1.0 Node v0.10.24 Node v0.4.12 Node v0.6.21-pre Node v0.8.26
10.1 Auto-Fragmentation
Case 10.1.1 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000 Pass1000



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:
κόσμεedited
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:
κόσμεedited
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 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 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 = 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 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 = 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 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.

MESSAGE:
κόσμε
cebae1bdb9cf83cebcceb5

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.

MESSAGE:

ce

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.

MESSAGE:
κ
ceba

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.

MESSAGE:
κ
cebae1

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.

MESSAGE:
κ
cebae1bd

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.

MESSAGE:
κό
cebae1bdb9

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.

MESSAGE:
κό
cebae1bdb9cf

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.

MESSAGE:
κόσ
cebae1bdb9cf83

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.

MESSAGE:
κόσ
cebae1bdb9cf83ce

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.

MESSAGE:
κόσμ
cebae1bdb9cf83cebc

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.

MESSAGE:
κόσμ
cebae1bdb9cf83cebcce

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.

MESSAGE:
κόσμε
cebae1bdb9cf83cebcceb5

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.

MESSAGE:

00

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.

MESSAGE:
€
c280

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.

MESSAGE:

e0a080

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.

MESSAGE:
𐀀
f0908080

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.

MESSAGE:

f888808080

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.

MESSAGE:

fc8480808080

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.

MESSAGE:

7f

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.

MESSAGE:
߿
dfbf

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.

MESSAGE:
￿
efbfbf

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.

MESSAGE:
􏿿
f48fbfbf

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.

MESSAGE:

f7bfbfbf

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.

MESSAGE:

fbbfbfbfbf

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.

MESSAGE:

fdbfbfbfbfbf

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.

MESSAGE:

ed9fbf

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.

MESSAGE:

ee8080

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.

MESSAGE:

efbfbd

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.

MESSAGE:
􏿿
f48fbfbf

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.

MESSAGE:

f4908080

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.

MESSAGE:

80

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.

MESSAGE:

bf

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.

MESSAGE:

80bf

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.

MESSAGE:

80bf80

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.

MESSAGE:

80bf80bf

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.

MESSAGE:

80bf80bf80

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.

MESSAGE:

80bf80bf80bf

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.

MESSAGE:

808182838485868788898a8b8c8d8e8f909192939495969798999a9b9c9d9e9fa0a1a2a3a4a5a6a7a8a9aaabacadaeafb0b1b2b3b4b5b6b7b8b9babbbcbdbe

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.

MESSAGE:

c020c120c220c320c420c520c620c720c820c920ca20cb20cc20cd20ce20cf20d020d120d220d320d420d520d620d720d820d920da20db20dc20dd20de20

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.

MESSAGE:

e020e120e220e320e420e520e620e720e820e920ea20eb20ec20ed20ee20

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.

MESSAGE:

f020f120f220f320f420f520f620

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.

MESSAGE:

f820f920fa20

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.

MESSAGE:

fc20

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.

MESSAGE:

c0

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.

MESSAGE:

e080

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.

MESSAGE:

f08080

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.

MESSAGE:

f8808080

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.

MESSAGE:

fc80808080

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.

MESSAGE:

df

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.

MESSAGE:

efbf

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.

MESSAGE:

f7bfbf

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.

MESSAGE:

fbbfbfbf

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.

MESSAGE:

fdbfbfbfbf

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.

MESSAGE:

c0e080f08080f8808080fc80808080dfefbff7bfbffbbfbfbffdbfbfbfbf

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.

MESSAGE:

fe

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.

MESSAGE:

ff

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.

MESSAGE:

fefeffff

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.

MESSAGE:

c0af

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.

MESSAGE:

e080af

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.

MESSAGE:

f08080af

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.

MESSAGE:

f8808080af

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.

MESSAGE:

fc80808080af

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.

MESSAGE:

c1bf

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.

MESSAGE:

e09fbf

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.

MESSAGE:

f08fbfbf

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.

MESSAGE:

f887bfbfbf

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.

MESSAGE:

fc83bfbfbfbf

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.

MESSAGE:

c080

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.

MESSAGE:

e08080

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.

MESSAGE:

f0808080

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.

MESSAGE:

f880808080

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.

MESSAGE:

fc8080808080

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.

MESSAGE:

eda080

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.

MESSAGE:

edadbf

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.

MESSAGE:

edae80

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.

MESSAGE:

edafbf

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.

MESSAGE:

edb080

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.

MESSAGE:

edbe80

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.

MESSAGE:

edbfbf

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.

MESSAGE:

eda080edb080

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.

MESSAGE:

eda080edbfbf

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.

MESSAGE:

edadbfedb080

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.

MESSAGE:

edadbfedbfbf

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.

MESSAGE:

edae80edb080

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.

MESSAGE:

edae80edbfbf

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.

MESSAGE:

edafbfedb080

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.

MESSAGE:

edafbfedbfbf

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.

MESSAGE:

efbfbe

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.

MESSAGE:
￿
efbfbf

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.

MESSAGE:
🿾
f09fbfbe

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.

MESSAGE:
🿿
f09fbfbf

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.

MESSAGE:
𯿾
f0afbfbe

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.

MESSAGE:
𯿿
f0afbfbf

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.

MESSAGE:
𿿾
f0bfbfbe

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.

MESSAGE:
𿿿
f0bfbfbf

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.

MESSAGE:
񏿾
f18fbfbe

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.

MESSAGE:
񏿿
f18fbfbf

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.

MESSAGE:
񟿾
f19fbfbe

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.

MESSAGE:
񟿿
f19fbfbf

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.

MESSAGE:
񯿾
f1afbfbe

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.

MESSAGE:
񯿿
f1afbfbf

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.

MESSAGE:
񿿾
f1bfbfbe

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.

MESSAGE:
񿿿
f1bfbfbf

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.

MESSAGE:
򏿾
f28fbfbe

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.

MESSAGE:
򏿿
f28fbfbf

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.

MESSAGE:
򟿾
f29fbfbe

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.

MESSAGE:
򟿿
f29fbfbf

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.

MESSAGE:
򯿾
f2afbfbe

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.

MESSAGE:
򯿿
f2afbfbf

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.

MESSAGE:
򿿾
f2bfbfbe

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.

MESSAGE:
򿿿
f2bfbfbf

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.

MESSAGE:
󏿾
f38fbfbe

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.

MESSAGE:
󏿿
f38fbfbf

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.

MESSAGE:
󟿾
f39fbfbe

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.

MESSAGE:
󟿿
f39fbfbf

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.

MESSAGE:
󯿾
f3afbfbe

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.

MESSAGE:
󯿿
f3afbfbf

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.

MESSAGE:
󿿾
f3bfbfbe

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.

MESSAGE:
󿿿
f3bfbfbf

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.

MESSAGE:
􏿾
f48fbfbe

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.

MESSAGE:
􏿿
f48fbfbf

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.

MESSAGE:

efbfbd

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.