Compliance cases
These are the 7,246 inputs a submission must answer.
A conforming implementation returns true
for the 2,791 valid ones and false
for the 4,455 invalid ones.
You can run the suite without reading it, or open any case to see its input and where its first ill-formed byte is.
Well-formed means Table 3-7 of the Unicode Standard, as RFC 3629 restates it: no overlong forms, surrogates, code points above U+10FFFF, stray continuation bytes or sequences cut short. The compliance suite combines Markus Kuhn's UTF-8 stress test, WPT's fatal TextDecoder tests, every lead byte against the edges of its allowed ranges, errors at every offset around 16-, 32- and 64-byte blocks and at the end of every length up to 130 bytes, large inputs, and seeded random text. simdutf, Python and a Table 3-7 reference agree on every answer.
Run the full compliance suite locally. Replace your-component.wasm
with your compiled component.
Download the suite
curl -fLo validate_utf8.comply.wasm https://calculated.world/comply/validate_utf8.wasm
npx qipok your-component.wasm --suite validate_utf8.comply.wasm
203 of 7,246 cases · 49 true · 154 false
| Case | Name | Expected | Note | Size |
|---|---|---|---|---|
| 006781 | generated/1514 Generated | true | 8 B | |
| 006794 | generated/1529 Generated | false | 13 B | |
| 006796 | generated/1532 Generated | true | 146 B | |
| 006803 | generated/1539 Generated | false | 10 B | |
| 006804 | generated/1540 Generated | true | 14 B | |
| 006805 | generated/1541 Generated | false | 67 B | |
| 006806 | generated/1542 Generated | false | 349 B | |
| 006816 | generated/1553 Generated | true | 19 B | |
| 006817 | generated/1554 Generated | false | 2 B | |
| 006824 | generated/1561 Generated | false | 20 B | |
| 006837 | generated/1574 Generated | false | 12 B | |
| 006852 | generated/1589 Generated | false | 61 B | |
| 006869 | generated/1607 Generated | false | 7 B | |
| 006881 | generated/1620 Generated | false | 71 B | |
| 006883 | generated/1623 Generated | true | 191 B | |
| 006886 | generated/1626 Generated | true | 61 B | |
| 006898 | generated/1638 Generated | false | 171 B | |
| 006910 | generated/1651 Generated | false | 23 B | |
| 006916 | generated/1658 Generated | false | 45 B | |
| 006922 | generated/1664 Generated | false | 242 B | |
| 006923 | generated/1665 Generated | false | 8 B | |
| 006954 | generated/1697 Generated | false | 274 B | |
| 006958 | generated/1701 Generated | false | 8 B | |
| 006962 | generated/1705 Generated | false | 15 B | |
| 006963 | generated/1706 Generated | false | 103 B | |
| 006971 | generated/1714 Generated | true | 56 B | |
| 006989 | generated/1732 Generated | false | 65 B | |
| 007024 | generated/1767 Generated | false | 17 B | |
| 007029 | generated/1772 Generated | false | 52 B | |
| 007032 | generated/1776 Generated | true | 11 B | |
| 007033 | generated/1777 Generated | true | 227 B | |
| 007039 | generated/1783 Generated | false | 222 B | |
| 007044 | generated/1788 Generated | false | 63 B | |
| 007058 | generated/1802 Generated | false | 290 B | |
| 007060 | generated/1804 Generated | false | 16 B | |
| 007063 | generated/1807 Generated | false | 7 B | |
| 007085 | generated/1829 Generated | false | 198 B | |
| 007086 | generated/1830 Generated | false | 49 B | |
| 007089 | generated/1833 Generated | false | 24 B | |
| 007104 | generated/1848 Generated | false | 22 B | |
| 007114 | generated/1858 Generated | false | 356 B | |
| 007116 | generated/1860 Generated | false | 388 B | |
| 007118 | generated/1862 Generated | false | 149 B | |
| 007152 | generated/1899 Generated | true | 64 B | |
| 007159 | generated/1907 Generated | false | 202 B | |
| 007168 | generated/1917 Generated | false | 28 B | |
| 007185 | generated/1935 Generated | true | 244 B | |
| 007187 | generated/1937 Generated | false | 36 B | |
| 007198 | generated/1950 Generated | false | 20 B | |
| 007224 | generated/1977 Generated | true | 379 B |
Where these rules come from
Well-formed UTF-8 is defined by Table 3-7 of
the Unicode Standard, chapter 3
, which
RFC 3629
restates as ABNF. Every answer is agreed by
simdutf
9.4.0, Python’s strict codec and a direct reading of the table; the
suite’s own tests add Node.js’s buffer.isUtf8
and a fatal TextDecoder.
- UTF-8 decoder capability and stress test — Markus Kuhn’s file, the source of the 80 Kuhn cases
-
WPT textdecoder-fatal tests
— what browsers must reject when decoding with
fatal: true - Validating UTF-8 In Less Than One Instruction Per Byte — John Keiser and Daniel Lemire’s vectorised algorithm, which simdutf uses