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 |
|---|---|---|---|---|
| 005921 | generated/0618 Generated | false | 48 B | |
| 005922 | generated/0619 Generated | false | 46 B | |
| 005923 | generated/0620 Generated | true | 16 B | |
| 005924 | generated/0621 Generated | false | 32 B | |
| 005925 | generated/0622 Generated | false | 43 B | |
| 005926 | generated/0624 Generated | false | 356 B | |
| 005927 | generated/0625 Generated | false | 230 B | |
| 005928 | generated/0626 Generated | true | 59 B | |
| 005929 | generated/0627 Generated | true | 13 B | |
| 005930 | generated/0628 Generated | true | 359 B | |
| 005931 | generated/0629 Generated | true | 51 B | |
| 005932 | generated/0630 Generated | true | 63 B | |
| 005933 | generated/0631 Generated | true | 10 B | |
| 005934 | generated/0632 Generated | true | 14 B | |
| 005935 | generated/0633 Generated | true | 46 B | |
| 005936 | generated/0634 Generated | false | 4 B | |
| 005937 | generated/0635 Generated | true | 9 B | |
| 005938 | generated/0636 Generated | false | 101 B | |
| 005939 | generated/0637 Generated | false | 153 B | |
| 005940 | generated/0638 Generated | true | 320 B | |
| 005941 | generated/0639 Generated | true | 391 B | |
| 005942 | generated/0640 Generated | false | 397 B | |
| 005943 | generated/0641 Generated | true | 15 B | |
| 005944 | generated/0642 Generated | false | 10 B | |
| 005945 | generated/0643 Generated | true | 47 B | |
| 005946 | generated/0644 Generated | false | 50 B | |
| 005947 | generated/0646 Generated | false | 68 B | |
| 005948 | generated/0647 Generated | true | 5 B | |
| 005949 | generated/0648 Generated | false | 28 B | |
| 005950 | generated/0649 Generated | false | 256 B | |
| 005951 | generated/0650 Generated | false | 4 B | |
| 005952 | generated/0651 Generated | false | 141 B | |
| 005953 | generated/0653 Generated | false | 11 B | |
| 005954 | generated/0654 Generated | false | 30 B | |
| 005955 | generated/0655 Generated | true | 54 B | |
| 005956 | generated/0656 Generated | true | 117 B | |
| 005957 | generated/0657 Generated | false | 119 B | |
| 005958 | generated/0659 Generated | false | 15 B | |
| 005959 | generated/0660 Generated | true | 7 B | |
| 005960 | generated/0661 Generated | false | 12 B | |
| 005961 | generated/0662 Generated | false | 306 B | |
| 005962 | generated/0663 Generated | false | 21 B | |
| 005963 | generated/0664 Generated | true | 6 B | |
| 005964 | generated/0665 Generated | false | 85 B | |
| 005965 | generated/0666 Generated | false | 74 B | |
| 005966 | generated/0667 Generated | false | 355 B | |
| 005967 | generated/0668 Generated | true | 373 B | |
| 005968 | generated/0669 Generated | false | 191 B | |
| 005969 | generated/0670 Generated | true | 8 B | |
| 005970 | generated/0671 Generated | false | 357 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