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 |
|---|---|---|---|---|
| 005721 | generated/0409 Generated | false | 91 B | |
| 005722 | generated/0410 Generated | false | 64 B | |
| 005723 | generated/0411 Generated | true | 61 B | |
| 005724 | generated/0412 Generated | true | 73 B | |
| 005725 | generated/0413 Generated | true | 10 B | |
| 005726 | generated/0414 Generated | true | 309 B | |
| 005727 | generated/0415 Generated | true | 324 B | |
| 005728 | generated/0416 Generated | true | 362 B | |
| 005729 | generated/0417 Generated | true | 3 B | |
| 005730 | generated/0418 Generated | false | 80 B | |
| 005731 | generated/0419 Generated | true | 79 B | |
| 005732 | generated/0420 Generated | true | 4 B | |
| 005733 | generated/0421 Generated | false | 28 B | |
| 005734 | generated/0422 Generated | false | 14 B | |
| 005735 | generated/0423 Generated | true | 18 B | |
| 005736 | generated/0424 Generated | false | 335 B | |
| 005737 | generated/0425 Generated | false | 348 B | |
| 005738 | generated/0426 Generated | false | 134 B | |
| 005739 | generated/0427 Generated | false | 75 B | |
| 005740 | generated/0428 Generated | true | 12 B | |
| 005741 | generated/0429 Generated | true | 4 B | |
| 005742 | generated/0430 Generated | false | 79 B | |
| 005743 | generated/0431 Generated | false | 52 B | |
| 005744 | generated/0432 Generated | false | 33 B | |
| 005745 | generated/0433 Generated | true | 16 B | |
| 005746 | generated/0434 Generated | false | 4 B | |
| 005747 | generated/0435 Generated | false | 314 B | |
| 005748 | generated/0436 Generated | true | 60 B | |
| 005749 | generated/0437 Generated | true | 185 B | |
| 005750 | generated/0438 Generated | true | 6 B | |
| 005751 | generated/0439 Generated | true | 56 B | |
| 005752 | generated/0441 Generated | true | 5 B | |
| 005753 | generated/0442 Generated | true | 208 B | |
| 005754 | generated/0443 Generated | false | 15 B | |
| 005755 | generated/0444 Generated | true | 31 B | |
| 005756 | generated/0445 Generated | true | 386 B | |
| 005757 | generated/0446 Generated | true | 4 B | |
| 005758 | generated/0447 Generated | false | 36 B | |
| 005759 | generated/0448 Generated | false | 6 B | |
| 005760 | generated/0449 Generated | true | 29 B | |
| 005761 | generated/0450 Generated | true | 10 B | |
| 005762 | generated/0451 Generated | true | 358 B | |
| 005763 | generated/0452 Generated | true | 161 B | |
| 005764 | generated/0453 Generated | true | 203 B | |
| 005765 | generated/0454 Generated | true | 29 B | |
| 005766 | generated/0455 Generated | false | 39 B | |
| 005767 | generated/0456 Generated | false | 28 B | |
| 005768 | generated/0457 Generated | true | 16 B | |
| 005769 | generated/0458 Generated | false | 14 B | |
| 005770 | generated/0459 Generated | true | 14 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