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 |
|---|---|---|---|---|
| 005806 | generated/0498 Generated | true | 50 B | |
| 005808 | generated/0500 Generated | false | 44 B | |
| 005812 | generated/0504 Generated | true | 69 B | |
| 005816 | generated/0508 Generated | true | 71 B | |
| 005820 | generated/0512 Generated | false | 246 B | |
| 005822 | generated/0514 Generated | false | 47 B | |
| 005827 | generated/0519 Generated | false | 246 B | |
| 005853 | generated/0548 Generated | false | 48 B | |
| 005860 | generated/0555 Generated | true | 50 B | |
| 005874 | generated/0570 Generated | true | 44 B | |
| 005877 | generated/0573 Generated | false | 12 B | |
| 005880 | generated/0576 Generated | false | 6 B | |
| 005893 | generated/0589 Generated | false | 326 B | |
| 005903 | generated/0599 Generated | false | 61 B | |
| 005942 | generated/0640 Generated | false | 397 B | |
| 005945 | generated/0643 Generated | true | 47 B | |
| 005946 | generated/0644 Generated | false | 50 B | |
| 005950 | generated/0649 Generated | false | 256 B | |
| 005951 | generated/0650 Generated | false | 4 B | |
| 005960 | generated/0661 Generated | false | 12 B | |
| 005962 | generated/0663 Generated | false | 21 B | |
| 005975 | generated/0676 Generated | false | 222 B | |
| 005978 | generated/0679 Generated | false | 221 B | |
| 005981 | generated/0682 Generated | false | 366 B | |
| 005983 | generated/0684 Generated | true | 272 B | |
| 006004 | generated/0705 Generated | false | 267 B | |
| 006010 | generated/0711 Generated | false | 42 B | |
| 006016 | generated/0717 Generated | false | 78 B | |
| 006034 | generated/0736 Generated | true | 120 B | |
| 006036 | generated/0738 Generated | false | 134 B | |
| 006054 | generated/0758 Generated | false | 370 B | |
| 006079 | generated/0783 Generated | false | 364 B | |
| 006095 | generated/0799 Generated | true | 110 B | |
| 006109 | generated/0813 Generated | false | 15 B | |
| 006122 | generated/0827 Generated | true | 236 B | |
| 006132 | generated/0838 Generated | false | 74 B | |
| 006139 | generated/0847 Generated | false | 43 B | |
| 006140 | generated/0849 Generated | true | 61 B | |
| 006153 | generated/0862 Generated | false | 118 B | |
| 006165 | generated/0876 Generated | true | 33 B | |
| 006183 | generated/0894 Generated | false | 326 B | |
| 006195 | generated/0906 Generated | false | 12 B | |
| 006197 | generated/0908 Generated | false | 67 B | |
| 006203 | generated/0914 Generated | false | 227 B | |
| 006219 | generated/0930 Generated | true | 22 B | |
| 006231 | generated/0942 Generated | false | 11 B | |
| 006234 | generated/0945 Generated | false | 21 B | |
| 006247 | generated/0959 Generated | false | 8 B | |
| 006256 | generated/0968 Generated | true | 4 B | |
| 006286 | generated/0998 Generated | true | 61 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