fontgenerator.tech
Menu

Testing Methodology

Last reviewed 2026-09-06.

How the 156 style transforms are tested

Each transform is built from an explicit, documented Unicode code-point table (cited to the relevant Unicode chart in source comments), not inferred at runtime. Automated fixtures check: the full ASCII alphabet and digits, every documented exception letter (for example, the 11 script-block substitutions and 5 Fraktur-block substitutions), decomposed accents, mixed scripts (Latin/Hindi/Arabic), multiline input, emoji sequences, protected-link/mention/hashtag boundaries, and the exact input/output size limits. The five most recently added styles (regional-indicator, circle-overlay, square-overlay, vaporwave, glitch) get the same treatment, plus a dedicated fixture confirming adjacent regional-indicator letters can't accidentally pair into a flag emoji. These run in CI on every change to the engine; a change that breaks a fixture blocks release.

Platform/device testing — current status

Real-device compatibility testing (an authorized iPhone and Android device, real Instagram/Discord accounts) has not yet been completed for this revision — see the compatibility tables on the Instagram and Discord pages, where every row is marked "not yet tested" rather than assumed. Once real testing runs, each record will show the platform, exact field, device, OS/app version, date, and evidence.

Accessibility testing — current status

Automated scanning (axe) has not been run yet as of this revision — the structural choices (landmarks, skip link, labeled controls, focus order) are in place, but that is not the same as an automated scan or a manual pass. Neither a VoiceOver+Safari nor an NVDA+Firefox session has been completed yet — see the accessibility statement.

Known issues in this revision

Release history