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 |
|---|---|---|---|---|
| 006350 | generated/1066 Generated | false | 2 B | |
| 006361 | generated/1078 Generated | true | 81 B | |
| 006371 | generated/1088 Generated | false | 13 B | |
| 006386 | generated/1104 Generated | true | 38 B | |
| 006390 | generated/1108 Generated | false | 290 B | |
| 006396 | generated/1114 Generated | false | 3 B | |
| 006401 | generated/1120 Generated | false | 331 B | |
| 006407 | generated/1126 Generated | false | 236 B | |
| 006410 | generated/1129 Generated | false | 35 B | |
| 006412 | generated/1131 Generated | false | 266 B | |
| 006414 | generated/1133 Generated | false | 242 B | |
| 006438 | generated/1157 Generated | false | 309 B | |
| 006440 | generated/1159 Generated | true | 92 B | |
| 006448 | generated/1167 Generated | false | 78 B | |
| 006454 | generated/1173 Generated | true | 379 B | |
| 006459 | generated/1178 Generated | false | 3 B | |
| 006471 | generated/1191 Generated | false | 4 B | |
| 006472 | generated/1192 Generated | false | 4 B | |
| 006481 | generated/1201 Generated | false | 275 B | |
| 006483 | generated/1203 Generated | false | 44 B | |
| 006500 | generated/1220 Generated | false | 8 B | |
| 006507 | generated/1227 Generated | false | 47 B | |
| 006517 | generated/1238 Generated | false | 139 B | |
| 006527 | generated/1248 Generated | false | 4 B | |
| 006534 | generated/1255 Generated | false | 265 B | |
| 006535 | generated/1256 Generated | false | 263 B | |
| 006536 | generated/1257 Generated | false | 61 B | |
| 006564 | generated/1287 Generated | false | 17 B | |
| 006576 | generated/1299 Generated | false | 15 B | |
| 006583 | generated/1306 Generated | true | 184 B | |
| 006592 | generated/1316 Generated | false | 5 B | |
| 006627 | generated/1351 Generated | false | 14 B | |
| 006640 | generated/1364 Generated | false | 10 B | |
| 006641 | generated/1365 Generated | false | 25 B | |
| 006656 | generated/1383 Generated | false | 25 B | |
| 006662 | generated/1389 Generated | false | 21 B | |
| 006671 | generated/1399 Generated | false | 10 B | |
| 006683 | generated/1411 Generated | false | 94 B | |
| 006688 | generated/1417 Generated | false | 15 B | |
| 006689 | generated/1418 Generated | false | 4 B | |
| 006710 | generated/1439 Generated | false | 12 B | |
| 006722 | generated/1453 Generated | false | 27 B | |
| 006726 | generated/1457 Generated | false | 378 B | |
| 006729 | generated/1460 Generated | true | 132 B | |
| 006730 | generated/1461 Generated | false | 385 B | |
| 006760 | generated/1492 Generated | false | 39 B | |
| 006762 | generated/1494 Generated | true | 159 B | |
| 006769 | generated/1501 Generated | false | 6 B | |
| 006774 | generated/1507 Generated | false | 37 B | |
| 006776 | generated/1509 Generated | true | 237 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