Testing Methodology
How QR64Code verifies tool function, privacy scope, browser compatibility, and measurable output.
A result is not assumed correct merely because it appears on screen. QR64Code uses known input/output pairs, round-trip checks, file comparisons, and accessible task flows.
Text and data tools
Base64 and URL tools are round-trip tested with ASCII, Turkish characters, multiple scripts, and emoji. The JSON tool is checked against valid samples and failures such as single quotes, trailing commas, and invalid numbers.
Hash and checksum
MD5, SHA-1, and SHA-256 are compared with known vectors. A file checksum must repeat for the same file and change after a one-byte modification.
QR tools
QR generation is checked across content types, error-correction levels, and export formats. Reader output is compared against samples produced by at least two encoders.
Image tools
Original and output size are recorded in bytes. Savings use `(original - output) / original × 100`. Pixel dimensions, transparency, and visible artifacts are inspected.
Privacy and accessibility
Developer tools verify that tool inputs are not attached to network requests. Keyboard order, visible focus, labels, error messages, and 390 px reflow are checked. This process does not by itself claim full WCAG compliance.