Acceptance Tests

acceptance-tests_en.html

This document defines canonical pass/fail checks. A build is not accepted merely because it looks plausible once on one screen.

1. Rendering Fidelity Tests

1. Given a tile with visible QR in live state, exported output must include the QR in matching relative position and scale.
2. Given a text-only URL-art tile, 8K output must keep the URL-art sharp and readable relative to the documented layout.
3. Given the same state and assets, live/export/scripted composition order must match the canonical layer order.
4. Given a low-resolution source image with overlays, overlays and generated text must remain crisp even if the bitmap layer is source-limited.

2. Localization Tests

1. Controls and labels must be translatable via a documented key system or equivalent localized mechanism.
2. Longer translated labels must not break control layout.
3. RTL layouts must not invert or break unrelated geometry such as QR placement unless such mirroring is explicitly defined.

3. Documentation Preservation Tests

1. Updated canonical files should not be smaller than their previous versions without explicit justification.
2. No accepted behavior may disappear from the docs.
3. New scripting commands or arguments must appear in commands-and-functions and/or scripting-interface docs.