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 |
|---|---|---|---|---|
| 006171 | generated/0882 Generated | false | 30 B | |
| 006172 | generated/0883 Generated | true | 391 B | |
| 006173 | generated/0884 Generated | true | 65 B | |
| 006174 | generated/0885 Generated | true | 10 B | |
| 006175 | generated/0886 Generated | true | 20 B | |
| 006176 | generated/0887 Generated | true | 37 B | |
| 006177 | generated/0888 Generated | true | 8 B | |
| 006178 | generated/0889 Generated | true | 67 B | |
| 006179 | generated/0890 Generated | false | 83 B | |
| 006180 | generated/0891 Generated | false | 9 B | |
| 006181 | generated/0892 Generated | false | 13 B | |
| 006182 | generated/0893 Generated | false | 3 B | |
| 006183 | generated/0894 Generated | false | 326 B | |
| 006184 | generated/0895 Generated | true | 81 B | |
| 006185 | generated/0896 Generated | true | 316 B | |
| 006186 | generated/0897 Generated | true | 214 B | |
| 006187 | generated/0898 Generated | true | 12 B | |
| 006188 | generated/0899 Generated | true | 65 B | |
| 006189 | generated/0900 Generated | true | 183 B | |
| 006190 | generated/0901 Generated | false | 124 B | |
| 006191 | generated/0902 Generated | true | 3 B | |
| 006192 | generated/0903 Generated | false | 59 B | |
| 006193 | generated/0904 Generated | true | 108 B | |
| 006194 | generated/0905 Generated | false | 51 B | |
| 006195 | generated/0906 Generated | false | 12 B | |
| 006196 | generated/0907 Generated | true | 2 B | |
| 006197 | generated/0908 Generated | false | 67 B | |
| 006198 | generated/0909 Generated | true | 18 B | |
| 006199 | generated/0910 Generated | false | 17 B | |
| 006200 | generated/0911 Generated | false | 34 B | |
| 006201 | generated/0912 Generated | true | 27 B | |
| 006202 | generated/0913 Generated | true | 55 B | |
| 006203 | generated/0914 Generated | false | 227 B | |
| 006204 | generated/0915 Generated | false | 29 B | |
| 006205 | generated/0916 Generated | false | 69 B | |
| 006206 | generated/0917 Generated | true | 372 B | |
| 006207 | generated/0918 Generated | false | 36 B | |
| 006208 | generated/0919 Generated | true | 144 B | |
| 006209 | generated/0920 Generated | true | 141 B | |
| 006210 | generated/0921 Generated | true | 78 B | |
| 006211 | generated/0922 Generated | false | 14 B | |
| 006212 | generated/0923 Generated | false | 11 B | |
| 006213 | generated/0924 Generated | false | 47 B | |
| 006214 | generated/0925 Generated | false | 112 B | |
| 006215 | generated/0926 Generated | false | 233 B | |
| 006216 | generated/0927 Generated | false | 55 B | |
| 006217 | generated/0928 Generated | true | 17 B | |
| 006218 | generated/0929 Generated | false | 5 B | |
| 006219 | generated/0930 Generated | true | 22 B | |
| 006220 | generated/0931 Generated | false | 69 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