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
1,925 of 7,246 cases · 1,057 true · 868 false
| Case | Name | Expected | Note | Size |
|---|---|---|---|---|
| 006521 | generated/1242 Generated | true | 29 B | |
| 006522 | generated/1243 Generated | true | 131 B | |
| 006523 | generated/1244 Generated | false | 16 B | |
| 006524 | generated/1245 Generated | true | 197 B | |
| 006525 | generated/1246 Generated | false | 64 B | |
| 006526 | generated/1247 Generated | false | 298 B | |
| 006527 | generated/1248 Generated | false | 4 B | |
| 006528 | generated/1249 Generated | true | 365 B | |
| 006529 | generated/1250 Generated | false | 150 B | |
| 006530 | generated/1251 Generated | true | 59 B | |
| 006531 | generated/1252 Generated | true | 300 B | |
| 006532 | generated/1253 Generated | false | 134 B | |
| 006533 | generated/1254 Generated | false | 17 B | |
| 006534 | generated/1255 Generated | false | 265 B | |
| 006535 | generated/1256 Generated | false | 263 B | |
| 006536 | generated/1257 Generated | false | 61 B | |
| 006537 | generated/1258 Generated | false | 18 B | |
| 006538 | generated/1259 Generated | true | 50 B | |
| 006539 | generated/1261 Generated | false | 15 B | |
| 006540 | generated/1262 Generated | false | 5 B | |
| 006541 | generated/1263 Generated | true | 60 B | |
| 006542 | generated/1264 Generated | false | 17 B | |
| 006543 | generated/1265 Generated | true | 12 B | |
| 006544 | generated/1266 Generated | true | 10 B | |
| 006545 | generated/1267 Generated | true | 349 B | |
| 006546 | generated/1268 Generated | false | 13 B | |
| 006547 | generated/1269 Generated | true | 273 B | |
| 006548 | generated/1270 Generated | false | 74 B | |
| 006549 | generated/1271 Generated | false | 7 B | |
| 006550 | generated/1272 Generated | true | 268 B | |
| 006551 | generated/1273 Generated | false | 79 B | |
| 006552 | generated/1274 Generated | false | 162 B | |
| 006553 | generated/1275 Generated | true | 9 B | |
| 006554 | generated/1276 Generated | false | 321 B | |
| 006555 | generated/1277 Generated | false | 3 B | |
| 006556 | generated/1278 Generated | true | 70 B | |
| 006557 | generated/1280 Generated | true | 9 B | |
| 006558 | generated/1281 Generated | true | 51 B | |
| 006559 | generated/1282 Generated | false | 96 B | |
| 006560 | generated/1283 Generated | false | 7 B | |
| 006561 | generated/1284 Generated | true | 35 B | |
| 006562 | generated/1285 Generated | false | 281 B | |
| 006563 | generated/1286 Generated | false | 343 B | |
| 006564 | generated/1287 Generated | false | 17 B | |
| 006565 | generated/1288 Generated | true | 11 B | |
| 006566 | generated/1289 Generated | true | 296 B | |
| 006567 | generated/1290 Generated | true | 37 B | |
| 006568 | generated/1291 Generated | false | 6 B | |
| 006569 | generated/1292 Generated | true | 36 B | |
| 006570 | generated/1293 Generated | false | 370 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