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
187 of 7,246 cases · 33 true · 154 false
| Case | Name | Expected | Note | Size |
|---|---|---|---|---|
| 005936 | generated/0634 Generated | false | 4 B | |
| 005949 | generated/0648 Generated | false | 28 B | |
| 005956 | generated/0656 Generated | true | 117 B | |
| 005984 | generated/0685 Generated | false | 289 B | |
| 005991 | generated/0692 Generated | false | 77 B | |
| 006007 | generated/0708 Generated | false | 6 B | |
| 006008 | generated/0709 Generated | false | 42 B | |
| 006020 | generated/0722 Generated | false | 63 B | |
| 006032 | generated/0734 Generated | false | 72 B | |
| 006047 | generated/0751 Generated | false | 196 B | |
| 006058 | generated/0762 Generated | false | 3 B | |
| 006091 | generated/0795 Generated | false | 13 B | |
| 006097 | generated/0801 Generated | false | 11 B | |
| 006099 | generated/0803 Generated | false | 317 B | |
| 006112 | generated/0817 Generated | true | 12 B | |
| 006114 | generated/0819 Generated | false | 168 B | |
| 006119 | generated/0824 Generated | false | 57 B | |
| 006120 | generated/0825 Generated | true | 266 B | |
| 006129 | generated/0835 Generated | false | 23 B | |
| 006131 | generated/0837 Generated | false | 7 B | |
| 006145 | generated/0854 Generated | false | 350 B | |
| 006164 | generated/0875 Generated | false | 221 B | |
| 006168 | generated/0879 Generated | false | 59 B | |
| 006171 | generated/0882 Generated | false | 30 B | |
| 006180 | generated/0891 Generated | false | 9 B | |
| 006204 | generated/0915 Generated | false | 29 B | |
| 006205 | generated/0916 Generated | false | 69 B | |
| 006236 | generated/0947 Generated | false | 4 B | |
| 006237 | generated/0948 Generated | false | 7 B | |
| 006238 | generated/0949 Generated | true | 12 B | |
| 006257 | generated/0969 Generated | false | 324 B | |
| 006262 | generated/0974 Generated | false | 5 B | |
| 006268 | generated/0980 Generated | false | 175 B | |
| 006272 | generated/0984 Generated | false | 3 B | |
| 006274 | generated/0986 Generated | false | 6 B | |
| 006285 | generated/0997 Generated | false | 91 B | |
| 006291 | generated/1003 Generated | false | 3 B | |
| 006301 | generated/1013 Generated | false | 3 B | |
| 006331 | generated/1045 Generated | true | 258 B | |
| 006379 | generated/1096 Generated | false | 17 B | |
| 006391 | generated/1109 Generated | true | 140 B | |
| 006404 | generated/1123 Generated | false | 234 B | |
| 006415 | generated/1134 Generated | false | 353 B | |
| 006417 | generated/1136 Generated | false | 4 B | |
| 006419 | generated/1138 Generated | false | 3 B | |
| 006422 | generated/1141 Generated | false | 73 B | |
| 006430 | generated/1149 Generated | false | 269 B | |
| 006432 | generated/1151 Generated | true | 319 B | |
| 006437 | generated/1156 Generated | false | 222 B | |
| 006449 | generated/1168 Generated | false | 77 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